You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The service-linked-roke spoke stack is marked as optional, but it is required (without manually doing the attachment first) for existing/new AWS accounts that never had attachments before to work with the tag automation.
We can't simply deploy the service-linked-role stack using stacksets as some accounts will already have this role and return error. This makes it harder to automate the service-linked-role creation for member accounts.
Describe the feature you'd like
I'd like the spoke template to perform a check on whether the service linked role already exist, and if not, create it as part of the same stack. This way users won't need to worry about the service linked role to avoid troubleshooting efforts.
Additional context
I can help with the solution for this if the team wants to implement this. Thanks.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The service-linked-roke spoke stack is marked as optional, but it is required (without manually doing the attachment first) for existing/new AWS accounts that never had attachments before to work with the tag automation.
We can't simply deploy the service-linked-role stack using stacksets as some accounts will already have this role and return error. This makes it harder to automate the service-linked-role creation for member accounts.
Describe the feature you'd like
I'd like the spoke template to perform a check on whether the service linked role already exist, and if not, create it as part of the same stack. This way users won't need to worry about the service linked role to avoid troubleshooting efforts.
Additional context
I can help with the solution for this if the team wants to implement this. Thanks.
The text was updated successfully, but these errors were encountered: