https://pulumi.com logo
#getting-started
Title
# getting-started
i

icy-eye-92908

08/02/2023, 4:11 PM
Hi everyone. We had developed a fullstack application with Next.JS in the Frontend and Nest.JS in the backend. All our code is written in Typescript. We are using Pulumi to deploy the backend and Database since the Frontend is deployed with Netlify Currently we launched to production about 15 days ago and we are taking steps into improving performance and availability of the app. One of the steps in this process is to start working on Database High Availabilty. For that purpose we need to enable automatic backups of the database and later we are planning to setup a multi AZ deployment. We are struggling a little bit with enabling automatic backup following official Pulumi documentation. Is there anyone with experience on enabling automatic backups for AWS Postgres RDS instances using Pulumi that can provide some guidance?
s

salmon-account-74572

08/04/2023, 3:28 PM
Hi @icy-eye-92908! I don’t have any direct experience with doing automatic backups for RDS, but it looks like the
backupRetentionPeriod
and
backupWindow
properties of the AWS RDS instance resource are what you’d be most interested in. Given that you don’t have direct experience with this (nor do I), I might suggest creating a new stack in a new branch and testing these properties on non-production infrastructure first.
i

icy-eye-92908

08/04/2023, 3:30 PM
Thanks Scott already dis some testing with those configuration keys but my staging environment couldn't deploy the Pulumi stack. Also I want to be able to decide on which environment to deploy these configuration keys (only on prod) but also struggled to enable it just for staging.
s

salmon-account-74572

08/04/2023, 3:32 PM
What sort of problems did you encounter when you tried to enable it just for staging?
i

icy-eye-92908

08/07/2023, 2:51 PM
Basically what happened was that after deploying I started to get errors on Pulumi that it couldn't downgrade from Postgres 14.7 to 14.2 and I don't know why exactly that happened, which forced me to revert everything and set the Postgres version to 14.7.