-
Notifications
You must be signed in to change notification settings - Fork 33
Add ECS Service Linked Role to sandbox accounts #49
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
base: main
Are you sure you want to change the base?
Add ECS Service Linked Role to sandbox accounts #49
Conversation
Ensures ECS clusters can be created in the sandbox account without permission issues by adding the ECS service-linked role to the Nuke configuration. This prevents Nuke from deleting the role and causing issues when creating ECS clusters.
Simplifies the creation of the ECS service-linked role by using `CfnServiceLinkedRole` instead of manually defining the role and its policies. This change also removes unnecessary suppressions for cfn-guard, as the `CfnServiceLinkedRole` doesn't support `cfnOptions`. The nuke config is also updated to reflect the changes.
|
Hi @aws-khargita ! |
|
Help needed |
| - property: RoleName | ||
| type: glob | ||
| value: aws-controltower-* | ||
| IAMServiceLinkedRole: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately this will cause any customizations to the nuke configuration to be rolled back on update. This is how CloudFormation behaves with the HostedConfiguration resource.
We are planning on making some changes to preserve any customizations in the configuration files while still allowing updates like this, but unfortunately we can not merge this in it's current state.
Sorry for the inconvenience, we will get this sorted out in the future.
|
Hi, I appreciate you opening this pull request. Unfortunately, the change to the nuke config will result in the AppConfig configuration being rolled back to the default content on stack update, which may cause issues for users updating the solution. We are planning to address this upgrade issue in the next release, where we can hopefully incorporate this change. In the meantime, if you are deploying from source, the changes made here should allow for the creation of ECS clusters. Apologies for any inconvenience. |
Summary
Adds ECS Service Linked Role (
AWSServiceRoleForECS) to sandbox account resources to resolve ECS cluster creation failuresChanges
CfnServiceLinkedRolefor ECS service inIsbSandboxAccountResourcesIAMServiceLinkedRolein nuke-config.yamlProblem Solved
Fixes "Unable to assume the service linked role" error when creating ECS clusters in sandbox accounts.
Testing