This topic describes the managed rules that are related to Elastic IP Address (EIP) and the methods to fix non-compliance issues.
eip_attached
Checks whether an EIP of your account is attached to an instance.
Trigger type: configuration change
Applicable resource type: ACS::EIP::EipAddress
Input parameter: none
Cause: An EIP of your account is not attached to an instance. Solution: Attach the
EIP to a network address translation (NAT) gateway, Elastic Compute Service (ECS)
instance, Server Load Balancer (SLB) instance, or secondary elastic network interface
(ENI). Cloud Config detects the configuration change and starts to re-evaluate the
resource within 10 minutes. You can fix this non-compliance issue by using one of
the following methods:
- Console
- For information about how to attach the EIP to an ECS instance, see Associate an EIP with an ECS instance.
- For information about how to attach the EIP to a NAT gateway, see Associate an EIP with a NAT gateway.
- For information about how to attach the EIP to an SLB instance, see Associate an EIP with an SLB instance.
- For information about how to attach the EIP to a secondary ENI , see Attach the EIP to a Secondary ENI.
- API
You can also call the AssociateEipAddress to attach the EIP to an instance in the same region. For more information, see AssociateEipAddress.