
上QQ阅读APP看书,第一时间看更新
Private hosted zones
This zone should contain all records that will be used by the internal users. Generally, in AWS, whenever we create a private hosted zone, it has to be associated to a VPC.
This means that all the records that we put in a Private Hosted Zone will be resolved by the EC2 instances within the VPC. This is illustrated in the following diagram:

In the following screenshot, we have created a new private hosted zone. Note the Type section and the VPC ID:
- Type: This can be either a public hosted zone or a private hosted zone
- VPC ID: This private zone will be associated with VPC. All EC2 instances within VPC will be able to resolve domains under these zones:
