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

I'd avoid default VPC entirely if possible.

the decision lies upon your use case and how many resources like this you'll need to produce.

Ideally, I find it easier to read the code to learn about the relationship between resources rather than clicking through AWS Console.

But there are cases where is it easier to create a resource manually and then inside pulumi just read the value (ARN or so,) from config or using `Get&lt;resource&gt;` function provided via the provider.

Additionally, you can import an existing resource that was created manually and start managing it from pulumi.

I hope this helps you to answer the question yourself.

One thing to mention, resources like RDS may add additional management overhead when dealing with updates.
So it's possible to extract them into a separate pulumi project or use my approach from above just by specifying required parameters in config

Thanks Jan, yes I am planning to setup Redis and PostGresql and deployed thru IaC. This greatly helps!

Another issue of mine is setting up SSL for my ALB using IaC that involves route53 and some certificate management.