5 Common AWS Errors New Developers Hit (And How to Fix Them)

Table of Contents Intro AccessDenied InvalidClientTokenId ThrottlingException ResourceNotFoundException ValidationException Patterns Behind the Errors Intro You take pride in writing clean code... You've passed all the technical interviews... You've shipped features locally without breaking anything... Then you attempt to deploy in a real AWS environment, and quickly get humbled. If you’ve read my previous blog post about starting your first developer job in an AWS environment, then you know the moment I’m referring to. You log into the console at work and notice resources that existed long before you arrived, with names that look autogenerated and dashboards that are lighting up. Then after a few weeks of getting comfortable, you try to deploy a feature or call an API for the first time, and you're stopped in your tracks by an AccessDenied error message. You feel confused at first because nothing seems obviously wrong. Your code runs, your logic is sound and yet AWS still tells you, "