大网数据广告活动
服务器运维问答

AWS VPN-only subnet in a VPC with private and public subnets

· 52CE 我爱测

I have a VPC (10.0.0.0/16) with public (10.0.1.0/24) and private (10.0.2.0/24) subnets. I have ELBs in the public subnet and EC2 Webservers in the private one. I've also setup a VPN Gateway, Consumer Gateway and a VPN connection …

问题原文

原帖链接 · Hesham · CC BY-SA 3.0

I have a VPC (10.0.0.0/16) with public (10.0.1.0/24) and private (10.0.2.0/24) subnets. I have ELBs in the public subnet and EC2 Webservers in the private one. I've also setup a VPN Gateway, Consumer Gateway and a VPN connection to allow a client to access our VPC.

How do I lock down the VPN connection to a subnet that is dedicated only for VPN (VPN-only subnet). I am planning to have EC2 instances in the VPN-only subnet and the client should be able to access those servers.

Thanks!

已采纳解答

原帖链接 · chris · CC BY-SA 3.0

First off, you should have multiple public and multiple private subnets.

The routes for the public subnets should have 0.0.0.0/0 targeting the IGW, which you don't mention in your question.

The private subnets can do the same - 0.0.0.0/0 should target the VGW.

Because the local route cannot be edited, and points to the CIDR block for the entire VPC, if you want to restrict access between public and private subnets, you will need to have Network ACLs on your subnets to deny undesired traffic. The same mechanism could be used to restrict traffic coming in from the VPN.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-11-17)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。