1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
You can use Cloudfront Behaviors to achieve this routing. You can see an example handling a similar use case here: https://containers-cdk-react-amplify.ws.kabits.com/frontend-react-with-aws-amplify/configure-cloudfront/ - https://aws.amazon.com/blogs/networking-and-content-delivery/improve-single-page-application-spa-performance-with-a-same-domain-policy-using-amazon-cloudfront/
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 3 ans- AWS OFFICIELA mis à jour il y a 10 mois
Thanks for your answer. Why can't I find the AWS Amplify Domain name(d36lqj7033ry8p.cloudfront.net) in CloudFront distributions
Amplify Console offers fully managed hosting so you don't get access to the CloudFront distribution.
If Amplify doesn't get access to Cloudfront, How can I workaround with your suggested solution? https://containers-cdk-react-amplify.ws.kabits.com/frontend-react-with-aws-amplify/configure-cloudfront/
unfortunately you would need to change the way you are hosting with amplify to something similar to what is described in the workshop where you explicitly configure cloudfront for a resource exposed from the AWS region