This is an old revision of the document!
Table of Contents
NIOS in AWS
The following appliances are supported in AWS/Azure/GCP
- TE-825
- TE-1425
- TE-2225
- TE-4015
- TE-4025
- TE-V5005
Network Discovery appliances are not supported in AWS.
Only two interfaces are on the AWS appliances - MGMT and LAN1.
AMI
NISO 8.6.2 in eu-west-2 (London) = ami-0c6eafc0cb90588fd (r4.large)
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.
DHCP Service for On-Premises Clients
A vNIOS appliance running on AWS can provide DHCP service for your on-premises clients. This DHCP appliance can serve as your primary DHCP server or be configured as part of a failover pair with a NIOS DHCP server running on-premises for a hybrid, survivable solution. Two vNIOS appliances, each running in AWS could also be configured for DHCP failover for highly available, fault tolerant DHCP services. Using a vNIOS appliance running on AWS for DHCP requires using DHCP Relay or IP Helper on your router or layer 3 switch to send DHCP traffic from your on-premises network to your AWS VPC.
NIOS on AWS
Best PDF on NIOS in AWS is here.
Official documentation is also here.
TE-1425 appliances will use EC2 instance type “r4.xlarge” (4 vCPU, 30.5 GB) and will have a 250 GiB General Purpose SSD (gp2) EBS storage disk.
There are two network interfaces.
Note: In order to use the MGMT interface of your vNIOS for AWS instance, you will need a VPC with two subnets in the same availability zone and the LAN1 and MGMT interfaces must be deployed in separate subnets.
When deploying, you can set defaults
#infoblox-config remote_console_enabled: y default_admin_password: infoblox temp_license: enterprise dns dhcp cloud nios IB-V1425