
Weekend Showcase Challenge: AWS ResourceLens
One Dashboard to Analyze, Estimate, and Manage AWS Resources
Managing cloud infrastructure often means jumping between multiple AWS services just to answer simple questions: What resources are running? How much could a new resource cost? Which services are consuming the most? And what would happen to the monthly estimate if I added another resource?
For the Weekend Showcase Challenge, I built AWS ResourceLens, an AWS-native platform designed to bring resource visibility, cost estimation, and resource management into one simple dashboard.
The idea is straightforward: instead of checking multiple AWS consoles separately, ResourceLens provides a centralized interface where users can analyze their AWS environment, estimate the cost of planned resources, and manage supported resources through a controlled workflow.
The Vision
The vision behind ResourceLens is to make AWS infrastructure easier to understand and manage without requiring users to constantly move between different service consoles.
The application focuses on three major areas:
Analyze — Understand the resources currently running in an AWS environment.
Estimate — Calculate an approximate monthly cost before deploying a new resource.
Manage — Provide a controlled workflow for creating or managing supported AWS resources.
The goal is not to replace the AWS Console. Instead, ResourceLens acts as a simplified infrastructure control layer that brings commonly needed information together.
How It Works
A user first signs into the application using AWS-native authentication.
After authentication, the application communicates with the backend through Amazon API Gateway. AWS Lambda processes the request and interacts with AWS services using IAM permissions.
The dashboard can retrieve information about supported AWS resources such as EC2 instances, S3 buckets, Lambda functions, DynamoDB resources, RDS resources, and other infrastructure components depending on the configured permissions.
For cost-related information, the application can retrieve AWS billing and cost data through AWS-native services. Users can also configure a planned resource and receive an estimated monthly cost before proceeding.
For example, a user could select an EC2 configuration, choose a region and instance type, define expected usage, and receive an estimated monthly cost.
The application can then present the result in a simple format:
Current Estimated Spend
New Resource Estimate
Projected Monthly Cost
This gives the user a better understanding of the potential financial impact before making an infrastructure change.
AWS Architecture
ResourceLens is designed around AWS managed services.
The frontend is hosted using Amazon S3 and delivered through Amazon CloudFront.
Authentication is handled using Amazon Cognito, keeping the authentication layer inside the AWS ecosystem rather than depending on external identity providers.
Requests from the frontend are sent to Amazon API Gateway, which invokes AWS Lambda functions.
Lambda acts as the application backend and communicates with AWS services using IAM roles and permissions.
The architecture can be summarized as:
User → Cognito → CloudFront/S3 → API Gateway → Lambda → AWS Services
For environments where cross-account access is required, AWS Security Token Service (STS) can be used with an IAM role to provide temporary access rather than storing permanent AWS access keys.
This is an important design decision because the application should never require users to paste or permanently store their AWS Secret Access Keys.
Cost Estimation
One of the main features of ResourceLens is cost estimation.
Before creating a resource, users can provide the configuration they are considering. The application then calculates an estimated monthly cost based on the selected configuration and expected usage.
The project separates estimated pricing from actual AWS billing data.
Actual spending can be retrieved from AWS billing services, while planned resource costs are treated as estimates.
This distinction is important because an estimate should not be presented as an exact future bill.
The dashboard can therefore help users answer questions such as:
- How much am I currently spending?
- How much could this new resource cost?
- What would my projected monthly cost look like?
- Which resources should I investigate?
Resource Management
ResourceLens also explores controlled resource management.
Instead of immediately executing infrastructure changes, the application follows a review-based workflow:
Configure → Estimate → Review → Confirm → Create
This approach gives the user an opportunity to verify the configuration and expected cost before an AWS API request is executed.
IAM permissions are used to control which operations the backend can perform.
This design also makes the project safer because resource creation is not treated as an unrestricted automated action.
Why AWS-Native?
One of the main goals of this project was to avoid unnecessary third-party dependencies.
The application uses AWS services for authentication, compute, APIs, infrastructure access, billing information, storage, monitoring, and AI capabilities.
The core platform can therefore operate within the AWS ecosystem without depending on services such as external authentication providers, third-party databases, or external AI APIs.
For AI-powered recommendations, Amazon Bedrock can be integrated to analyze resource information and provide infrastructure optimization suggestions.
For example, ResourceLens could identify resources that deserve investigation and explain why they may represent an optimization opportunity.
Challenges
The biggest challenge was not building the interface. It was thinking carefully about permissions and security.
An application that can interact with AWS resources must be designed around least-privilege access.
Giving the backend unrestricted permissions would make the application unnecessarily risky. Instead, the architecture uses IAM permissions to limit what the application can access and which operations it can perform.
Another challenge was separating cost estimation from actual billing information. Cloud pricing depends on region, resource configuration, usage patterns, and other factors, so the application needs to communicate estimates clearly rather than presenting them as guaranteed costs.
What I Learned
This project helped me look at AWS from a platform-engineering perspective rather than focusing on a single service.
I worked through how authentication, APIs, serverless compute, IAM, AWS resource APIs, billing information, and cost estimation can come together into one application.
The project also reinforced an important lesson: cloud automation is not simply about making infrastructure changes faster. Good automation also needs strong permission boundaries, visibility, validation, and cost awareness.
What's Next?
There are several directions I would like to explore in future versions.
ResourceLens could provide more detailed cost dashboards, resource history, budget alerts, infrastructure recommendations, and additional AWS service support.
Another interesting direction would be adding a natural-language interface through Amazon Bedrock.
A user could ask:
“What resources are currently running in this region?”
or:
“Estimate the monthly cost of adding another application server.”
The system could translate those requests into structured AWS operations and return the relevant information.
Final Thoughts
AWS provides powerful services for building infrastructure, but managing multiple resources can quickly become complex.
With ResourceLens, I wanted to explore a simple idea: what if resource visibility, cost estimation, and controlled infrastructure management could exist in one AWS-native interface?
This project is my attempt to turn that idea into a practical weekend build.
It combines AWS serverless architecture, IAM-based security, AWS resource APIs, billing information, cost estimation, and optional generative AI capabilities into one platform.
More importantly, the project gave me an opportunity to move beyond simply learning individual AWS services and think about how those services can work together to solve a real infrastructure problem.
GitHub Repository: https://github.com/SYMOIZ/AWS-ResourceLens-Cognito-authenticated-AWS-dashboard-MVP
AWS Services: Amazon S3, Amazon CloudFront, Amazon Cognito, Amazon API Gateway, AWS Lambda, IAM, AWS STS, AWS Cost Explorer, Amazon Bedrock, Amazon DynamoDB
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article