-
Notifications
You must be signed in to change notification settings - Fork 84
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
Doesnt work out of the box with a new Control Tower AWS IAM account #506
Comments
The |
I raised the lambda concurrency limit to move further and
then failed
|
Are you deploying the solution to to an existing VPC? |
Yes, with private subnets |
The reason for the first timeout is that this custom resource runs in a VPC and in order for a custom resource to signal to CloudFormation that it has either succeeded or failed it must write to an S3 bucket: if there is no NAT gateway or S3 endpoint in the VPC then there is no way for this request to get to S3. There is documentation to verify if the VPC you are deploying to has the necessary configuration: Without a NAT gateway will need VPC endpoints for every service listed in the documentation below in order for the Discovery process to work (this should also should fix your ECS issue): https://docs.aws.amazon.com/solutions/latest/workload-discovery-on-aws/aws-apis.html |
Describe the bug
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: