I've been exploring ways to better integrate "Cloud Resources" into our architecture using Compass, particularly with a focus on AWS Accounts. I believe that having cloud resources show up as "services" in Compass could significantly enhance our visibility into interdependencies.
For example, we could define each cloud resource (like AWS S3, AWS RDS, VPCs, etc.) as a component within Compass, explicitly associating it with the specific AWS Account it belongs to. This would allow us to track which services are dependent on particular cloud resources and across which AWS Accounts, thereby giving us a clearer picture of our architecture.
Currently, I'm having to switch all items like AWS accounts, VPCs, and other cloud resources that were imported as "Cloud Resource" components into "Service" components to make them show in Jira Service Management, especially when they are required for a change request or incident. This additional step can be cumbersome and seems to be a workaround rather than a seamless integration.
Is there a recommended approach for bringing AWS Accounts and cloud resources into Compass as first-class "Service" components, and if not, could this be a potential area for improvement? How might we enhance Compass to support these use cases more effectively and improve integration with Jira Service Management?
