DNS error on bucket S3
pierro-mojito
PROOP

2 years ago

Hi everyone, I've just deploy the template to automate postgresql backups and I got this error when the script try to deploy the backup :

Error while running backup:  Error: getaddrinfo EAI_AGAIN ******.s3.us-west-3.amazonaws.com

Do you know why I got this error ?

Have a good day

35 Replies

pierro-mojito
PROOP

2 years ago

62a7d631-15d2-4bde-a633-b2e28b306105


pierro-mojito
PROOP

2 years ago

Inside the console, I see that there is a section about "access points" for my S3 but it's not mentionned in the blog


2 years ago

did you put those asterix there?


pierro-mojito
PROOP

2 years ago

Yes to hide my bucket name


2 years ago

are you using private networking


pierro-mojito
PROOP

2 years ago

Yes


pierro-mojito
PROOP

2 years ago

It's enabled by default no ?


2 years ago

yes it's enabled by default, I'm not asking if you have it enabled, I'm asking if you are actually using it


pierro-mojito
PROOP

2 years ago

Yes I use it for some of my services


2 years ago

link me the template you are using for database backups please



pierro-mojito
PROOP

2 years ago

I've forked the original one


pierro-mojito
PROOP

2 years ago

To add a feature


pierro-mojito
PROOP

2 years ago

Basically to backup more than one database


pierro-mojito
PROOP

2 years ago

It's the same logic from the original one but with a foreach loop


2 years ago

do you have it set to run a backup at start?


pierro-mojito
PROOP

2 years ago

Yes for testing


2 years ago

can you prefix the start script with sleep 3 &&


pierro-mojito
PROOP

2 years ago

1156622793736208400


pierro-mojito
PROOP

2 years ago

I redeploy


pierro-mojito
PROOP

2 years ago

I have the same error :/


pierro-mojito
PROOP

2 years ago

If I use eu-west2 do you think it will work ?


2 years ago

i dont think thats the issue here, look into the connection docs for the s3 client in use


pierro-mojito
PROOP

2 years ago

Ok i will check 😉


pierro-mojito
PROOP

2 years ago

I think it is the bucket s3, I can't ping it


2 years ago

well thats odd


pierro-mojito
PROOP

2 years ago

Hi @Brody,

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 AWSS3ENDPOINT=https://***.s3.eu-west-2.amazonaws.com provided by the project, I now got this error :


pierro-mojito
PROOP

2 years ago

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

pierro-mojito
PROOP

2 years ago

Do you have those kind of errors ?


pierro-mojito
PROOP

2 years ago

I've put *** to hide my bucket name


pierro-mojito
PROOP

2 years ago

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"
],

pierro-mojito
PROOP

2 years ago

You can close this issue


2 years ago

right click on the chat


2 years ago

app > ✅ mark solution


coopbri
PRO

2 years ago

How did you fix the issue -- the ERR_TLS_CERT_ALTNAME_INVALID one?


Loading...