Steps to Create IIP

1. Identify which network of AWS belong to you backend servers. Lets say your NSIP is 192.168.1.1 and NSGW ip is 192.168.2.1 and Backend server/SNIP subnet is 192.168.3.0

2. In AWS EC2 Console > Select NetScaler Instance > Actions > Networking > Manage IP address.

3. Assign the IP which you want to assign for IIP. (This makes sure that the AWS knows that this IP belongs to NetScaler and routes back).
   

4. As per the above screen shot my backend server IP to which we are trying  to connect is 192.168.3.23. Hence, we should take IP in 192.168.3.0 network (192.168.3.229, 3.4,3.213 are few IP and we have used IPs from AWS pool).

5. From this take 192.168.3.213 IP from AWS pool and use it as the intranet IP in the NetScaler Gateway deployment.
   

6. Now let's connect and get 192.168.3.213 as the intranet IP
   

7. We can now successfully open 192.168.3.23.
   

• We can’t assign any user taken IP to intranet IP. We have to make sure the IP which we need to use as IIP has been taken from AWS pool from Manage Ip address
• Backend servers should be reachable from the same interface on which we are taking Manage IP address ( i.e if my backend server is 192.168.3.23 and it is reachable from ethernet2 on NetScaler. Then we should take IPs ( under manage IP address) from ethernet2 only.
• IIP can talk to backend servers but not Internet/Public IP. Accessing Internet or public ip via IIP is having some restrictions on the AWS route topology. It requires lot of manual steps/config and is not 100% successful. For now we can say that IIP supports backend server accessibility but Internet access via IIP is not supported for now.