2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
Have you tried using an Alias record? Inside of Route53 when you are creating a record, there is a toggle switch for "Alias". Enable this, and then you can point the root domain directly to the Elastic Beanstalk instance, or the Application Load Balancer.
Some documentation that will help:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
1
If you don't require all the features of an ALB you can use an NLB with an elastic IP and point the domain to this.
Otherwise you can put the NLB in front of the ALB. NLBs now accept ALBs as a target group so this will handle the changing ALB address with no need for funky extra coding.
Hope this helps
답변함 2년 전
Can i automated above process using Lambda or cft
This domain is not hosted by Route 53 and I wouldn't let Route 53 host this domain because there are many other DNS hosts under this domain.
Apologies, I saw that you tagged Route 53 to this question so I assumed you were using the service. Unfortunately if the zone is not hosted within AWS, it's very hard to map it without using a CNAME and following the same procedure you're doing now.