Applies To:Show Versions
BIG-IQ Centralized Management
- 7.1.0, 7.0.0
Create an AWS Image of BIG-IQ Centralized Management VE
How do I create an AWS image (AMI) of a BIG-IQ VE?
- Create a staging Linux instance in your AWS environment, and then copy the tar file to its default volume and unzip it on the secondary volume.
- Create a secondary Linux instance, and attach the staging Linux's volume to the secondary Linux instance's boot volume.
- Create the AMI on the secondary Linux instance. You'll use that AMI as the source for creating BIG-IQ VE instances.
Create a Linux instance and copy the BIG-IQ tar file to it
- Download the AWS BIG-IQ VE tar.gz file fromdownloads.f5.com.The file content can be as much as 5 GB compressed and includes the version number as part of its name. For example:AWS-F5_Networks-BIG-IQ-VERSION-standard-xxx.tar.gzYou can save time by alternatively transferring the tar. file directly from the Amazon Linux EC2 instance using cURL. Copy the file's URL fromdownloads.f5.com, then use the cURL command:curl "[URL]" > AWS-F5_Networks-BIG-IQ-VERSION-standard-xxx.tar.gz
- Log in to the AWS Management Console and launch a new Linux staging instance (for example, the Amazon Linux AMIhttps://aws.amazon.com/amazon-linux-ami) with the following attributes:
- The instance's storage should have enough free space to contain the downloaded BIG-IQ image. We recommend using an i3.xlarge or larger instance.
- During configuration, choose these settings:
- Size: 32 GiB
- Volume Type: Provisioned IOPS SSD (1)
- IOPS: 1600.
- To prevent SSH timeouts, in SSH, from the SSHConnectionsmenu, change theSeconds between keepalivessetting to90.
- Using SSH, connect to the Linux staging instance.For the Amazon Linux AMI, the user name isec2-user.
- Type the following SSHSecure copy (SCP) command to copy the tar.gz file to the staging instance's default volume.For example:scp -i <path_to_instance_ssh_key> <path_to_bigiq_tar_gz_file> ec2-user@staging_instance_ip:/tmp
- When the command finishes, stop the instance from the AWS Console.Do not stop the instance from SSH.
Create an empty volume and attach it to the staging Linux
- From the AWS Management Console, create a 500GB volume.
- Attach the volume to the staging Linux instance using the device name/dev/xvdc.When you're ready to attach the volume, your screen should look similar to this.
- Start the staging Linux instance.
- From SSH, connect and run the appropriate command to unzip and copy the files to the new volume.This process can take quite some time.
- If you have thepvutility installed, type:tar -zxOf AWS-F5_Networks-BIG-IQ-VERSION-standard-xxx.tar.gz | pv -bt | sudo dd bs=1M of=/dev/xvdc
- If you do not have thepvutility installed, type:tar -zxOf AWS-F5_Networks-BIG-IQ-VERSION-standard-xxx.tar.gz | sudo dd bs=1M of=/dev/xvdc
- When the command finishes, stop this instance from the AWS Console.Do not stop the instance from SSH.
- Detach the volume from the staging instance and then terminate the instance.If you do not terminate the instance, you might incur unexpected costs associated with the instance.The unattached volume is now accessible underELASTIC BLOCK STOREon the AWS EC2 Dashboard.
Create a second Linux instance and attach the staging Linux's volume to its boot volume
- From the AWS Management Console, launch a new Linux instance (HVM with at least 4 vCPUs and 8 GiB of RAM).
- When the new instance is ready, stop the instance.
- Detach the root volume from this new instance.This removes the OS boot volume. After you do this, this instance will have no available volumes.
- Attach the staging Linux instance's volume to the new instance using the device name/dev/xvda.Do not start this instance.When you're ready to attach the volume, your screen should look similar to this.When the attach
Create the Amazon Machine Image for the BIG-IQ VE source
- From the AWS Management Console underInstances, right click .
- Change allVolume TypestoGeneral Purpose SSD (GP2).This sets all of the default volume types to GP2 for future instances launched from this AMI.