Applies To:

Show Versions Show Versions

Manual Chapter: Getting Started with BIG-IP Virtual Edition in AWS
Manual Chapter
Table of Contents   |   Next Chapter >>

Sample multi-NIC configuration for BIG-IP VE in AWS

The following diagram shows a basic multi-NIC deployment of BIG-IP® VE in an Amazon Virtual Private Cloud (VPC).

Complete the tasks in this guide to create this deployment.

Note: Alternately, you can use CloudFormation templates to create this deployment. For more information about CloudFormation templates provided by F5®, go to https://github.com/F5Networks.
This deployment shows three subnets:
  • An external, public subnet, where you'll create a virtual server to accept Internet traffic.
  • An internal, private subnet, where your application servers live.
  • A management subnet, where you can access the BIG-IP Configuration utility; the Configuration utility is used to configure BIG-IP VE.
Traffic flows from clients through BIG-IP VE to application servers.

All IP addresses and network interfaces are created in AWS. Then in BIG-IP VE, you create corresponding objects for the same IP addresses, represented by the shaded boxes in the diagram.

If you want to create a deployment with a single NIC, Auto Scaling, or high availability, see the respective guides on the AskF5™ Knowledge Base at askf5.com.

Amazon EC2 instances for BIG-IP VE

When you deploy BIG-IP® VE, you have to choose an Amazon instance type. The type you choose is based on how many F5® modules you want to run, how much throughput you need, how many vNICs you need, and how much vCPU and storage you require. You should choose an F5 license and Amazon instance type before deploying BIG-IP VE.

Good Licenses

If you choose a Good image, you can use the following AWS EC2 instance types.

AWS instance vCPUs Memory (GiB) Max # of vNICs
t2.medium* 2 4 3
t2.large* 2 8 3
m3.medium* 1 3.75 2
m3.large 2 7.5 3
m4.large 2 8 2
c3.xlarge 4 7.5 4
c4.xlarge 4 7.5 4

*25 Mbps and 200 Mbps licenses only.

With a Good license, you can also use any of the instance types recommended for Better or Best, though the license determines the maximum vCPU that can be used. For maximum limits for each F5 module, see https://support.f5.com/csp/article/K14810 in the AskF5™ Knowledge Base (http://support.f5.com).

Better Licenses

If you choose a Better image, you can use the following AWS EC2 instance types.

AWS instance vCPUs Memory (GiB) Max # of vNICs
t2.medium* 2 4 3
t2.large* 2 8 3
m3.large 2 7.5 3
m4.large 2 8 2
c3.xlarge 4 7.5 4
c4.xlarge 4 7.5 4
m3.xlarge 4 15 4
m4.xlarge 4 16 4
c3.2xlarge 8 15 4
c4.2xlarge 8 15 4

You can also use any of the recommended types for Best, though the license determines the maximum vCPU that can be used.

Best Licenses

If you choose a Best image, you can use the following AWS EC2 instance types. You can also use any instance type listed for Better.

Note: The license determines the maximum vCPU that can be used.
AWS instance vCPUs Memory (GiB) Max # of vNICs
m3.2xlarge 8 30 4
m4.2xlarge 8 32 4
m4.4xlarge 16 64 8
m4.10xlarge 40 160 8
c3.4xlarge 16 30 8
c3.8xlarge 32 60 8
c4.4xlarge 16 30 8
c4.8xlarge 36 60 8
cc2.8xlarge 32 60.5 8

Performance may vary (based on things like region, instance type, traffic profile, functionality enabled, etc.). You may not need all licensed vCPUs to get the performance you need.

If necessary, you can resize the instance after you deploy. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html for details.

Standalone Modules

For standalone modules, choose an image based on the following information. Supported AWS EC2 instances are the same as listed in the tables above.

Module Image (BYOL Instances) Image (Utility Instances)
DNS Good, Better, or Best Better or Best
AFM Better or Best Better or Best
ASM Best* Best
APM Best* Best

*Best is recommended but Better may be used. However, Better may not be supported in later versions of BIG-IP VE.

Create an SSH key pair

To access Amazon EC2 instances, you must have an SSH key pair. You can create one in the AWS console or import a key pair if you already have one.

  1. In AWS, note the region where you are logged in. Everything you create in the console going forward must be in the same region.
  2. From the Services menu at the top of the screen, select EC2.
  3. In the Navigation pane, under NETWORK & SECURITY, select Key Pairs.
  4. Click Create Key Pair.
  5. Enter a name and click Create.
    A .pem file is downloaded to your computer. Save this file somewhere secure where you can find it later.
Later, you will use PuTTY to access your EC2 instance. Use PuTTYgen to convert the .pem file to .ppk format.
Table of Contents   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)