1 Answer
- Newest
- Most votes
- Most comments
2
The second set of instructions you have is what you'd want to use.
If you're in Route 53 you would use an A record that is an Alias to target the ALB in your environment. Make sure the security groups on your ALB are setup correctly as that may be what's preventing you from connecting to your application once you have it directed there.
If you're using something like Wordpress on the site behind the ALB you may have to turn on SSL support to get it work correctly and be all encrypted. But otherwise you should be good to go for the most part. If it's straight Apache there is a potential you may have to implement a re-write rule for SSL.
Relevant content
- Accepted Answerasked 10 months ago
- Accepted Answerasked 5 days ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
Thank you so much for your recommendations, Rob_H – they really helped. I edited the ACL, and now I can connect to my instance using both https and http. Unfortunately, another problem sprung up (https://repost.aws/questions/QUa5TsjwWGTUWlzfaxq3nX_Q/ec-2-instance-cant-access-the-internet). If you could look into it and let me know what you think, I would be most grateful.