Static Website with Object Storage - default index error
Hello everybody!
I'm unable to configure a bucket to serve the default index on direct access through a CNAME entry set up at Cloudflare.
Example:
I'm accessing http://bucket-name.website-us-east-1.linodeobjects.com it resolves on default index set on website configuration, all good
I'm accessing https://bucket-name ( CNAME entry on Cloudflare ) - i get Access Denied on the request.
I'm accessing https://bucket-name/index ( which is the default index file set on Linode ) - i get correct response, all good.
The bucket policies were not touched, the bucket root is set to private, CORS enabled.
The file "index" is set public-read, content-type=text/html
I've tried this scenario on 2 different Object Storage environments, and got the same result.
From this i conclude that i'm completely missing something when setting up a static website Linode Object Storage + Cloudflare DNS entry.
Any clues will help!
PS: already tried all the online resources and Linode tutorials that i've found on this type of situation and none sorted the things out.
Thanks a mill!
1 Reply
Later Update,
While searching the web on this above, i think i got to the response.
Important Note: Linode Object Storage is S3-compatible, allowing you to use AWS's S3 constructs for policies. However, Linode's Object Storage does not currently support some of the static website hosting features provided by AWS S3, such as specifying an index document or error document. Thus, you will also need to handle requests for your website's root and 404 errors at the DNS or CDN level if needed.
So, basically Linode does not offer this type of environment setup, no matter what i place on default index root.
The information is from here :
https://www.pulumi.com/ai/answers/7uhwxkTReedhk5VTXoQMpM/handy-guide-static-website-hosting-with-linode-object-storage