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
I'd like to see support imports for CloudFormation templates and/or stacks.
Use Case
The correct, and robust way, to define infrastructure is by using IaC approach. The service for that on AWS is CloudFormation. Most mature organizations will not have a bunch of resources just scattered around an account. So a diagram based on an account scan is mostly useless.
A boundary for an application is generally a CloudFormation Stack(s).
So it makes sense to base the diagrams on that too.
Suggested Solution
Rather than scanning resources manually, allow users to feed a CloudFormation template or provide a stack name from which to extract resources.
Alternatives Considered
N/A
Additional Context
N/A
Checklist
I have searched for similar feature requests.
I have included all necessary information.
The text was updated successfully, but these errors were encountered:
Hi @moltar, thanks for taking the time to open this issue. Our current script focuses on scanning existing infrastructure resources. We're planning to add CloudFormation support as a new feature in the near future. We'll keep you updated on our progress in this thread.
Feature Description
I'd like to see support imports for CloudFormation templates and/or stacks.
Use Case
The correct, and robust way, to define infrastructure is by using IaC approach. The service for that on AWS is CloudFormation. Most mature organizations will not have a bunch of resources just scattered around an account. So a diagram based on an account scan is mostly useless.
A boundary for an application is generally a CloudFormation Stack(s).
So it makes sense to base the diagrams on that too.
Suggested Solution
Rather than scanning resources manually, allow users to feed a CloudFormation template or provide a stack name from which to extract resources.
Alternatives Considered
N/A
Additional Context
N/A
Checklist
The text was updated successfully, but these errors were encountered: