Skip to content
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

[Enhancement] Add ability to manage SCPs on nested ou's #1046

Open
Brian969 opened this issue Aug 17, 2022 · 1 comment
Open

[Enhancement] Add ability to manage SCPs on nested ou's #1046

Brian969 opened this issue Aug 17, 2022 · 1 comment
Assignees
Labels
1-Codebase Related to the SEA Solution/automation tooling 2-Enhancement New minor feature or request

Comments

@Brian969
Copy link
Contributor

  • ASEA manages SCPs on top level OUs
  • ASEA manages SCPs on specific AWS accounts
  • add ability to manage nested OU SCPs
  • add ability to mandate an account level SCP, at the OU level
@Brian969 Brian969 added 2-Enhancement New minor feature or request 1-Codebase Related to the SEA Solution/automation tooling labels Aug 17, 2022
@Brian969 Brian969 self-assigned this Aug 17, 2022
@rverma-dev
Copy link
Contributor

rverma-dev commented Aug 26, 2022

It seems an imminent need, We recently tried to upgrade to CT 3.0. We observed that we are running out of SCP limitations of 5 per OU.

Seems like CT adds 2 SCPs per OU, then we need to attach the FullAccessPolicy too, which left room for just 2 policies, but we are attaching 3 (Phase-0, Phase-1, Sensitive). I felt Sensitive is no more required too. However, it seems the Control tower teams have unnecessarily bloated the SCPs by packaging small policy doc within single SCPs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-Codebase Related to the SEA Solution/automation tooling 2-Enhancement New minor feature or request
Projects
None yet
Development

No branches or pull requests

3 participants