Replies
|
3 replies
Answer selected by NAL100
And yes the bucket usually should be private, because usually users do not want to share the notes to the public. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I thought I set up everything correctly - I'm new to Amazon S3 and set up a bucket. I click "Check connectivity" and hit Check, and it says the bucket cannot be reached. Followed all of the instructions. The bucket is set for versioning, encryption, and public access is blocked (I assume the key still allows logging in). No access points have been set up, I'm using the default ones in the article.
Here is what my CORS file looks like - I didn't know what settings to use but here is what I put (BTW it would be really helpful to have a sample file for people to upload so they don't have to generate their own):
[ { "AllowedHeaders": [ "*" ], "AllowedMethods": [ "GET", "PUT", "POST", "DELETE" ], "AllowedOrigins": [ "app://obsidian.md", "capacitor://localhost", "http://localhost" ], "ExposeHeaders": [] } ]Endpoint and region used in settings:
s3endpoint: s3.us-east-1.amazonaws.com
s3region: us-east-1
Public and private key were generated by creating a new IAM user with "AmazonS3FullAccess" permissions group. I'm not sure what I'm doing wrong.
@NAL100
Please also add
HEADintoAllowedMethodsand try again.If you still encounter errors, would you please open the console and see if any hints/errors shown up there?