You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to sync a bucket in eu-west-1 from a docker running within the same region to a bucket in us-west-1 I get the error mentioned in the title.
The default region set in ~/.aws/config and AWS_REGION and AWS_DEFAULT_REGION are all eu-west-1
parseS3Url: input: :https://s3.eu-west-1.amazonaws.com/example.documents-assets.eu-west/
parseS3Url: input: :https://s3.us-west-1.amazonaws.com/example.documents-assets.us-west-1/
parsed-command-line:
command: sync
args: [] https://s3.eu-west-1.amazonaws.com/example.documents-assets.eu-west/, https://s3.us-west-1.amazonaws.com/example.documents-assets.us-west-1/
options:
bucket: example.documents-assets.eu-west
toBucket: example.documents-assets.us-west-1
verbose: true
region: us-west-1
filter: ({ LastModified }) => String(LastModified).startsWith('2023-')
folder: https://s3.eu-west-1.amazonaws.com/example.documents-assets.eu-west/
tofolder: https://s3.us-west-1.amazonaws.com/example.documents-assets.us-west-1/
s3p: d: 1s 193μs, items: 0, items/s: 0, listRequests: 2, listWorkers: 2, copied 0/0 0_B/0_B 0_B/s inFlight: 0_B copyWorkers: 0 + 0 same: 0(0_B) toDelete: 0(0_B)
S3.list-error:
bucket: :example.documents-assets.eu-west
prefix: undefined
startAfter: ""
limit: 1000
error: Error:
class: class S3ServiceException
stack:
PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
at throwDefaultError (/root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/smithy-client/dist-cjs/index.js:846:20)
at /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/smithy-client/dist-cjs/index.js:855:5
at de_CommandError (/root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4734:14)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:484:18
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:110:22
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:138:14
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:34:22
Error:
class: class S3ServiceException
stack:
PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
at throwDefaultError (/root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/smithy-client/dist-cjs/index.js:846:20)
at /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/smithy-client/dist-cjs/index.js:855:5
at de_CommandError (/root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4734:14)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:484:18
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:110:22
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:138:14
at async /root/.npm/_npx/301b345c5affbb3b/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:34:22
Description
When trying to sync a bucket in
eu-west-1
from a docker running within the same region to a bucket inus-west-1
I get the error mentioned in the title.The default region set in
~/.aws/config
andAWS_REGION
andAWS_DEFAULT_REGION
are alleu-west-1
To reproduce run
It will return
Observations
The same works with s3p 3.4.10
The text was updated successfully, but these errors were encountered: