AWS Builder Center

What a Software Dev Student Wishes They Knew Before Touching AWS

.

Software dev
As a dev student, my first instinct with any AWS service used to be "how do I use this" — studying for Cloud Practitioner shifted that to "how does this get misconfigured." A few things that reframed how I study: S3 isn't insecure by default — misconfiguration is the risk. Public bucket breaches almost always trace back to a permissions setting someone forgot to check, not a flaw in S3 itself. The Shared Responsibility Model is the whole ballgame. AWS secures the cloud. You secure what's in the cloud. A huge chunk of real-world breaches happen because someone assumed AWS had their side covered. CloudTrail isn't optional if you care about what's happening in your account. No logging means no idea what happened when something goes wrong. It's the first thing I look for now. If you're studying for a cert, treating every service as "how could this be abused" instead of "how do I turn this on" changes how fast it sticks. Question for the comments: What's one AWS default setting you'd change immediately on any new account?
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article