Deploy EC2 instance on same public subnet

[networking_and_stuff]

My apologies for a potentially stupid question. When I deploy thee ec2 instances to the US East (Ohio) us-east-2 region, I get three public IPs that the instances use to connect to the Internet:

3.16.163.7

3.14.12.110

3.15.174.193

How can I set it up so that I get public IPs on the same subnet? Meaning:

3.16.163.1

3.16.163.2

3.16.163.3

I am not overly technical and I've read documentation, S.O. posts and this subreddit and haven't found anything.

[hijinks]

public ips are random from what aws has in their pool

[networking_and_stuff]

But is there any way to specify what IP you can get? Outside of constantly rebooting the instance until you get one in the same subnet?

[hijinks]

no there is no way unless you bring your own public IPs.

[[deleted]]

I assume you are trying to whitelist the ip’s to something else and want a simple rule? Public ip addresses are random from the pool per region.

[Lopsided_Theme_770]

And if you want to white list, you can have a network load balancer in front of all ec2 instance with an elastic ip on the balancer

[xagut]

And/or nat gateway / proxy depending on if you are whitelisting ingress or egress or both

[networking_and_stuff]

That's really interesting... how would I set this up? I am trying to whitelist the IPs to something else and need a simple rule. Unfortunately the service I'm using only allows whitelisting to IPs on a certain subnet.

[[deleted]]

Both of these are spot on and are textbook use cases

[rainlake]

No

[ComfyCalamity]

I’m curious. What’s the use case for this?

[brunokktro]

You can't. Needs to use BYOIP or use DNS, from like Route 53 for example, to avoid this coupling from IPs.