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

this should happen automatically if you provide outputs from the rds instance to the postgres provider. Is this not happening? if not, can you share code and any errors?

Im getting a connection refused error.

but it may be because there is an existing database and the postgres provider uses new resources

is your RDS in a private subnet? can you access it with netcat or telnet?

yes it is private and I can acces it using a bastion. I think the issue is that the new posgresql commands is using a newly generated password and not the one already provisioned.

hey <@UCWG26BH7>, I am getting this error when the postgres provider attempts to run the different resources:

```error detecting capabilities: error PostgreSQL version: pq: SSL is not enabled on the server```

this is how I am setting up my provider:
```
    const pgsqlProvider = new postgresql.Provider(
      `${parentId}-db-pgsql-provider`,
      {
        host: db.instance.endpoint,
        password: this.password,
        sslmode: 'disable',
        username: this.username,
      },
    );```

:disappointed: awww, ok Ill keep tsearching/trying

do commands wiht the postgresql provider run in sequential order as they are defined? or is it necesary to use `dependsOn` to ensure they run in a specific order?

hmm does the provider run inside the VPC? im getting this error now:
```dial tcp 10.0.253.222:5432: connect: operation timed out```
not sure if its networking related or permissions

&gt; do commands wiht the postgresql provider run in sequential order as they are defined? or is it necesary to use dependsOn to ensure they run in a specific order?
you can use dependsOn, but if you pass an output from one resource (ie, the db address or username) as an input to another resource (ie: the provider) the engine figures out the correct order

&gt; hmm does the provider run inside the VPC?
no it runs from the machine you’re running Pulumi on

it looks like your bastion isnt working correctly, it still seems like a network problem to me

aaah! thats it! I was thinking this ran remotely somehow inside the aws env. I turned on teh bastion and its connecting! Thanks for clearing that up!