Help Center/ Config/ User Guide/ Resource Compliance/ Built-In Policies/ Elastic IP/ EIPs Bound Within Specified Days
Updated on 2025-08-25 GMT+08:00
View PDF
Share

EIPs Bound Within Specified Days

Rule Details

Table 1 Rule details

Parameter

Description

Rule Name

eip-use-in-specified-days

Identifier

EIPs Bound Within Specified Days

Description

If an EIP remains unbound to any resources within the specified number of days, this EIP is non-compliant.

Tag

eip

Trigger Type

Periodic

Filter Type

vpc.publicips

Rule Parameters

allowDays: indicates the maximum number of days that an EIP is allowed to remain unbound. This is a numeric type parameter.

Application Scenarios

The EIP service provides independent public IP addresses and public outbound bandwidth. An EIP can be bound to or unbound from resources such as ECSs, BMSs, virtual IP addresses, ELBs, and NAT gateways. Idle EIPs may cause the following problems:

  • Unnecessary expenses: Idle EIPs are still billed, causing increased expenses.
  • Exposure risk: Idle EIPs may be maliciously bound, increasing the possibility of being attacked.
  • Resource confusion: Idle EIPs increase the management difficulty.

Solution

If an EIP is still required, bind it to a resource. For details, see Binding or Unbinding an EIP.

If an EIP is no longer used, release it. For details, see Releasing or Unsubscribing From an EIP.

Rule Logic

  • If an EIP remains unbound to any resources within the specified number of days, this EIP is non-compliant.
  • If an EIP has been bound to a resource within the specified number of days, this EIP is compliant.
Parent topic: Elastic IP