# License issue at AWS Fargate deploy: LeasedActivationStrategy **URL:** \ **Category:** Ignition\ **Tags:** docker, ignition81\ **Created:** [December 21, 2023, 8:52pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447 "2023-12-21T20:52:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Nicolas\_Spadavecchia](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicolas_spadavecchia/32/50940_2.png) [@Nicolas\_Spadavecchia](https://forum.inductiveautomation.com/u/Nicolas_Spadavecchia)\ **Post date:** [December 21, 2023, 8:52pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447/1 "2023-12-21T20:52:46Z")
Hi all, we are experiencing an issue when we deploy a new task in AWS Fargate, specifically this one: jvm 1 | E [c.i.i.g.l.LeasedActivationStrategy] : Received error when trying to activate. Request ID: 'xxx-xxx-xxxx-xx-xxxx', Code: '3', Message: 'Activation Request sent Too Early'. We have an external volume for /bin/ignition/data and the 8-keys license. We have been doing successful deploys using the standard license (6-keys). Now it looks like moving to the 8-keys license is not working. Any ideas? Thanks in advance. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 21, 2023, 9:39pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447/2 "2023-12-21T21:39:31Z")
The logger you find searching "LeasedActivationStrategy" set to DEBUG may be useful. [https://docs.inductiveautomation.com/display/DOC81/Diagnostics+-+Logs#DiagnosticsLogs-ChangingLoggingLevels](https://docs.inductiveautomation.com/display/DOC81/Diagnostics+-+Logs#DiagnosticsLogs-ChangingLoggingLevels) ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [December 21, 2023, 10:08pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447/3 "2023-12-21T22:08:40Z")
> Now it looks like moving to the 8-keys license is not working. Is your Gateway inactive (showing the trial banner)? Or is it just that you see this error message? Are you seeing this error message repeating periodically? ---
**Author:** ![Nicolas\_Spadavecchia](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicolas_spadavecchia/32/50940_2.png) [@Nicolas\_Spadavecchia](https://forum.inductiveautomation.com/u/Nicolas_Spadavecchia)\ **Post date:** [December 22, 2023, 8:36pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447/4 "2023-12-22T20:36:02Z")
Hi kevin, thanks for pointing me to this. I was able to solve the issue by checking the logs in deep. The issue was related to one of our custom scripts for perspective. Thank you! ---
**Author:** ![Nicolas\_Spadavecchia](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicolas_spadavecchia/32/50940_2.png) [@Nicolas\_Spadavecchia](https://forum.inductiveautomation.com/u/Nicolas_Spadavecchia)\ **Post date:** [December 22, 2023, 8:38pm UTC](https://forum.inductiveautomation.com/t/license-issue-at-aws-fargate-deploy-leasedactivationstrategy/83447/5 "2023-12-22T20:38:01Z")
Hi Joel, the gateway was always up and licensed, the issue was related to a new deployment. I was able to solve the issue by checking the logs. The issue was related to one of our custom scripts. Thanks!