These tasks are required to use Auto Scaling with BIG-IP® VE.
|1||In BIG-IP VE, specify the Auto Scaling group name you will use in AWS||BIG-IP VE needs to know the name you plan to use for the AWS Auto Scaling group. You will create a group with this name later in AWS.||modify sys autoscale-group autoscale-group-id <groupname>|
|2||Optional. In BIG-IP VE, set up communication of metrics to AWS||BIG-IP VE can send metrics about its health to AWS; you can use these metrics to trigger Auto Scaling. If you want to use AWS metrics instead, you do not need to perform this task.||load sys config merge file /usr/share/aws/metrics/aws-cloudwatch-icall-metrics-config|
|3||In BIG-IP VE, finalize the instance by removing license files||You must remove license files specific to this instance of BIG-IP VE. This ensures that new instances created from the image retrieve new licensing from F5.||run util finalize-custom-ami|
|4||In AWS, create an image of the BIG-IP VE instance you want to scale||Shut down BIG-IP VE and create an Amazon machine image (AMI). This image will be used to create new instances.|
|5||In AWS, create a CloudWatch alarm||If you want to use BIG-IP metrics to trigger Auto Scaling, create the CloudWatch alarm before creating the launch configuration. If you want to use AWS metrics, you do not need this task; you can create the alarm while creating the Auto Scaling group.|
|6||In AWS, create a launch configuration and Auto Scaling group||The name you entered in BIG-IP VE for the Auto Scaling group must be the name of the AWS Auto Scaling group. Each time a new BIG-IP VE instance is created, it is added to the AWS ELB.|
If you want to use metrics provided by BIG-IP, complete the following steps.
|IAM role||Select the role you created earlier. This is required, unless you are using an IAM user's keys instead.|
|Enable CloudWatch detailed monitoring||Select this option.|
|Advanced Details > IP Address Type > Assign a public IP address to every instance||Select this option. BIG-IP VE must access the internet when it launches, so it can be licensed with F5.|
|Advanced Details > User data > As text||If you want to use IAM user keys instead of an IAM role,
or a different user created the BIG-IP VE image, enter your
Note: Keys override roles.
|Configure Security Group||Select an existing group that is associated with the VPC.|
|Group name||Type the name of the Auto Scaling group you created in tmsh.|
|Network and Subnet||Select the virtual private cloud (VPC) and its subnet (10.0.0.0/24).|
|Receive traffic from Elastic Load Balancer(s)||Select this check box and choose your ELB. This ensures that traffic flows from AWS ELB load balancer to the BIG-IP VE instances.|
|Use scaling policies to adjust the capacity of this group||Set the minimum and maximum number of instances and add
If you want to use BIG-IP metrics to trigger scaling of BIG-IP instances, from the Execute policy when list, select the CloudWatch alarm you created previously.