Applies To:

Show Versions Show Versions

Manual Chapter: Deploying BIG-IQ Virtual Edition
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

About VE EC2 deployment

To deploy the BIG-IQ Virtual Edition (VE) system on EC2, you perform these tasks:

  • Verify the host machine requirements.
  • Deploy a BIG-IQ system as a virtual machine.
  • Deploy a BIG-IP system.
  • After you have deployed the virtual machines, log in to the BIG-IQ VE system and run the Setup utility. Using the Setup utility, you perform basic network configuration tasks, such as assigning VLANs to interfaces.
  • Configure secure communication between the BIG-IQ system and the BIG-IP device.

Task summary for EC2 deployment

To deploy BIG-IQ Cloud using the Amazon elastic compute cloud (EC2) public cloud virtual machine management service, you perform a series of tasks using Amazon Web Services (AWS).

Task list

Creating a key pair

Before you can deploy a virtual machine on Amazon Web Services (AWS) Elastic Cloud Computing, you need an AWS account.

To create a virtual private cloud (VPC) on which you can deploy the BIG-IQ system, you need a (private-public encryption) key pair to authenticate your sessions. Key pairs are reusable, so if you have a key pair, you do not need to repeat this task.

For the most current instructions for creating a key pair, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site, http://aws.amazon.com/documentation/vpc/.
Important: It is crucial to your success that you be consistent in the region that you choose throughout the configuration process. Objects configured in one region are not visible within other regions, so they cannot function together. There are a number of factors that determine which region will best suit your requirements. Refer to Amazon user documentation for additional details.
The file that downloads from Amazon Web Services uses the extension .pem. If you plan to use this key pair with the PuTTY terminal emulator application, you will need to convert the key pair from a .pem to a .ppk file. At the time of this release, PuTTY does not support the extension .pem. PuTTY does have a tool (called PuTTYgen) that converts your key pair to the required PuTTY format.

Creating a new virtual private cloud

You need a virtual private cloud (VPC) to deploy the BIG-IQ Cloud system because Amazon Web Services (AWS) only provides multiple network interface card (NIC) support for EC2 instances that reside within a VPC.

For the most current instructions for creating a Virtual Private Cloud, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site, http://aws.amazon.com/documentation/vpc/.
Important: It is crucial to your success that you be consistent in the availability zone that you choose throughout the configuration process. Objects configured in one zone are not visible within other zones, so they cannot function together.
Important: The first choice you have when creating a VPC is to select a VPC configuration. Choose the VPC with Public and Private Subnets option.

Adding an additional subnet

When you create a VPC, Amazon Web Services creates two subnets (Management and External) for it. Many network topologies require three or more subnets (Management, External, and Internal).

For the most current instructions for creating an internal subnet, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site http://aws.amazon.com/documentation/vpc/.
If you are following a typical deployment strategy, when you finish adding the Internal subnet, your VPC will have three subnets.
  • a Management subnet on 10.0.0.0/24
  • an External subnet on 10.0.1.0/24
  • an Internal subnet on 10.0.2.0/24

Creating new security groups

To use your virtual private cloud (VPC) to deploy your virtual machine, the VPC needs two security groups; each with its own set of rules that govern the security behavior for the traffic that routes through it. The table details the rules required for each group to function properly.

Group Name Group Description Rule Name Source Rule Type
allow-only-ssh-https-ping Allow only SSH HTTPS or PING Inbound SSH 0.0.0.0/0  
    Inbound HTTPS 0.0.0.0/0  
    Inbound Custom ICMP 0.0.0.0/0 Echo Request
    Outbound Custom ICMP 0.0.0.0/0 Echo Request
    Outbound Custom ICMP 0.0.0.0/0 Echo Reply
allow-all-traffic Allow all traffic Inbound All Traffic 0.0.0.0/0  
    Outbound All Traffic 0.0.0.0/0  
  1. Create two security groups, one named allow-only-ssh-https-ping and the other named allow-all traffic.
    Tip: For the most current instructions for creating security groups, refer to the Amazon Virtual Private Cloud (VPC) Documentation web site http://aws.amazon.com/documentation/vpc/.
    Important: The allow-all-traffic security group is critically important for successful operation of the BIG-IP VE on Amazon EC2.
  2. For each security group, create the rules described in the preceding table. For each rule, define the Group Description, Rule Name, Source, and Rule Type as shown in the table.
    Important: No punctuation is permitted in the text of the Group Description that you type in.
When you finish adding the two groups and their associated rules, your VPC should be ready to go with three subnets and two security groups.

It is a good idea to test connectivity before proceeding. You should be able to communicate with your VPC NAT server at this point.

F5 Networks recommends enhancing your security by using the security group source fields to restrict the subnets to allow only management access; however, we recognize that this does not complete your security solution. For enhanced security, you may want to deploy a topology with limited management network access.

Adding a route for external subnet accessibility

Most network topologies require an Amazon Web Services route to the virtual private cloud (VPC) that makes the external subnet used by the virtual machine accessible to the Internet.

  1. From the Services tab at the top of the Amazon Web Services Management Console screen, select VPC.
  2. In the navigation pane, select Route Tables. The Route Tables screen opens.
  3. Select the routing table with one subnet.
  4. Click the Associations tab at the bottom of the window.
  5. From the Select a subnet list, select the 10.0.1.0/24 subnet.
  6. Click Associate. The Associate Route Table dialog box opens.
  7. Click Yes, Associate.

Launching a new virtual machine

You need to know the name of your key pair and the Availability Zone from which they were created before you can complete this task.

You need to have an EC2 Amazon Machine Image (AMI) to deploy the virtual machine.

Important: At publication, this task illustrates the Amazon web interface. However, F5 recommends that you refer to Amazon user documentation for the latest documentation.
  1. Log in to your account on Amazon Web Services (AWS) marketplace.
  2. In the Search AWS Marketplace bar, type F5 BIG-IQ and then click GO. The F5 BIG-IQ Virtual Edition for AWS option is displayed.
  3. Click F5 BIG-IQ Virtual Edition for AWS and then click CONTINUE.
    Tip: You might want to take a moment here to browse the pricing details to confirm that the region in which you created your security key pair provides the resources you require. If you determine that the resources you need are provided in a region other than the one in which you created your key pair, create a new key pair in the correct region before proceeding.
    The Launch on EC2 page is displayed.
  4. Click the Launch with EC2 Console tab.
    Important: At the time this was written, the virtual machine must be launched in a VPC so that NICs can be attached. This configuration is supported from the Launch with EC2 Console option, but not the 1-Click Launch option.
    Launching Options for your EC2 AMI are displayed.
  5. Select the software version appropriate for your installation and then click the Launch with EC2 button that corresponds to the Region that provides the resources you plan to use.
    Important: The first time you perform this task, you need to accept the terms of the end user license agreement before you can proceed, so the Launch with EC2 button reads Accept Terms and Launch with EC2.
    Important: There are a number factors that determine which region will best suit your requirements. Refer to Amazon user documentation for additional detail. Bear in mind that the region you choose must match the region in which you created your security key pair.
    The Request Instances Wizard opens.
  6. Select an Instance Type appropriate for your use.
  7. From the Launch Instances list, select VPC.
  8. From the Subnet list, select the 10.0.0.0/24 subnet and then click CONTINUE. The Advanced Instance Options view of the wizard opens.
  9. From the Number of Network Interfaces list, select 2.
  10. Click the horizontal eth1 tab to set values for the second network interface adapter, and then from the Subnet list, select the 10.0.1.0/24 subnet, and then click CONTINUE The Storage Device Configuration view of the wizard opens.
  11. In the Value field, type in an intuitive name that identifies this AMI and then click CONTINUE(for example, BIG-IQ VE <version>. The Create Key Pair view of the wizard opens.
  12. From Your existing Key Pairs, select the key pair you created for this AMI, and then click CONTINUE. The Configure Firewall view of the wizard opens.
  13. Under Choose one or more of your existing Security Groups, select the allow-all-traffic security group, and then click CONTINUE. The Review view of the wizard opens.
  14. Confirm that all settings are correct, and then click Launch. The Launch Instance Wizard displays a message to let you know your instance is launching.
  15. Click Close.
Your new AMI appears in the list of instances when it is fully launched.

Adding a third network interface

When you first create a virtual private cloud (VPC), there are typically only two network interfaces associated with it. F5 Networks recommends adding a third network interface to the VPC before you use it to deploy the virtual machine.

  1. From the Services tab at the top of the Amazon Web Services (AWS) Management Console screen, select EC2.
  2. In the navigation pane, select Network Interfaces. The Network Interfaces screen opens.
  3. Click the Create Network Interface button (at top left). The Create Network Interface dialog box opens.
  4. In the Description field, type Internal 10.0.2.0-24 (or a similarly mnemonic name).
  5. In the Subnet field, select 10.0.2.0/24.
  6. From the Security Groups list, select allow-all-traffic.
  7. Click Yes, Create AWS adds your network interface to the list.
  8. Right-click the new network interface, and then select Attach. The Attach Network Interface dialog box opens.
  9. From the Instance list, select the VE AMI that you created.

Making the virtual machine management port accessible

The management port for your virtual machine may require accessibility over the Internet. However, there are alternative topologies that do not require exposing the management port to the Internet.

F5 Networks recommends, at a minimum, adding restrictions to your source addresses in the allow-only-ssh-https-ping security group.

Alternatively, you may find the Amazon Web Services EC2 VPN sufficiently effective so that you do not need to associate an Internet-accessible Elastic IP with the management port.

  1. From the Services tab at the top of the Amazon Web Services Management Console screen, select EC2.
  2. In the navigation pane, select Elastic IPs. The Addresses screen opens.
  3. Click Allocate New Address. The Allocate New Address dialog box opens.
  4. From the EIP used in list, select VPC.
  5. Click Yes, Allocate.
  6. In the Address column, right-click the newly created Elastic IP and select Associate from the popup menu. The Associate Address dialog box opens.
  7. From the Instance list, select the VE AMI that you created as an EC2 hypervisor.
  8. From the Private IP Address list, select 10.0.0.0/24 (the Management subnet).
  9. Click Yes, Associate.

Logging in and setting the Admin password

To perform this task, you must have completed the following tasks:
  • Created a key pair
  • Created and configured a VPC
  • Instantiated and launched a BIG-IQ Virtual Edition (VE) AMI
  • Made the virtual machine management port accessible through the Internet

To maintain security, the first time you log in to your EC2 AMI, you should log in as root, and change the Admin password.

  1. Log in to the new AMI that you just launched. Use the name of the key pair (.pem file), and the elastic IP address of your EC2 instance. $ ssh -i <username>-aws-keypair.pem root@<elastic IP address of EC2 instance>
    Tip: You can also use a terminal emulator such as PuTTY to test your connectivity. At publication, PuTTY does not support the extension .pem, so remember that you will also need to convert the key pair .pem file to a .ppk file before you can use it with PuTTY.
  2. At the command prompt, type tmsh modify auth password admin.
    Warning: Because this login is visible externally, make sure to use a strong, secure password.
    The terminal window displays the message: changing password for admin, and then prompts: new password.
  3. Type in your new password and then press Enter. The terminal window displays the message: confirm password.
  4. Re-type the new password and then press Enter.
  5. To ensure that the system retains the password change, type tmsh save sys config, and then press Enter.
    Important: Without your security key pair, you cannot access this AMI. Once you log in with your key pair, you could create a root password. However, if you decide to do this, choose the root password wisely, bearing in mind that depending on your Security Group policies, this login may provide external SSH access.
The Admin password is now changed.
Tip: If at some point you determine you want to restore your virtual machine to its default state, use the following tmsh command:tmsh load sys config default; bigstart restart dhclient Using a less explicit tmsh command has been shown to produce undesirable results.
Table of Contents   |   << Previous Chapter   |   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)