Public IPv4 addressing behavior with AWS spot instances

amazon-web-services amazon-ec2 cloud amazon-elastic-ip

I'm deploying a very resource intensive web scraper, to optimize costs I opted to use AWS Spot Instances knowing the default behavior of IP addresses when dealing with EC2 instances the 1st question that came up to mind was if it's possible to maintain a fixed IP address when spots are reissued by AWS.

it is crucial to be able to do this without any human intervention (the whole thing is connected to multiple gitlab pipelines)


Put them behind a NAT gateway - that way they’ll extenally use the NAT GW IP address.

Related

passing real IP address from one nginx instance to another and writing it in the logs
How to set permanent mtu size for ppp0
ZFS on Linux denied access when accessing child dataset on NFS
Implementing recursive property loading in EF Core
JavaScript(ES6) WeakMap garbage collection when set an object to null
android:how to check if application is running in background
How do I append data from a data frame in R to an Excel sheet that already exists
Problem with -libjars in hadoop
IIS 7.5, Web Service and HTTP 405 error
How do Java programs run without defining the main method?
Blocking Chrome Extensions from running on my site
Two ArrayList one RecyclerView Adapter