Checks whether each elastic IP address (EIP) is associated with a cloud resource within the specified number of days after the EIP is created. If so, the evaluation result is Compliant.
Scenarios
You need to pay attention to idle EIPs that are not bound to cloud resources. This helps you better manage costs.
Risk level
Default risk level: medium.
When you apply this rule, you can change the risk level based on your business requirements.
Compliance evaluation logic
If each EIP is associated with a cloud resource within the specified number of days after the EIP is created, the evaluation result is Compliant.
If an EIP is not associated with a cloud resource within the specified number of days after the EIP is created, the evaluation result is Non-compliant.
If an EIP is created within the specified number of days (7 days by default), the evaluation result is Not Applicable.
Rule details
Parameter | Example |
Rule name | eip-idle-check |
Rule identifier | |
Tag | EipAddress |
Automatic remediation | Not supported |
Trigger type | Configuration change |
Supported resource type | EIPs |
Input parameter | allocateDays. Default value: 7 days. |
Non-compliance remediation
Bind an EIP to a cloud resource after the EIP is created for the specified number of days. For more information, see Release a pay-as-you-go EIP.