如何解决对 AWS VPC 进行子网划分时,按可用区 VS 子网类型划分子网的优缺点是什么?
在 AWS VPC Quickstart 的子网调整部分中讨论的两种情况之间,您为什么要使用其中一种?
第一个场景将 VPC 划分为子网类型,然后按可用区进一步细分。
VPC 10.0.0.0/16
Private subnets A 10.0.0.0/17
---------------------- -------------
Availability Zone 1 10.0.0.0/19
Availability Zone 2 10.0.32.0/19
Availability Zone 3 10.0.64.0/19
Availability Zone 4 10.0.96.0/19
Public subnets 10.0.128.0/18
---------------------- -------------
Availability Zone 1 10.0.128.0/20
Availability Zone 2 10.0.144.0/20
Availability Zone 3 10.0.160.0/20
Availability Zone 4 10.0.176.0/20
Private subnets B ACL 10.0.192.0/19
---------------------- -------------
Availability Zone 1 10.0.192.0/21
Availability Zone 2 10.0.200.0/21
Availability Zone 3 10.0.208.0/21
Availability Zone 4 10.0.216.0/21
Spare subnet capacity 10.0.224.0/19
---------------------- -------------
Availability Zone 1 10.0.224.0/21
Availability Zone 2 10.0.232.0/21
Availability Zone 3 10.0.240.0/21
Availability Zone 4 10.0.248.0/21
第二个场景通过将 VPC 划分为可用区,然后划分为子网类型来分离 CIDR 范围。
VPC 10.0.0.0/16
Availability Zone 1 10.0.0.0/18
---------------------- -------------
Private subnet A 10.0.0.0/19
Public subnet 10.0.32.0/20
Private subnet B 10.0.48.0/21
Spare subnet capacity 10.0.56.0/21
Availability Zone 2 10.0.64.0/18
---------------------- -------------
Private subnet A 10.0.64.0/19
Public subnet 10.0.96.0/20
Private subnet B 10.0.112.0/21
Spare subnet capacity 10.0.120.0/21
Availability Zone 3 10.0.128.0/18
---------------------- -------------
Private subnet A 10.0.128.0/19
Public subnet 10.0.160.0/20
Private subnet B 10.0.176.0/21
Spare subnet capacity 10.0.184.0/21
Availability Zone 4 10.0.192.0/18
---------------------- -------------
Private subnet A 10.0.192.0/19
Public subnet 10.0.224.0/20
Private subnet B 10.0.240.0/21
Spare subnet capacity 10.0.248.0/21
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。