How to Fix AWS Elastic IP Stuck with "ServiceManaged: RDS" Issue

Select Language:

If you’re noticing that an Elastic IP (EIP) is still associated with your RDS resources, even though it isn’t visible in the RDS console, it might be because RDS manages certain network resources behind the scenes. The presence of the “ServiceManaged: rds” tag shows that RDS has control over this resource through its service-linked role.

To resolve this, start by checking for any hidden or active RDS resources. Use the AWS Command Line Interface (CLI) to look for database instances that might be in the process of being deleted or transitioning:

To find database instances:

aws rds describe-db-instances –region us-east-2

ADVERTISEMENT
To locate Aurora clusters:

aws rds describe-db-clusters –region us-east-2
To check for custom cluster endpoints:

aws rds describe-db-cluster-endpoints –region us-east-2

Next, examine your network interfaces, as RDS often manages them and they can retain Elastic IPs:

Log into the EC2 console.
Go to “Network Interfaces” and filter the list by the region us-east-2.
Look for interfaces with descriptions mentioning “RDS” or with a “Requester ID” of “amazon-rds.”
Check if any of those interfaces are associated with your Elastic IP.

Also, consider whether RDS has created Virtual Private Cloud (VPC) endpoints, which might hold network resources. Run this command to find any associated with RDS:

aws ec2 describe-vpc-endpoints –region us-east-2 –filters “Name=service-name,Values=rds“

The service-linked role that RDS uses has permissions to manage EC2 resources, including addresses. Sometimes, cleanup processes can be delayed or get stuck. Given that your support case has been unassigned for over 12 days, it’s a good idea to escalate this issue or open a new support case. Be sure to mention the “ServiceManaged: rds” tag and the specific concern about the stuck EIP.

Ask AWS Support to check for any orphaned RDS-managed resources tied to your account. They can also verify if cleanup operations for the service-linked role are complete regarding this specific Elastic IP.

Since these resources are controlled by AWS through the service-linked role, you can’t directly force RDS to release the Elastic IP yourself. Instead, AWS Support has the tools and permissions necessary to handle this process.

For detailed information about the role’s permissions, you can review the Amazon RDS Service Role Policy through the AWS documentation here.