Open guillefix opened 1 year ago
Same error here but I'm using Linode Object Storage. Previously configuring 'website_endpoint' with '%(bucket)s' and a hard coded region was working for me.
DEBUG: get_hostname(ai-space): ai-space.s3.amazonaws.com
It's still AWS S3. Try this:
$ s3cmd --host="${S3_HOSTNAME}" --host-bucket='%(bucket)s.'"${S3_HOSTNAME}" <args>
While the S3_HOSTNAME
variable is "\<region>.digitaloceanspaces.com". See Setting Up s3cmd 2.x with DigitalOcean Spaces :: DigitalOcean Documentation for details.
Linode's docs about configuring s3cmd: Using S3cmd with Object Storage | Linode Docs
I found solution, when you configure s3cmd with s3cmd --configure
you need to specify DNS-style for accessing bucket. Like this:
Use "%(bucket)s.s3.amazonaws.com" to the target Amazon S3. "%(bucket)s" and "%(location)s" vars c
an be used if the target S3 system supports dns based buckets.
DNS-style bucket+hostname:port template for accessing a bucket []: %(bucket)s.nyc3.digitaloceanspaces.com
Hello, I am getting the following error
S3 error: 403 (InvalidAccessKeyId): The AWS Access Key Id you provided does not exist in our records.
when using DigitalOcean Spaces.I configured s3cmd correctly, but it seems s3cmd is ignoring the host configuration for some of the requests, as seen in when running
s3cmd --debug la --recursive