Another deployment type, termed "Full-Public-Cloud," places the Grid Master and all Grid members in the organization's AWS public cloud. In this example, the VPC peering model is used to illustrate a full Grid deployment.
Figure 1.2 illustrates Infoblox vNIOS for AWS support for a Full-Public-Cloud with multiple VPCs.
Figure 1.2 Full Public Cloud Deployment Example
Characteristics of this deployment include the following:
- A Grid Master runs in the Shared Services VPC;
- Numerous VPCs can operate in this type of deployment; the main AWS restriction is that all VPCs peering with one another must have direct connections to each another in the same region. The topology is typically a hub-and-spoke, with the Shared Service VPC as the hub;
- User access to the Grid Master and NIOS is performed through the Amazon regional service endpoint;
- Each Infoblox vNIOS for AWS instance can be set to be authoritative for the VPC of which it is a part;
- You do not need to deploy Infoblox vNIOS for AWS instances in every VPC involved in a peering arrangement. The number and placement of Infoblox vNIOS for AWS instances should be based upon expected network object counts and expected volume of DNS query traffic generated by each of the peered VPCs;
- All VPCs are discovered and managed by default in the same Network View.
Figure 1.3 illustrates Grid management of multiple VPCs across two or more AWS Regions.
Figure 1.3 Routed Shared Service/Peered VPCs
Characteristics of this deployment type include the following:
- A Grid Master runs in the on-premises network, which routes between each of the multiple Shared Services VPCs;
- The on-premise Grid Master or Grid member can act as the AWS API Proxy for each of regional Peered/Shared Service VPC. This is a recommended configuration due to the appliance's proximity to the administrator performing the API calls;
- The NIOS Grid extends across the organization's on-premise sites and the AWS Peered/Shared Service VPCs;
- Each Infoblox vNIOS for AWS instance can be set to be authoritative for the VPC of which it is a part;
- Each Shared Services/Peered VPC instance from each AWS Region is managed through a separate Network View in NIOS;
- You do not need to deploy Infoblox vNIOS for AWS instances in every VPC involved in a peering arrangement. The number and placement of Infoblox vNIOS for AWS instances should be based upon expected network object counts and volume of DNS query traffic generated by each of the peered VPCs
- All VPCs are discovered and managed by default in the same Network View.