2 回答
- 最新
- 投票最多
- 评论最多
0
I have been in the same situation (almost). I did this workaround: create a new EC2 free tier, attach the IP, stop the instance, detach the IP, release it, and then delete the EC2. In my case, always work in that way
已回答 2 年前
0
I was in the same issue having requested a reverse DNS record before you could set them with the API. We also have a basic support plan so I couldn't open a regular support case to have the address unlocked.
I requested to have the address unlocked at https://support.console.aws.amazon.com/support/contacts#/rdns-limits and they did it within 12 hours.
已回答 1 年前
相关内容
AWS 官方已更新 3 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
It didn't helped.
It does not work. My Elastic ip is for VPC. Any way to contact support to fix their own bug? BTW, I only have basic support plan.