DNS error on bucket S3
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 :
Do you know why I got this error ?
Have a good day
22 Replies
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 no ?
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
GitHub
GitHub - FournyP/postgres-s3-backups: A simple Node app to automati...
A simple Node app to automatically backup PostgreSQL databases to an S3 bucket - GitHub - FournyP/postgres-s3-backups: A simple Node app to automatically backup PostgreSQL databases to an S3 bucket
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 redeploy
I have the same error :/
If I use eu-west2 do you think it will work ?
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 @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 :
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 :
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 :
You can close this issueright click on the chat
app > ✅ mark solution
How did you fix the issue -- the
ERR_TLS_CERT_ALTNAME_INVALID
one?