How can I DELETE my Public IPv4 before February 2024 =(



I have a big problem.

I cant delete my public IPv4 and I am going around in circles.

Support told me to disassociate my Elastic IP address and Delete my VPC endpoints.

Unfortunately, I cant do both.

I am getting an error when I tried to do both.

Attached is a screenshot of the error messages I am getting

Elastic IP error

VPC Endpoint Error

I hope you guys and gals can help me.

Thank you very much in advance.

Sincerely, Vic Miranda

preguntada hace 8 meses2348 visualizaciones
4 Respuestas


This is a permission issue,please check you iam user have DisassociateAddressand DisassociateAddress action is allowed. Enter image description here

for more details:

profile pictureAWS
respondido hace 8 meses

Hi Vic,

Your user needs to have IAM authorizations ec2:DisassociateAddress and ec2:ReleaseAddress: to be able to dissociate and release your IP v4 address

See to get all details about those auths.

Your account admin will be able to grant you those rights (or dissociate / release for you)



profile pictureAWS
respondido hace 8 meses

Fristly, It doesnt look like a permissions issue to me, just that the resources are in use. I can reproduce the same error with being a Full Admin.

Secondly, public IPs do not get assigned to Private Endpoints. You should not need to delete endpoints as these are internal (PRIVATE RFC1918) IPs only. You cant delete a "Requester VPC Endpoint" until you have removed the service thats using it such as Aurora. This is still likely to be a private Endpoint and not public.

Thridly, an easy way to see where your public IP is being used is in the EC2 console. Goto Network Interfaces, and search for the public IP Address. Here you can see the description and private IP of what interface the public IP address is assigned too.

Based on the errors your seeing.

It looks to me that your Public IP May be assigned to a Internet Network Load Balancer.

profile picture
respondido hace 8 meses

Hi ThinkTik, Didier and Gary,

Thank you very much for your response. I was told by support that they think the endpoint was created by Redshift. Unfortunately, I already deleted my redshift instance a long time ago.

Is this as easy as re-creating my Redshift Instance and disassociate the endpoint there or am i just going to dig myself into a deeper hole doing this?

Thank you very much, Vic Miranda

respondido hace 8 meses

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas