Not working: 2 static websites, 2 origins, 1 CloudFront distribution

0

I have a CloudFront distribution that works fine with a single (primary) origin pointed to a static website hosted in S3. I then added a secondary origin with the same characteristics (static website hosted in S3) via a sub-path, and specified the precedence via the Behaviors to come first. In other words, I'd like requests to "/path" to go to my secondary static website and requests to "/" to go to the primary static website.

No matter what I do it doesn't seem to work. It's going directly to the secondary website even if my path is "/".

  • Precedence rule 0: Path pattern /path/* - origin is secondary
  • Precedence rule 1: Default (*) - origin is primary
Tom
已提問 10 個月前檢視次數 285 次
2 個答案
0

Try changing the path pattern to "path/*".
Perhaps the "/" at the beginning of the "/" is used to route to secondary when accessing with "/".
Also, the secondary S3 directory structure should be such that the contents are placed under "path/".
CloudFront does not ignore paths that match the path set in the Path Pattern when they are sent to Origin, but includes the path in the Path Pattern.
Therefore, if there is no content under "path/" in the secondary S3, an error will occur.

profile picture
專家
已回答 10 個月前
0

Thanks. I didn't need to remove the "/" in front of "/path/*".

Instead, there were 2 things I had to do:

  1. The secondary website had to have the website deployed to a "/path" subfolder inside the bucket. In my case, my website was a React app. To use the new path and ensure all referencing paths were set properly, I had to add this to my package.json: "homepage": "http://mywebsite.com/path"
  2. When referencing the secondary website, I had to add the trailing slash https://example.com/path/. This didn't work: https://example.com/path
Tom
已回答 10 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南