- 新しい順
- 投票が多い順
- コメントが多い順
Hello There,
Yes! ideally managing at the domain register would be the perfect solution, unless you're not adding any custom settings on the proxy other than redirect
Based on the second point I noted that the domain is pointing to the Proxy server and The same will redirect to the ELB. To leverage this, you can make use of Alias record and directly point to the ELB.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
By doing this, you will be managing all at one end and looks clean.
Regards, CK
Hello rePost-User-6394976,
Since you referenced ELB without saying if it had a static IP address, I will assume you are using an ALB. One work around to get rid of your proxy instance is to use a NLB in front of your ALB. This allows you to assign a static IP address (EIP) to the NLB with targets to your ALB. You can then create A records pointing to the IP of the NLB and no longer need the proxy instance. See this document for further information. I hope this helps!
-Nick
関連するコンテンツ
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前
- AWS公式更新しました 1年前