- Newest
- Most votes
- Most comments
Hello.
The Elastic IP address may be associated with some AWS resource.
So please try deleting that AWS resource first.
https://repost.aws/knowledge-center/ec2-troubleshoot-elastic-ip-addresses
When releasing an Elastic IP address from my account, I'm getting the error: "Elastic IP address could not be released. You do not have permission to access the specified resource."
This error message occurs when you try to release or disassociate an Elastic IP address that's used by an AWS Managed Service. Examples of AWS Managed Services are Elastic Load Balancing (ELB), NAT Gateway, Amazon Elastic File System (Amazon EFS), and so on. To release an Elastic IP address associated with an AWS Managed Service, delete the resource that's using it. For example, if you have a NAT Gateway with an attached Elastic IP address, then you must first delete the NAT Gateway before you can release the Elastic IP address.
its associated with an internet gateway and I am unable to delete it as well with the same permission error. It pointed me to delete VPC endpoints, when I tried to delete it I get this message and no further information
There was an error deleting your endpoints Details
Create a temporary user with view permission for ELB, EC2, Elastic IP, etc. Then ask the person you want to take a look into the account. Then they might get a better perspective. Because the solution provided by the expert is ample to solve the error that you are getting. There must be something that is missing out which is causing your Elastic IP stay put
Relevant content
- asked 2 years ago
- asked 4 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
I don't think Elastic IP addresses are attached to internet gateways. Maybe it's attached to the ENI rather than the internet gateway? If you look at the relevant ENI, you may be able to see the AWS resources that the ENI is linked to in the description.
It could be a VPC endpoint created by some AWS resource. In that case, the VPC endpoint will not disappear unless you delete the relevant AWS resource first.