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

Could this have something to do with my domain? SQL Server is connected to a DC in the same VPC, and I'm getting this error in the same `pullumi up` calls:
&gt;  aws:directoryservice:LogService (mydomain):
&gt;   error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:34623: connect: connection refused"

Oh, and this one from RDS:
&gt;   aws:rds:Instance (mydb):
&gt;    error: transport is closing

I noticed it had a bad log group (it was using the name of a log group that was deleted yesterday.. no referential integrity!). When I fixed that, the problem went away. Looks like the problem wasn't with making the change, it was with reporting the change to Cloud Watch! And that caused the action to abort.