AWS Usage Monitoring Expert
Budget: $250 – $750 CAD
I’m tightening up the spend on my AWS estate and the first priority is solid usage monitoring. Most of my costs come from a mix of EC2 instances, S3 buckets and RDS databases, so I need CloudWatch-driven visibility that lets me drill straight from a monthly bill spike down to the offending resource.
I’ve already written some helper code, but it needs polishing, testing and a bit of re-architecting. Because I can’t expose my production credentials, you’ll run the code against your own active AWS and Azure accounts first, prove the results, then guide me step-by-step in hooking it into mine.
Here’s what I’m after:
• Refactor or extend my current scripts so they pull detailed CloudWatch metrics for EC2, S3 and RDS and store them in a cost-focused data model.
• Build a lightweight dashboard or CLI summary that highlights anomalies, idle resources and daily burn rates.
• Provide a short hand-off doc and a live walk-through so I can replicate everything inside my environment without surprises.
Successful delivery means the scripts run error-free in your accounts, the dashboard surfaces at least one clear optimisation in each service area, and I can repeat the process on my side in a single session.
If you actively manage both AWS and Azure today and are comfortable living inside CloudWatch, let’s get started.
I’ve already written some helper code, but it needs polishing, testing and a bit of re-architecting. Because I can’t expose my production credentials, you’ll run the code against your own active AWS and Azure accounts first, prove the results, then guide me step-by-step in hooking it into mine.
Here’s what I’m after:
• Refactor or extend my current scripts so they pull detailed CloudWatch metrics for EC2, S3 and RDS and store them in a cost-focused data model.
• Build a lightweight dashboard or CLI summary that highlights anomalies, idle resources and daily burn rates.
• Provide a short hand-off doc and a live walk-through so I can replicate everything inside my environment without surprises.
Successful delivery means the scripts run error-free in your accounts, the dashboard surfaces at least one clear optimisation in each service area, and I can repeat the process on my side in a single session.
If you actively manage both AWS and Azure today and are comfortable living inside CloudWatch, let’s get started.
Related categories:
Linux
Cloud Computing
Azure
Amazon Web Services
Node.js
Aws Lambda
Data Analysis
Cloud Security