Inspiration
AWS JAM
What it does
Jam - CLD 42 fixes and secures AWS cloud infrastructure by improving availability, logging, automation, and deployment checks. It turns incomplete AWS setups into working, production-style cloud workflows.
How we built it
We used AWS services like EC2, ALB, CloudFront, RDS, CloudWatch Logs, S3, Lambda, EventBridge, CodePipeline, CodeBuild, and CodeCommit. Each task involved finding the broken configuration, fixing it, and validating it through AWS.
Challenges we ran into
We ran into IAM permission limits, strict bucket policy requirements, failed pipeline checks, and broken EC2 metadata routing. Some issues looked correct at first but required checking logs and service-specific settings.
Accomplishments that we're proud of
We successfully configured high availability, secured ALB access through CloudFront, automated RDS audit log exports, and fixed CI/CD template issues. We also troubleshot a Windows EC2 metadata route problem using PowerShell.
What we learned
We learned how AWS services connect in real cloud operations and how small permission or configuration mistakes can break automation. We also learned to rely on logs, validation checks, and least-privilege security practices.
What's next for Jam- CLD 42
Next, we would add monitoring dashboards, CloudWatch alarms, stronger S3/KMS security, and full infrastructure-as-code automation. We would also improve visibility into failed log exports and pipeline failures.
Built With
AWS Lambda, EventBridge, RDS, CloudWatch Logs, S3, EC2, ALB, CloudFront, CodePipeline, CodeBuild, CodeCommit, CloudFormation, IAM, Python, PowerShell, cfn-lint, and cfn-nag.
Log in or sign up for Devpost to join the conversation.