#DNS error on bucket S3
37 messages · Page 1 of 1 (latest)
Project ID: 62a7d631-15d2-4bde-a633-b2e28b306105
62a7d631-15d2-4bde-a633-b2e28b306105
Inside the console, I see that there is a section about "access points" for my S3 but it's not mentionned in the blog
did you put those asterix there?
Yes to hide my bucket name
are you using private networking
yes it's enabled by default, I'm not asking if you have it enabled, I'm asking if you are actually using it
Yes I use it for some of my services
link me the template you are using for database backups please
I've forked the original one
To add a feature
Basically to backup more than one database
It's the same logic from the original one but with a foreach loop
do you have it set to run a backup at start?
Yes for testing
can you prefix the start script with sleep 3 &&
i dont think thats the issue here, look into the connection docs for the s3 client in use
Ok i will check 😉
I think it is the bucket s3, I can't ping it
well thats odd
Hi @devout linden,
Sorry it take some times to work on my project.
I've try on the eu-west-2 region and get the following error :
Error while running backup: 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/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
at /root/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
at de_PutObjectCommandError (/root/node_modules/@aws-sdk/client-s3/dist-cjs/protocols/Aws_restXml.js:5721:12)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async /root/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
at async /root/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
at async /root/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
at async /root/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/flexibleChecksumsMiddleware.js:57:20
at async /root/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26 {
'$fault': 'client',
'$metadata': {
httpStatusCode: 301,
requestId: '5SEYQH8XA8D9VMV9',
extendedRequestId: 'WFWT12p4LBCi4W9VJd0jethNOuhtDtkJ0jvKIcwpOBbtjLb2mgMpcicsqDhPC4zg6INzxM6yrFo=',
cfId: undefined,
attempts: 1,
totalRetryDelay: 0
},
Code: 'PermanentRedirect',
Endpoint: '***.s3.eu-west-2.amazonaws.com',
Bucket: '***',
RequestId: '5SEYQH8XA8D9VMV9',
HostId: 'WFWT12p4LBCi4W9VJd0jethNOuhtDtkJ0jvKIcwpOBbtjLb2mgMpcicsqDhPC4zg6INzxM6yrFo='
}
So locally, on my WSL, I've try to debug the project, by setting the AWS_S3_ENDPOINT=https://***.s3.eu-west-2.amazonaws.com provided by the project, I now got this error :
Error while running backup: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: ***.ezexchange-db-backups.s3.eu-west-2.amazonaws.com. is not in the cert's altnames: DNS:*.s3.eu-west-2.amazonaws.com, DNS:s3.eu-west-2.amazonaws.com, DNS:*.s3-eu-west-2.amazonaws.com, DNS:s3-eu-west-2.amazonaws.com, DNS:*.s3.dualstack.eu-west-2.amazonaws.com, DNS:s3.dualstack.eu-west-2.amazonaws.com, DNS:*.s3.amazonaws.com, DNS:*.s3-control.eu-west-2.amazonaws.com, DNS:s3-control.eu-west-2.amazonaws.com, DNS:*.s3-control.dualstack.eu-west-2.amazonaws.com, DNS:s3-control.dualstack.eu-west-2.amazonaws.com, DNS:*.s3-accesspoint.eu-west-2.amazonaws.com, DNS:*.s3-accesspoint.dualstack.eu-west-2.amazonaws.com, DNS:*.s3-deprecated.eu-west-2.amazonaws.com, DNS:s3-deprecated.eu-west-2.amazonaws.com
Do you have those kind of errors ?
I've put *** to hide my bucket name
I've fix the issue but another is triggered :
Error while running backup: AccessDenied: Access Denied
The policy in the blog post is too restrictif. You must put those allowed actions :
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:ListBucket"
],
You can close this issue