{"id":15713,"date":"2025-09-15T18:14:29","date_gmt":"2025-09-15T12:44:29","guid":{"rendered":"https:\/\/www.skynats.com\/?p=15713"},"modified":"2025-09-15T18:14:31","modified_gmt":"2025-09-15T12:44:31","slug":"aws-inter-region-vpc-peering-for-rds-replica-access","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/aws-inter-region-vpc-peering-for-rds-replica-access\/","title":{"rendered":"\u00a0AWS Inter-Region VPC Peering for RDS Replica Access"},"content":{"rendered":"\n<ul class=\"wp-block-list\">\n<li>VPC Peering in AWS allows private communication between instances in different Virtual Private Clouds (VPCs).<\/li>\n\n\n\n<li>It supports secure and low-latency network connectivity without requiring public IPs or VPNs.<\/li>\n\n\n\n<li>This <a href=\"https:\/\/aws.amazon.com\/\" target=\"_blank\" rel=\"noopener\"><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-secondary-color\">aws<\/mark><\/a> vpc peering setup especially useful when setting up Amazon RDS read replicas across regions.<\/li>\n\n\n\n<li>With inter-region VPC peering, an application in one region can connect to an RDS replica in another region securely.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\" id=\"h-create-an-rds-read-replica-in-another-region\"><strong>Create an RDS Read Replica in Another Region<\/strong><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to the RDS Console.<\/li>\n\n\n\n<li>Select your primary RDS instance.<\/li>\n\n\n\n<li>Click Actions ,then Create Read Replica.<\/li>\n\n\n\n<li>Choose a different region ( for example , us-west-2).<\/li>\n\n\n\n<li>Select a subnet group in the target VPC.<\/li>\n\n\n\n<li>Launch the replica.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\" id=\"h-create-inter-region-vpc-peering-connection\"><strong>Create Inter-Region VPC Peering Connection<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Go to VPC Dashboard in the source region (us-east-1):<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Navigate to Peering Connections , then choose Create Peering Connection.<\/li>\n\n\n\n<li>Enter a name.<\/li>\n\n\n\n<li>Choose the requester VPC (us-east-1) and accepter VPC (us-west-2).<\/li>\n\n\n\n<li>Select the appropriate account and VPC in the target region.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Accept the peering request in the target region\u2019s VPC dashboard (us-west-2).<\/p>\n\n\n\n<h2 class=\"wp-block-heading has-small-font-size\" id=\"h-update-route-tables\"><strong>Update Route Tables<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Each VPC must be aware of how to route traffic to the other:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In us-east-1:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Go to the route table associated with the subnet your app resides in.<\/li>\n\n\n\n<li>Add a route:<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Destination: 10.1.0.0\/16 (CIDR of target VPC)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Target: Peering Connection ID<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In us-west-2:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do the same, but route to 10.0.0.0\/16.<\/p>\n\n\n\n<h3 class=\"wp-block-heading has-small-font-size\" id=\"h-modify-security-groups\"><strong>Modify Security Groups<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Adjust security groups to allow communication.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the RDS read replica\u2019s security group (us-west-2):<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Add an inbound rule allowing traffic from the source VPC&#8217;s subnet\/IP range (10.0.0.0\/16) on the appropriate port (e.g., 5432 for PostgreSQL).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On your application\u2019s security group (us-east-1), allow outbound traffic to the target VPC subnet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Test the Connection<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On an EC2 instance in the us-east-1 VPC, try to connect:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mysql -h &lt;read-replica-endpoint&gt; -u &lt;user&gt; -p<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Inter-region VPC peering is a powerful AWS networking feature that enables secure and efficient communication between VPCs in different regions. When used with Amazon RDS read replicas, it allows applications to access remote replicas without exposing them to the public internet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Need expert help setting up AWS VPC Peering for seamless RDS replica access across regions? Our team at Skynats specializes in reliable <a href=\"https:\/\/www.skynats.com\/aws-management\/\">AWS Management Services<\/a>, ensuring secure, optimized, and highly available cloud infrastructure. Contact us today to simplify your AWS networking and database replication needs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Create an RDS Read Replica in Another Region Create Inter-Region VPC Peering Connection Go to VPC Dashboard in the source region (us-east-1): Accept the peering request in the target region\u2019s VPC dashboard (us-west-2). Update Route Tables Each VPC must be aware of how to route traffic to the other: In us-east-1: Destination: 10.1.0.0\/16 (CIDR of [&hellip;]<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[1028,722,1006,773,1105,1007],"class_list":["post-15713","post","type-post","status-publish","format-standard","hentry","category-blog","tag-amazon-rds","tag-aws","tag-aws-management-services","tag-rds","tag-rds-replica-access","tag-vpc-peering"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15713","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=15713"}],"version-history":[{"count":2,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15713\/revisions"}],"predecessor-version":[{"id":15716,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/15713\/revisions\/15716"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=15713"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=15713"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=15713"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}