In AWS, most public IPs are temporary. Restart an EC2 instance, and it could receive a completely different IP. For basic setups, this isn’t always a problem. But if you’re running infrastructure that depends on stable connectivity—like proxies, licensed software (e.g., cPanel), or DNS entries—constantly changing IPs will break things.
Elastic IPs solve this by giving you control over a permanent IP address. You can detach it from one instance and move it to another in seconds. This flexibility ensures your service remains accessible, whether you’re scaling proxies, replacing servers, or managing failover.
While AWS provides Elastic IPs for free when attached to a running instance, there’s a small charge if they’re idle, since they’re a limited resource.
Code Example
Here’s a quick AWS CLI example of allocating and assigning an Elastic IP:
# Allocate a new Elastic IP
aws ec2 allocate-address --domain vpc
# Associate it with an instance
aws ec2 associate-address --instance-id i-0123456789abcdef0 --allocation-id eipalloc-12345678
What’s your use case?
Chat with one of our Data Nerds and unlock a 2GB free trial tailored to your project.
Use Cases
Running proxy infrastructure
Elastic IPs provide stable entry points for proxy services. This ensures clients can consistently connect without DNS changes every time an instance restarts.
Reliable DNS pointing
If your domain points directly to an EC2 instance, an Elastic IP prevents disruptions caused by changing public IPs.
Application licensing
Many server tools, like WHM/cPanel, tie licenses to a fixed IP. Elastic IPs make sure those licenses remain valid.
Failover and redundancy
If a proxy node or server fails, you can instantly remap the Elastic IP to a backup instance—keeping traffic flowing with minimal downtime.
Best Practices
Use Elastic IPs only where needed
They’re ideal for proxy endpoints and public-facing services, but don’t assign them to every instance. Elastic IPs are limited per region (default: 5).
Release unused Elastic IPs
Since AWS charges for idle EIPs, make sure you release any that aren’t actively attached to running instances.
Automate remapping
In proxy fleets or scaling environments, scripts or orchestration tools (like Terraform or Ansible) can automatically reassign Elastic IPs during failover or scaling events.
Secure the endpoint
Even with a stable IP, always protect your proxy endpoints with proper firewalls and access controls to prevent abuse.
Conclusion
An Elastic IP is a permanent, public IPv4 address in AWS. It ensures stability across restarts and makes it easy to move traffic between instances. For anyone running proxies, hosting services, or licensing software tied to IP addresses, Elastic IPs are the simplest way to keep infrastructure reliable.
Ready to power up your data collection?
Sign up now and put our proxy network to work for you.
Frequently Asked Question
Do I always need an Elastic IP for proxies?
+
Yes, if clients or software connect directly to a fixed IP. Otherwise, you’d need to reconfigure DNS every time an instance’s IP changes.
Are Elastic IPs free?
+
Yes, as long as they’re attached to a running instance. AWS charges for unused ones.
How many Elastic IPs can I have?
+
By default, five per region. You can request more from AWS if your proxy network or infrastructure requires it.
Can I move an Elastic IP to another instance?
+
Absolutely. That’s one of their biggest strengths—Elastic IPs can be remapped within seconds during failover or scaling.