Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:aws [2023/08/15 08:11] – [NIOS in AWS] bstafford
+++ infoblox_nios:aws [2025/01/14 12:52] (current) – [AMI] bstafford
@@ Line 7: / Line 7: @@
   * TE-4025
   * TE-V5005
+[[https://docs.infoblox.com/space/NAIG/37651026/Infoblox+vNIOS+for+AWS+AMI+Shapes+and+Regions|List of supported AWS images]]
 Network Discovery appliances are not supported in AWS.
@@ Line 18: / Line 20: @@
 ===== AWS x6 =====
+[[https://docs.infoblox.com/space/NAIG/37651026/Infoblox+vNIOS+for+AWS+AMI+Shapes+and+Regions|Documentation]]
 ^ Model ^ VM CPUs ^ VM Memory ^ Image ^
 | TE-926 | 4 | 32Gb | m6i.2xlarge |
@@ Line 28: / Line 31: @@
 ===== AMI =====
-NISO 8.6.2 in eu-west-2 (London) = ''ami-0c6eafc0cb90588fd'' (r4.large)
+NIOS 8.6.2 in eu-west-2 (London) = ''ami-0c6eafc0cb90588fd'' (r4.large)
+===== HA =====
+[[https://docs.infoblox.com/space/NAIG/636354593/Configuring+HA+with+vNIOS+for+AWS+Instances|AWS HA for NIOS]].
 ===== Subnet =====
 AWS allows you to create a subnet in your VPC that uses the same CIDR prefix and mask as for the host VPC, and add new instances to it. For example, consider a VPC CIDR 172.17.0.0/16. In AWS, an administrator is allowed to create a subnet with the same CIDR 172.17.0.0/16 and to run instances within it. NIOS does not allow for subnets in an AWS VPC that use the same prefix and mask as the VPC network container, and does not discover or recognize resources within that subnet. You will also not be able to create new Grid objects in that subnet. Ensure that all VPCs to be managed or discovered through Grid Manager only use subnets with CIDR mask values that are smaller than the CIDR denoting the VPC. For example, the host VPC has a CIDR mask of /16, and the subnets have a mask of /24.
@@ Line 53: / Line 57: @@
 default_admin_password: infoblox
 temp_license: enterprise dns dhcp cloud nios IB-V1425</code>