- Newest
- Most votes
- Most comments
You can consider registering (or creating) a domain under Route53 and provide that to your end customers for access. There are specific steps for routing traffic towards an EC2 instance. Having said that, generally speaking, adding an elastic load balancer in front of your EC2 instances is a much better pattern than having a public IP address associated with your production EC2 instance.
An Elastic IP address is a static IPv4 address designed for dynamic cloud computing. An Elastic IP address is allocated to your AWS account, and is yours until you release it. If you are concerned that the IP may be released by someone and hence you may not be able to obtain the same IP again, the alternative option is to bring your own IP. More information on the process to do this can be found here - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-byoip.html
Relevant content
- asked 5 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago