1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
This has to do with attempting to use an S3 & Cloudfront deployment after using the amplify console kept failing at the build stage. Using python > 3.7 in lambdas caused a backend build error which was resolved using:
https://github.com/aws-amplify/amplify-console/issues/595#issuecomment-761049327
Erasing the S3 Cloudfront instances and erasing the custom domain from wihtin the amplify console then re-configuring it sorted out all the issues.
The confusing part was an error message referencing the domain being associated with another cloudfront distribution when there was no other cloudfront distribution.
beantwortet vor 3 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr