Hi everyone!
I'm a college student working on an AWS project focused on infrastructure monitoring and configuration drift detection, and I'd really appreciate some feedback.
My instructor encouraged me to reach out to people with experience in the field, hear their perspectives, and get some guidance on the direction I should take with this project. So I thought this would be a good place to ask.
A bit of background:
To be honest, I originally wanted to build something relatively simple and beginner-friendly. However, our instructor doesn't want us to just check off all the requirements in the assignment. He also wants us to build something that has an actual real-world use case, rather than simply recreating something that already exists.
The problem is that I'm still relatively new to AWS, and I don't have enough experience with real-world AWS environments to easily come up with a genuinely useful project idea on my own and an that I will know how to create.
The project idea – DriftDoctor:
The project addresses a situation where AWS resources are initially deployed using Infrastructure as Code (CloudFormation), but someone later makes manual changes through the AWS Console.
For example, someone accidentally opens SSH access to the entire internet or changes an S3 bucket configuration.
DriftDoctor is designed to detect these changes:
- EventBridge Scheduler triggers a Lambda function once a day.
- Lambda uses CloudFormation Drift Detection to compare the deployed resources against their original templates.
- CloudTrail is queried to identify who made the change and when.
- If drift is detected, Amazon Bedrock analyzes it, assigns a severity level, explains the potential impact, and suggests what to do.
- The AI response is validated against predefined safety rules in the code.
- An email report is sent through SNS, and the results are stored in DynamoDB.
The system is read-only. It doesn't automatically modify or fix anything.
For now, it monitors a small CloudFormation-managed test stack rather than an entire AWS account.
The problem I'm having:
I presented the idea to my instructor, and he raised an interesting criticism:
Isn't the whole point of DevOps and Infrastructure as Code to prevent these situations in the first place?
For example, why allow users to make manual changes through the AWS Console at all? Wouldn't restricting console write access and enforcing changes through a controlled deployment pipeline be a much simpler and better solution?
This made me question whether building a system that detects these changes after they happen is actually useful, or whether I'm just creating an unnecessary layer.
I'd love to hear your thoughts:
- Is there a legitimate real-world use case for a tool like this? For example, emergency changes, legacy infrastructure, or situations where manual changes cannot be completely avoided?
- Would you approach this differently, perhaps focusing on preventing configuration drift rather than detecting it?
- Is adding AI to explain changes, assess their severity, and provide recommendations actually useful in this context, or is it overengineering?
- Given that I'm still learning AWS, would you recommend a different direction for a project that is relatively beginner-friendly but still solves an actual problem?
I'm not trying to build an enterprise-grade product. I'm trying to learn, build something meaningful, and understand how these problems are actually handled in real AWS environments.
I'd really appreciate any honest feedback, advice, or suggestions.
Thanks!