- Newest
- Most votes
- Most comments
Hello,
Thank you for your query regarding the RDS Network Interfaces and public IP addresses. I understand your concern about AWS charges for public IPv4 addresses and your efforts to clean up your resources. Here's some clarification on your situation:
-
When you change the public accessibility of an RDS instance from "Yes" to "No", the public IP address is automatically removed. There's no need to manually delete the network interface.
-
You're unable to delete these network interfaces because they are still associated with your active RDS instance. This is expected behavior.
-
These network interfaces will be automatically deleted when you delete the RDS instance. However, since you still need your RDS instance, you don't need to (and shouldn't) delete these interfaces manually.
-
By changing the public accessibility to "No", you've already accomplished your goal of removing the public IP address. This change should be reflected in your AWS console and billing.
I've tested this in my own environment to confirm this behavior. Rest assured that by setting public accessibility to "No", you've taken the necessary step to remove the public IP address and its associated charges.
If you have any further questions or concerns, please don't hesitate to ask.
Interfaces that are provisioned by AWS services, such as RDS or Lambda, are owned by that service and not by your AWS account, despite the VPC they're in being yours. Only the service that owns the interface can delete it.
Did you remove the public IP address just moments ago? It may take some time for RDS to complete the configuration changes and to clean up leftover resources afterwards. I'd advise simply waiting and checking if the ENIs are gone by the next day.
If it's been longer since the public IPs were removed and the ENIs are still appearing with public IPs days later, I'd suggest opening a support ticket under the billing topic due to the public IPs getting charged despite your configuration not specifying them.
Relevant content
- asked 7 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago
Thank you, Leo. I am providing a status. The ENIs did not delete automatically, so I just created a support ticket under billing as advised. I will update when this moves along further, including providing an explanation of anything else I had to do in case someone else has a similar problem in the future.
I finally received a reply from billing. They pointed me to a couple of articles that I had already read, and then suggested I post a question on re:Post, which I've already done. So I guess I am at a standstill unless someone has another suggestion.
I am going to reply to the billing department that I've already posted a question here, and that contacting them was the suggestion I received from re:Post.