-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECS Service fails to launch on Fargate 1.4.0 #222
Comments
Which region do u use? |
us-east-1 |
Hi @seth-xdam
|
I'm us-east-2 and and I'm getting the exact same error using the keycloak-aurora-serverless-from-existing-vpc.template. After googling the error it seemed to be related to changes AWS made in Fargate 1.4.0, so I downloaded your template and specified version 1.3.0 but it didn't help. Our VPC is a very simple, default setup, we're not doing anything special or unusual but I'm happy to help you troubleshoot. Its unfortunate that you took all the time to put this full example together and its not working so I'm guessing its something minor that needs to be tweaked. I'd really like to get this working because setting it all up manually is going to be a real pain. Is there anyway we can short circuit the secrets thing where I set that part up manually in advance and modify the template accordingly? |
When trying to launch the "keycloak-from-existing-vpc" in a region that uses Fargate 1.4.0, the ECS Cluster gets stuck trying to create. Digging in to the resource, it continuously tries to run the configured tasks, and fails because:
I have tried making the many possible changes to my existing VPC suggested in this thread with no success, including adding a Secrets Manager endpoint to my VPC, trying both public and private subnets, opening additional ports on related security groups, and even modifying you template to assign public IPs to the ECS Tasks.
The text was updated successfully, but these errors were encountered: