skip to Main Content

Say I have a vpc with network 10.130.0.0/16.

Is there anyway to isolate subnets within this /16 so that they cannot be routed between one another?

say I have 10.130.1.0/24 and 10.130.2.0/24 and I don’t want them to talk to each other- is this possible?

I see the entire network as "local" when creating these subnets – would I need to move them out of the vpc to have isolation?

2

Answers


  1. Yes, you can use Network ACLs to block traffic between subnets.

    Login or Signup to reply.
  2. Yes, you can isolate subnets by preventing them to be routable to each other.

    All subnets created within the VPC are by default associated with the default main route table. You can, however, create custom route tables and you can associate them to the subnets as required.

    From the documentation:

    Your VPC has an implicit router, and you use route tables to control where network traffic is directed. Each subnet in your VPC must be associated with a route table, which controls the routing for the subnet (subnet route table). You can explicitly associate a subnet with a particular route table. Otherwise, the subnet is implicitly associated with the main route table. A subnet can only be associated with one route table at a time, but you can associate multiple subnets with the same subnet route table.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search