I'm testing some cloudformation infrastructure templates, and I noticed that most of the examples include routing tables to connect private subnets to public subnets, but my question then is:

if two private subnets exist in different AZs (and are attached to individual routing tables) and the resources within them may need to access a resource on the other subnet (for example a private service on the subnet 1 accessing a database on the subnet 2)

  1. Should I create a route to connect the two private subnets in each of their routing tables?
  2. Would it be a better practice to attach both subnets to a single shared routing table (both CIDRs are contiguous)?
  • Both subnets are on the same VPC
    – Manatax
    Commented Aug 9, 2019 at 21:16

1 Answer 1


Are they in the same VPC? If yes it should just work as the VPC CIDR route will take care of all the subnets intercommunication.

  • yes, they are on the same VPC, but if that is the case, then why do I need to connect private a public subnets? take into account I'm not using the default routing table. All subnets currently have their own routing table.
    – Manatax
    Commented Aug 9, 2019 at 21:15
  • I see, I'm not connecting the private to the public, but the private to the NAT in the public...
    – Manatax
    Commented Aug 9, 2019 at 21:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.