This Guidance shows you how to implement the Resource Inventory Management capability. The Resource Inventory Management capability enables the collection, visibility, tracking, configuration validation, and service mapping of cloud resources. By tracking and monitoring your cloud resources, you can find opportunities for cost optimization, efficient allocation of resources, and increased governance.

Please note: [Disclaimer]

Architecture Diagram


Download the architecture diagram PDF 

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

Additional Considerations

Maintaining a healthy cloud environment starts with effective resource inventory management. Resource inventory management can enhance your disaster recovery preparedness and sustainability initiatives. Visibility into the location and configuration of resources helps you maintain an efficient and reliable cloud infrastructure for your business or projects. 

Establishing resource inventory management will contribute to a secure cloud environment by detecting unauthorized configurations, which allows for automated or manual responses to findings. Monitoring your resource inventory helps ensure optimal service application and performance, while also contributing to a secure environment through access tracking and effective security measures. Proper resource management aids in cost optimization by identifying underutilized or unused resources to help you get the most value out of your cloud investments. Additionally, maintaining a comprehensive inventory enables swift disaster recovery, resulting in minimal impact to business continuity during disruptions.

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

[Content Type]


This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].


The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.

Was this page helpful?