I have a lingering Elastic IP since a few days. I used it for just a few minutes, after which I disassociated/released it. Since then, the EIP's Actions menu had 'Release...' and 'Disassociate...' greyed out. However, it keeps showing in my list.
I only had one instance in that region, and that instance doesn't show the EIP as tied to it, nor does its single ENI show any affiliation with that EIP. I checked through both the VPC and EC2 menus.
As a workaround, I spun up another instance and tried associating the EIP to it, but it says the EIP "is already associated".
It seems incredibly easy to issue an EIP, but problematic to get rid of it and thus get charged.
Please help me get rid of this EIP and stop getting charged. I might try to reassociate the EIP right now just to stop the charges for now.
AWS 공식업데이트됨 일 년 전
I didn't recall having made a NAT Gateway in this region, which was somehow tied to the EIP. I had made the EIP just for that instance though, and had even labeled it as such. I killed the GW and was able to release the EIP now... hmm....
The UI provides 2 options while creating NAT Gateway:
If you didn't add the extra click needed for step#2, then your existing (and unused) EIP got attached to the NAT Gateway.