Explain why stability is needed
Some integrations require an allowlisted address. I would ask whether that is the real need or whether a DNS name or managed endpoint fits better. A static address solves a particular requirement; it is not necessary for every server.
Check association and access
Associating an address does not open ports or create a missing route. Review the subnet path and access rules. Reassociation can redirect traffic, so record the purpose, owner and expected resource instead of treating the address as an anonymous allocation.
Review charges and cleanup
Public IPv4 addresses can incur charges, including unused allocations. Check current pricing and release addresses no longer needed. Deleting the instance is not a reason to assume every related network resource has also disappeared.
Try it yourself
Write an inventory entry with address purpose, associated resource, owner and cleanup decision. Decide how application users should reach it.
A common question
Does a static address make one server highly available?
No. A stable address and an available application solve different problems.
References & video notes
Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.
Keep learning
- Public and private IP addresses in AWS
- EC2 security groups: allow the right connections
- Amazon VPC: draw your network before creating it