AWS VPC Peering – Certification

VPC Peering Overview

  • A VPC peering connection is a networking connection between two VPCs that enables routing of traffic between them using private IP addresses.
  • Instances in either VPC can communicate with each other as if they are within the same network
  • VPC peering connection can be established between your own VPCs, or with a VPC in another AWS account in a single different region.
  • AWS uses the existing infrastructure of a VPC to create a VPC peering connection; it is neither a gateway nor a VPN connection, and does not rely on a separate piece of physical hardware.
  • There is no single point of failure for communication or a bandwidth bottleneck

VPC Peering Rules & Limitations

  1. VPC peering connection cannot be created between VPCs that have matching or overlapping CIDR blocks.
  2. VPC peering connection cannot be created between VPCs in different regions. (NOTEVPC Peering is now supported inter-region.)
  3. VPC peering connection are limited on the number active and pending VPC peering connections that you can have per VPC.
  4. VPC peering does not support transitive peering relationships. In a VPC peering connection, the VPC does not have access to any other VPCs that the peer VPC may be peered with even if established entirely within your own AWS account
  5. VPC peering does not support Edge to Edge Routing Through a Gateway or Private Connection
  6. In a VPC peering connection, the VPC does not have access to any other connection that the peer VPC may have and vice versa. Connections that the peer VPC can include
    1. A VPN connection or an AWS Direct Connect connection to a corporate network
    2. An Internet connection through an Internet gateway
    3. An Internet connection in a private subnet through a NAT device
    4. A ClassicLink connection to an EC2-Classic instance
    5. A VPC endpoint to an AWS service; for example, an endpoint to S3.
  7. Only one VPC peering connection can be established between the same two VPCs at the same time
  8. Maximum Transmission Unit (MTU) across a VPC peering connection is 1500 bytes.
  9. A placement group can span peered VPCs that are in the same region; however, you do not get full-bisection bandwidth between instances in peered VPCs
  10. Any tags created for the VPC peering connection are only applied in the account or region in which they were created
  11. Unicast reverse path forwarding in VPC peering connections is not supported
  12. Instance’s public DNS hostname does not resolve to its private IP address across peered VPCs.
  13. Circa July 2016, Instance’s Public DNS can now be resolved to its private IP address across peered VPCs

VPC Peering Architecture

AWS VPC Architecture
  • VPC Peering can be applied to create shared services or perform authentication with an on-premises instance
  • This would help creating a single point of contact, as well limiting the VPN connections to a single account or VPC

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. A company has an AWS account that contains three VPCs (Dev, Test, and Prod) in the same region. Test is peered to both Prod and Dev. All VPCs have non-overlapping CIDR blocks. The company wants to push minor code releases from Dev to Prod to speed up time to market. Which of the following options helps the company accomplish this?
    1. Create a new peering connection Between Prod and Dev along with appropriate routes.
    2. Create a new entry to Prod in the Dev route table using the peering connection as the target.
    3. Attach a second gateway to Dev. Add a new entry in the Prod route table identifying the gateway as the target.
    4. The VPCs have non-overlapping CIDR blocks in the same account. The route tables contain local routes for all VPCs.

31 thoughts on “AWS VPC Peering – Certification

    1. Hi Veeresha, frankly speaking from my experience it might just be enough to clear as it covers most of the stuff for Associate exams.

  1. Hi jayendra,
    Thanks for wonderful blog…. it helping…..
    What are the certifications u cleared??
    Hi Veeresha,
    Have u cleared the exam??

      1. Hi Jayendra, Thanks first of all and appreciate your efforts to put in the AWS knowledge on this nicely organized portal. Just would like to check if your block contents are constantly updated now a days ( Jan 18 ) ?

        1. Most of the contents are updated and they are constantly updated as well.
          Key points to remember – AWS have enhancements every other day and the exams do not reflect the same.

      1. Congrts Amit !!!. Amit, I am also planning to appear SA exam in near future. could you please help me what questions were appeared in the exam ? cloud guru is sufficient to clear exam ?

        Your response will be really helpful to me

        My email is


        1. Thank u Senthil…
          I dont remembered all the questions. But more were from EBS and S3. and few from VPC… exam was looks very easy…
          Cloud guru course is good.. but not enough… u need to read all faqs and this blogs…

  2. Can you help with this q?

    A company has configured and peered two VPCs: VPC-1 and VPC-2. VPC-1 contains only private subnets, and VPC-2 contains only public subnets. The company uses a single AWS Direct Connect connection and private virtual interface to connect their on-premises network with VPC-1. Which two methods increases the fault tolerance of the connection to VPC-1? Choose 2 answers:

    A.Establish a hardware VPN over the internet between VPC-2 ana the on-premises network.

    B.Establish a hardware VPN over the internet between VPC-1 and the on-premises network.

    C.Establish a new AWS Direct Connect connection and private virtual interface in the same region as VPC-2.

    D.Establish a new AWS Direct Connect connection and private virtual interface in a different AWS region than VPC-1.

    E.Establish a new AWS Direct Connect connection and private virtual interface in the same AWS region as VPC-1

    1. Would go for B & E as Direct Connect connections are not redundant and you need to provide fault tolerance either by setting up a second Direct Connect connection or using VPN. Also, the connection should be to the same VPC as even though the VPC are peered, you cannot connect from one VPC to other.

    1. As the connections are non transitive, a route table entry would not work and you would need to set a new peering connection between prod and dev.

      1. Hello Jayendra,

        The answer “a” also tends to transitive peering i.e. test prod and test dev so ideally we should not be doing transitive peering between prod dev .
        Could you please explain how “a” option suits the best .

  3. Using shared VPCs, you can mount an Amazon EFS file system that is owned by one account from Amazon EC2 instances that are owned by a different account.

  4. hi Jayendra..going through this blog and CLOUDGURU Course and cloud guru mentioned whitepapers is enough for the certification???

    1. Tharks Marek, yup Public DNS resolution within VPC peering seems to be supported now. Will update the blog.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.