#new public ip

1 messages ยท Page 1 of 1 (latest)

lapis pelicanBOT
#

For AWS public IP changes, here's what you need to do:

1. New Instance IP

The new instance should already have a public IP automatically assigned (unless you specifically disabled it).

2. Update DNS (if using a domain)

If you have a domain pointing to your old IP:

  • Go to Route 53 (or your DNS provider)
  • Update the A record to point to the new public IP

3. Elastic IP Considerations

  • If you had an Elastic IP on the old instance โ†’ disassociate and release it (or re-associate to new instance)
  • If you want a static IP going forward โ†’ allocate an Elastic IP and associate it with your new instance

4. Security Groups

Check if your security groups reference the old IP in any rules (e.g., whitelisted IPs). Update if needed.

#

Quick One-Liner for New Instance

# Get your new public IP
curl ifconfig.me

Note: If you need a permanent/static IP to avoid this in the future, allocate an Elastic IP in AWS and keep it associated with your instance.

Does that help? ๐Ÿฆ