1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
Both the error "Code: NoSuchKey" and message "Message: The specified key does not exist." appear to be S3 related errors, and not ALB/EC2 related. I believe your CloudFront is only directing to S3, and you are formulating URLs that you expect to find content on your ALB/EC2 that are actually being directed to S3. When the specific item being requested does not exist in S3, particularly if there is not a bucket or folder called "efforsition", you would get the error as described.
Can you separate the S3 access and ALB/EC2 into two separate CloudFront instances? If not, revisit to ensure that your logic on funneling traffic to one or the other is correct.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa