Amazon VPC has come along way since it was first introduced. For those who are not familiar the Amazon VPC (Virtual Private Cloud), it allows us to provision our own section of the cloud. Here we can manage our own routing tables, subnets, internal static IP addresses as well as create VPN (Virtual Private Network) connections to our VPC. Now that Amazon VPC has evolved, it’s good practice to always put our instances inside of a VPC. This can present somewhat of a problem if you already have EC2 (Elastic Compute Cloud) and RDS (Relational Database Service) instances running outside of a VPC. Running our database instance inside of a VPC allows our instance to run on a private network and not open to the internet. Outside of a VPC, your database server is open to the general internet/public, which is a huge security issue.
If you’re looking for a “nitty gritty” detail course on Amazon Web Services and Amazon VPC you can view our AWS Certified Solutions Architect – Associate Level course module over at The Linux Academy. Now, we can get started.