You created NICs for the management and external subnets when you deployed the instance. Stepįrom the AWS Marketplace, choose an F5 BIG-IP VE image. Now deploy a BIG-IP VE instance and configure basic networking for it. BIG-IP VE uses these ports for config sync and failover. You can choose My IP from the Source list to select your computer’s public IP address.Īn internal IP address, for example 10.0.0.0/16. PurposeĪdministrator’s IP address on a secure network. Leave outbound traffic for each group as the default (all). In the Navigation pane, under Security, select Security Groups.Ĭreate three groups associated with the VPC, based on the following information. In AWS, from the Services menu at the top of the screen, select VPC. This specific configuration uses three security groups: one for the BIG-IP Configuration utility, one for virtual server traffic, and one for internal traffic. You can create security groups based on your needs. These groups determine which traffic can travel in and out of the VPC.Īmazon security groups control the inbound and outbound traffic allowed by an EC2 instance. NAT instance and associated network interface.Īdd routes so BIG-IP VE can access the InternetĪdd the private IP address of the external subnet as the gateway in a route for outbound traffic.External subnet (called Private in the AWS UI): 10.0.1.0/24.Management subnet (called Public in the AWS UI): 10.0.0.0/24.Use the VPC wizard to create a management subnet for administrative access, an external subnet for application access, and a NAT instance for network translation. This is the network environment where your instances will reside. To create a multi-NIC configuration, you must first create an Amazon virtual private cloud (VPC).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |