- Newest
- Most votes
- Most comments
You can allocate and associate Elastic IP to the VM which is yours until you release it. Detail description and "how to" is in this link: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
Hi together, I'm facing the same topic, and fubar's answer is not the answer to the question.
I'm migrating servers from OnPrem Nutanix to AWS, local on NTX we have 172.16.84.0/24. migrated machines will be in the 172.21.1.0/24 subnet on AWS. AWS and OnPrem are connected via VPN, tunnel 172.16.0.0/16 <-> 172.21.0.0/16 is established. How do I access the screen of the migrated machine to set a new IP in the 172.21.1.0/24 subnet to be able to access the machine through network again? I don't yet understand the migration technique of AWS, or how to do this the correct way. Thank god that my first test-machine is accessed from all systems by DNS-name, but my predecessor userd hardcoded IP for connecting systems, so this will be h*ll of a job to migrate those machines. Using the "old" network on AWS is not possible, as some machines will remain onpremises in that network, and also it is not possible to migrate all machines in on wave over a weekend, and having the same network on both sides as we all know is not possible.
Relevant content
- asked 3 months ago
- published 3 years ago
@AWS-User-alantam is this a good thing to do for private IPs that are only going to be used internally in a private subnet? I guess I always though of elastic IPs as for use in situations where you need a public IP.