Subnet Groups and Network Placement
What you'll learn: How to configure subnet groups to control where your managed database lives within your VPC and how it spreads across availability zones.
The Core Idea
When you launch a managed database like Amazon RDS, it doesn't just float in the cloud—it needs a specific home address within your Virtual Private Cloud (VPC). A subnet group is essentially a collection of subnets (network segments) that you've pre-approved as possible locations for your database instances.
Think of it like telling a delivery service: "You can drop off packages at my front door, back door, or side entrance—but nowhere else." The subnet group defines those acceptable drop-off points.
Why This Matters
By creating a subnet group, you:
- Control network placement: Decide which parts of your VPC can host database instances
- Enable high availability: Spread your database across multiple availability zones (different data centers) by including subnets from each zone
- Enforce security boundaries: Keep databases in private subnets, away from direct internet access
- Simplify deployment: Pre-configure networking so launching new databases is consistent
How It Works
You define a subnet group by selecting at least two subnets from different availability zones within the same VPC. When you launch a database instance, you specify which subnet group to use, and the managed service automatically places your database in one of those subnets—or across multiple subnets for Multi-AZ deployments.
Key Takeaway: Subnet groups act as a networking blueprint for your managed databases, defining which VPC subnets can host instances and enabling you to distribute databases across availability zones for resilience and control.