Now deploy a BIG-IP® VE instance and configure basic networking for it.
|1||Deploy a BIG-IP VE instance||From the AWS Marketplace, choose an F5® BIG-IP VE image. Ensure you add an extra, external NIC, and assign an IAM role if you intend to do high availability.||
|2||Create an internal network interface||You created NICs for the management and external subnets when you deployed the instance. You must create an internal NIC and reboot, so BIG-IP VE can recognize the new NIC, and hourly instances can license with F5.||Internal interface: eth2, primary private IP: 10.0.2.200|
|3||Create an Elastic IP address for the BIG-IP Configuration utility||An EIP address is a publicly-routable address that provides access to the BIG-IP Configuration utility. If the BIG-IP VE is rebooted, stopped, or terminated, the EIP address persists on that NIC.||EIP: 52.x.y.x|
|4||Assign a secondary private IP address to the external interface||This is the address BIG-IP VE will use for the virtual IP address.||Secondary private IP: 10.0.1.202|
|5||Create an Elastic IP address for the virtual server||You must create an EIP address and associate it with the secondary private IP address of the external subnet. This will make the virtual server accessible from the Internet.||EIP: 52.x.y.x|
When you created the BIG-IP® VE instance, you associated two network interfaces with it (one for management and one for external). To connect BIG-IP VE with your internal servers, create an internal network interface, and attach it to your BIG-IP VE instance.