- 新しい順
- 投票が多い順
- コメントが多い順
Whatever Global Accelerator points to needs to be a proxy that fetches the Amplify content to preserve the apex URL. Maybe an ALB in front of a couple EC2 proxies or a Lambda function.
Like @kentrad said above, If you need to host the application in Amplify then you would need something in the middle to handle rewriting the domain. Given the requirements you outlined, I’m not sure that Amplify is the best choice. There are other hosting options to Amplify that can still help with the management/overhead of the AWS infrastructure involved, like Elastic Beanstalk for example. Another alternative would be running your application on EC2 instances. You would still have the ability to integrate your CI/CD process with hooks into your source code repositories that would allow you to automate builds/deployments using AWS Code* services. Using Global Accelerator with an ALB endpoint that targets one or more EC2 instances would solve the redirect/rewrite issue you are experiencing and allow you to point the apex record to the IPs provided by the Global Accelerator.
関連するコンテンツ
- AWS公式更新しました 10ヶ月前
- AWS公式更新しました 2年前