**Points of My Scenario:** 1. I tried to create 3 private subnets (subnets without an internet gateway) so that EC2 instances would be unable to access Internet 2. I used the procedure in AWS document https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html 3. Upon completion, I checked the route table for each subnet... 4. Alas! Each one had destination 0.0.0.0/0 associated with the default igw-: just like the other system-generated subnets. **Question:** why is this happening and how can I create truly private subnets?

How to create a no-internet access (private) subnet?

Points of My Scenario:

I tried to create 3 private subnets (subnets without an internet gateway) so that EC2 instances would be unable to access Internet
I used the procedure in AWS document https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html
Upon completion, I checked the route table for each subnet...
Alas! Each one had destination 0.0.0.0/0 associated with the default igw-<GUID>: just like the other system-generated subnets.

Question: why is this happening and how can I create truly private subnets?

トピック

ネットワークとコンテンツ配信

タグ

Amazon VPC

言語

English

waltforbes

質問済み 1年前658ビュー

1回答

新しい順
投票が多い順
コメントが多い順

承認された回答

In your VPC is a default route table. The instructions on that page don't mention it but if you don't assign a specific route table to a subnet the default is used. In your case, the default route table has a route to the Internet Gateway.

To fix this, create a new route table in your VPC and assign it to the private subnets.

エキスパート

Brettski-AWS

回答済み 1年前

エキスパート

AWS-User-Nitin

レビュー済み 1年前

waltforbes
1年前
OMG! That's it! That works! A bundle of thanks, Brettski-AWS!

How to create a no-internet access (private) subnet?

関連するコンテンツ