This video will demonstrate how NetScaler VPX can be deployed in AWS and leverage CloudFormations to synchronize NetScaler vserver instances with an application’s back end autoscaling group in AWS.
This integration eliminates the need to manually provision services on NetScaler in response to Auto Scale in AWS.
You can launch a Citrix NetScaler VPX instance on Amazon Web Services (AWS). The NetScalerVPX appliance is available as an Amazon Machine Image (AMI) in AWS marketplace. A NetScalerVPX instance on AWS enables customer like you to leverage AWS Cloud computing capabilities and use NetScaler load balancing and traffic management features for their business needs. The VPX instance supports all the traffic management features of a physical NetScaler appliance, and they can be deployed as standalone instances or in HA pairs.
How a NetScaler VPX Instance on AWS Works
The NS VPX is available as an AMI in AWS marketplace, and it can be launched as an EC2 instance within an AWS VPC. The VPX AMI instance requires a minimum of 2 virtual CPUs and 2 GB of memory. An EC2 instance launched within an AWS VPC can also provide the multiple interfaces, multiple IP addresses per interface, and public and private IP addresses needed for VPX conﬁguration. Each VPX instance requires at least three IP subnets:
- A NetScaler Management subnet
- A client-facing subnet (VIP)
- A back-end facing subnet (SNIP,MIP, etc.)
Citrix recommends three network interfaces for a standard VPX on AWS installation.
AWS currently makes multi-IP functionality available only to instances running within an AWS VPC. A VPX instance in a VPC can be used to load balance servers running in EC2 instances. An Amazon VPC allows you to create and control a virtual networking environment, including your own IP address range, subnets, route tables, and network gateways.