VPC is the topic that flies under the radar of many Software Developers, despite being present in every AWS account (well, maybe not for accounts created before 2009…but that’s unlikely). There are a few reasons for this I can think of:

1. Big companies have Ops/DevOps/SysAdmin/SRE/Security departments that take care of VPC
2. Startups often don’t bother tuning it - everything works with default settings after all
3. Networking is complicated and is rarely regarded as fun

Despite those somewhat justified arguments, most developers that deal with AWS would benefit from digging deeper into VPC setup and its configuration. Here are my counterpoints:

1. Understanding VPC will help you communicate with; Ops/DevOps/SysAdmin/SRE/Security department much more efficiently
2. Everything works by default because everything is open (i.e. unsecure) by default
3. Oh but it is fun when you dig deep enough

#devops #aws #aws-services #amazon-web-services #aws vpc