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

[Feature] Manage Organization resources using CloudFormation #580

Open
diegoroccia opened this issue Sep 18, 2024 · 2 comments
Open

[Feature] Manage Organization resources using CloudFormation #580

diegoroccia opened this issue Sep 18, 2024 · 2 comments

Comments

@diegoroccia
Copy link

diegoroccia commented Sep 18, 2024

Subject of the issue

AWS Cloudformation added support for the following new resource types

But org-formation still manages them via API calls and not via CloudFormation. Having the resources managed via CloudFormation would make it easier to migrate from/to org-formation.

Your environment

  • version of org-foramtion (ofn --version) 1.0.16
  • version of node (node --version) v18.19.1
  • which OS/distro Linux / Ubuntu

Steps to reproduce

Tell us how to reproduce this issue. Please provide ofn projct files if possible,
you can use this template as a base.
https://plnkr.co/edit/m568SDw2KPufQsUl

  • execute aws cloudformation list-stacks in the management account of an Organization managed via org-formation
  • notice that

Expected behaviour

There should be stacks for the Organization, the OUs, the Accounts and policies

Actual behaviour

no stacks are listed there

@yannickvr
Copy link

Not an issue for most/many, but CloudFormation has a resource limit of 500 resources, so migrating to CF would limit OFN to manage a maximum of 500 accounts.

@diegoroccia
Copy link
Author

@yannickvr the tool could create multiple stacks to overcome the limit. Also, this could be an opt in feature, since not everyone cares about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants