No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

You've got a few options. For example, you can separate the DB configuration work into a separate project, and run that project from a bastion within a suitable subnet in the VPC.

Or you could use multiple projects within a single automation-api app: one of the projects includes setting up direct access from the deployment machine to the DB, and that project's stack would be destroyed within the automation-api app.

Or you move your DB configuration code out of Pulumi and into something that does have access to the DB, like an app VM or container.

Thank you! I love the thrid one since I don’t need to change anything. :grin:  got to set up a machine under the same vpc and run pulumi from it everytime.

If you currently set up the VPC and the DB from the same project, then you will definitely need to change something.

Oh Yes, that is 1. DB is under the default vpc, so nothing need to change.