[Enhancement] Redirect trailing / pages to index.html about cloudfront-authorization-at-edge

[gekart]

I think the best way to implement this is by creating a Origin Request lambda (that one is still available to be used) according to https://aws.amazon.com/de/blogs/compute/implementing-default-directory-indexes-in-amazon-s3-backed-amazon-cloudfront-origins-using-lambdaedge/

[ottokruse]

Thanks for mentioning this use case and linking to that solution.
To keep Auth@Edge as simple as possible, I think this would not need to be a functionality to be included by default. But for sure it is good to mention it here.

Another approach that would work is to upload those index.html files to the exact S3 path you'd want, and utilize the fact that object keys on S3 may end with a slash:
/my/sub/folder/index.html --> s3://mybucket/my/sub/folder/ (so the key would be "/my/sub/folder/")

That would save you a Lambda@Edge invocation.

[gekart]

Well the point is that I don't think this is how Hugo works oob (at least to my knowledge).

But you are right: The solution can be added on top of this application, since the "Origin request" lambda is still free to add. In my first post I still had the assumption that one would need to add the functionality to the "check-auth" lambda.