We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The current sspa script does not handle generating S3 Web host URL endpoints for EU regions
The text was updated successfully, but these errors were encountered:
This should be quite easy. simply change the region in the config file from Ireland to eu-west-1. That did the trick for me:
sebastian@ubuntu:~/PycharmProjects/learnjs$ ./sspa create_bucket fuit-sebisa
make_bucket: s3://fuit-sebisa/ Website endpoint is: http://fuit-sebisa.s3-website-eu-west-1.amazonaws.com
~/.aws/config: [default] region = eu-west-1 [profile admin] region = eu-west-1
Actually only the profile admin is necessary and used for your sspa so ignore the default one.
The Error I had before was:
sebastian@ubuntu:~/PycharmProjects/learnjs$ ./sspa create_bucket fuit-seb
make_bucket failed: s3://fuit-seb/ Could not connect to the endpoint URL: "https://s3.Ireland.amazonaws.com/fuit-seb" ./sspa: line 53: conf/s3/fuit-seb/endpoint.txt: No such file or directory Website endpoint is: http://fuit-seb.s3-website-Ireland.amazonaws.com Could not connect to the endpoint URL: "https://s3.Ireland.amazonaws.com/fuit-seb?website"
make_bucket failed: s3://fuit-seb/ Could not connect to the endpoint URL: "https://s3.Ireland.amazonaws.com/fuit-seb"
./sspa: line 53: conf/s3/fuit-seb/endpoint.txt: No such file or directory Website endpoint is: http://fuit-seb.s3-website-Ireland.amazonaws.com
Could not connect to the endpoint URL: "https://s3.Ireland.amazonaws.com/fuit-seb?website"
Sorry, something went wrong.
No branches or pull requests
The current sspa script does not handle generating S3 Web host URL endpoints for EU regions
The text was updated successfully, but these errors were encountered: