I run the setup of S3 + Cloudfront and never ran into their index problem becaus... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

lawik on Feb 17, 2020 | parent | context | favorite | on: Building a static serverless website using S3 and ...

I run the setup of S3 + Cloudfront and never ran into their index problem because I'm not trying for URLs without document file extensions.

I assume that's the reason for really wanting index redirect in directories. Pretty URLs, I didn't feel the need. There are other valid reasons too I'm sure. But my needs diverged from the article even earlier than SEO penalties.

mlmitch on Feb 17, 2020 [–]

The pretty URLs thing is confusing me now too. AWS lets you configure the buckets to do the pretty URLs.

https://docs.aws.amazon.com/AmazonS3/latest/dev/HowDoIWebsit... https://docs.aws.amazon.com/AmazonS3/latest/dev/IndexDocumen...

I put up a Jekyll site on s3/cloudfront recently and it seems to work well.

Anyway, I’m still wondering about the consequences of the naked s3 endpoint being available.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact