Bug ID 611512: AWS: Pool member autoscaling in BIG-IP fails to add pool members when pool name is same as AWS Autoscaling Group name.

Last Modified: Jul 18, 2026

Affected Product(s):
BIG-IP LTM, MA-VE(all modules)

Known Affected Versions:
12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Aug 17, 2016

Severity: 3-Major

Symptoms

In AWS, Pool member autoscaling in BIG-IP fails to add pool members when pool name in BIG-IP is same as Autoscaling Group name in AWS.

Impact

- Pool member autoscaling doesn't occur correctly without user intervention.

Conditions

- BIG-IP is configured to perform autoscaling of pool members in AWS. - Pool name in BIG-IP is same as the autoscaling group name in AWS attached with it.

Workaround

When configuring pool member auto-scaling in AWS, you must choose a different name for the pool compared to the autoscaling group name attached with it.

Fix Information

Choose different names for Pool in BIG-IP and autoscaling group in AWS to correctly configure Pool member autoscaling in BIG-IP .

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips