- 最新
- 投票最多
- 评论最多
For just root, "/" should do it.
Did you wait for it to fully propagate before testing with a cleared cached? Any CF changes can take 20+ minutes to take effect.
Yes I did wait for it to propagate. But I figured out the issue if anyone else runs into this!
Specify a Default Root Object is the culprit. If you specify a default root object for your cloudfront distribution, that supersedes any path pattern you have, and I'm pretty sure immediately executes through the default bin. So if you have a lambda @ edge function for the default bin it will still call that one.
What I did was remove the default root object, then in my Path Pattern '/' behavior, I redirected to '/index.html' (or whatever your default root object was) once I performed my needed functions in my lambda function. Hope this helps!
相关内容
- AWS 官方已更新 2 年前