Issues with Elastic IP address on EC2? We can help you.

Generally, we receive errors while we allocate or release an Elastic IP address associated with the Amazon EC2 instance.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how to troubleshoot common issues with Elastic IP addresses.

Issues with Elastic IP address on EC2

In this article let us see how our Support Techs troubleshoot a few common issues.

Most often, the following are common issues that might occur with an Elastic IP address in the AWS account:

An associated Elastic IP address isn’t released, even after terminating the EC2 instance.

In this case, we need to disassociate an Elastic IP address from any resources to release it.

Once done, we can re-associate it with a different resource.

Suppose, we don’t need the Elastic IP address. Then we can release it.

“Elastic IP address could not be allocated. The maximum number of addresses has been reached”

Generally, we come across this error when we allocate a new Elastic IP address.

By default, all AWS accounts have a limit of five Elastic IP addresses per region.

In case of this error, we verify the number of Elastic IP addresses we use and the limit for the account.

Suppose, we need additional Elastic IP addresses. Then we request a quota increase.

“Elastic IP address could not be associated. You are not authorized to perform this operation”

This error occurs when we associate an Elastic IP address to one of the EC2 instances.

To allocate an Elastic IP address to the AWS account, we use the AllocateAddress API call.

On the other hand, we use the AssociateAddress API call associate an Elastic IP address to any of the resources.

The AWS IAM user or role using the command must have the following permission in the IAM policy:

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"ec2:AllocateAddress",
"ec2:AssociateAddress"
],
"Resource": "*"
}
]
}

“Elastic IP address could not be released. You do not have permission to access the specified resource.”

We see this error when we try to release or disassociate an Elastic IP address that an AWS Managed Service uses.

To release an Elastic IP address, we delete the resource that uses it.

[Stuck with the troubleshooting? We are here for you]

Conclusion

In short, we saw how our Support Techs go about the issues with Elastic IP address on EC2.