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
Our AWS Org settings require all new IAM roles to have a specific Permission Boundary applied. Any role create command where the role does not have this permission boundary will fail.
I have followed the instructions to set up the Console, and when I deployed the console stack in us-east-1, I customized the template so that the SST role you're using has the Permission Boundary.
BUT since you are using that role to create other roles, they also need the same permission boundary applied. Is there a way I can instruct SST Console to use a certain boundary for any roles that it wants to create?
Our AWS Org settings require all new IAM roles to have a specific Permission Boundary applied. Any role create command where the role does not have this permission boundary will fail.
I have followed the instructions to set up the Console, and when I deployed the console stack in us-east-1, I customized the template so that the SST role you're using has the Permission Boundary.
BUT since you are using that role to create other roles, they also need the same permission boundary applied. Is there a way I can instruct SST Console to use a certain boundary for any roles that it wants to create?
See related discord thread: https://discord.com/channels/983865673656705025/990989982799900792/1241145612624330872
The text was updated successfully, but these errors were encountered: