DevOps
How to Assign Separate Static IPs for Each Whitelabel on AWS
Solution Overview
AWS lets you assign multiple static IPs (Elastic IPs) to your server’s network interface.
The typical approach is as below
Option1 : Assign multiple Elastic IPs to your EC2 instance
Allocate an Elastic IP in the AWS console for each white-label brand.
Attach multiple Elastic IPs to the network interface (ENI) of your server.
In your app or at the OS level (Apache/nginx/Node.js/etc.), bind domains or routes based on the destination IP.
Example:
- BrandA → Elastic IP 1
- BrandB → Elastic IP 2
Both IPs map to the same server but your app logic distinguishes requests.
Option2 : Elastic Load Balancer (ELB) + multiple domains
If what you actually want is multiple domains (brand1.com, brand2.com) but one server:
- Use one Elastic IP or ELB.
- Map multiple domains (white-label brands) via DNS → same IP.
- Your app handles the domain based routing.
This is more scalable & cost efficient than managing many Elastic IPs.
Option3 : AWS Global Accelerator (Advanced)
If you want static global IPs (e.g., to serve clients worldwide with low latency)
- Use AWS Global Accelerator → assigns 2 static Anycast IPs.
- Map domains/brands at DNS to these IPs.
- Accelerator routes traffic to your server.
Important considerations
- AWS lets you have up to 5 Elastic IPs by default (can request increase).
- Each Elastic IP counts towards billing if unused or if you exceed the free allocation for the instance type.
- App or web server (e.g., nginx) must be configured to listen on multiple IPs / bind traffic as needed.
- DNS + domain mapping can be more flexible than assigning multiple static IPs.
Ready to transform your business with our technology solutions? Contact Us today to Leverage Our DevOps Expertise.
Comment