A single HTML file that displays your entire AWS service inventory using the AWS JavaScript SDK and Bootstrap.
AWS Inventory is a client-side web application that provides a comprehensive overview of all your AWS services and resources in a single HTML file. It solves the problem of fragmented AWS management by allowing users to view their entire cloud inventory without installing software or configuring servers.
AWS administrators, DevOps engineers, and cloud developers who need a quick, portable way to audit and visualize their AWS resources across multiple services.
Developers choose AWS Inventory for its extreme simplicity—it requires only a browser and AWS credentials—and its flexibility in querying AWS APIs with JMESPath to create custom inventory views without backend infrastructure.
AWS Inventory in a single HTML file using JS AWS-SDK & Bootstrap
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The entire tool is a single HTML file with zero installation or server setup required, making it highly portable and easy to deploy, as emphasized in the README.
Leverages the official AWS JavaScript SDK for browser-based API calls, ensuring reliable and up-to-date interactions with AWS services without custom backends.
Uses JMESPath syntax to parse and extract specific data from AWS API responses, allowing users to customize table configurations and focus on relevant resource details.
Presents inventory data in clean, responsive tables using Bootstrap, providing a polished user experience without additional CSS work, as shown in the example screenshot.
The README admits that not all AWS services are supported due to CORS restrictions in the browser SDK, limiting inventory to a subset of AWS APIs and reducing comprehensiveness.
Requires AWS credentials to be entered or stored in the browser, which poses risks like accidental exposure or XSS attacks, especially in shared or untrusted environments.
Each AWS service needs custom JMESPath queries and table headings defined in code, which can be error-prone and time-consuming for users unfamiliar with AWS APIs or JMESPath.