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

Is it different to setting up a non-public RDS instances? There's an example in the API docs: <https://www.pulumi.com/registry/packages/aws/api-docs/rds/instance/>

So long as it's in a subnet with an IGW and appropriate NACLs and SGs, isn't public?

I see a `publiclyAccessible` property which defaults to _false_.

Ooo big. Text snippets are good :slightly_smiling_face:

&gt;  I see a `publiclyAccessible` property which defaults to _false_.
Yes that's part of it

&gt; Text snippets are good
 which snippet would I choose from above, that's already minimal

I mean the Slack feature "Create Text Snippet" :slightly_smiling_face:

I think all the properties in that TF example have Pulumi equivalents. Is there one you can't find?

CleanShot 2022-02-14 at 16.00.18@2x.png

For starters vpc, nothing about public subnets or availability zones in pulumi

That VPC is from the AWS module. The Pulumi equivalent is awsx.ec2.Vpc. You can create public subnets manually, or allow awsx do it for you.

If you're comfortable with Pulumi, I prefer doing it manually, but the awsx package does make it very easy to set up.

I don't know if the docs for awsx have moved to registry, but here's the old docs: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ec2/>

I don't know what the awsx package is, will take a look

&gt;  Simpler interfaces encapsulating common AWS patterns.
ah

The only gotcha for awsx.ec2.Vpc is that subnets are dynamically created, which you can avoid if you do it yourself.

The upside of this is that awsx can take something simple like "2 public and 2 private subnets sharing CIDR 10.1.0.0/16" and work it all out for you.

The downside is that the subnets are created inside an `apply()` which means that you can't get at them except via an `apply()`. Normally this is no problem, but sometimes, it makes code a little more complex and untidy.

If this is your first Pulumi project, use awsx. If it's not and if you're comfortable creating the IGW, NAT gateway etc. yourself, then do it manually.

Thanks <@U012UJTT55M> this is the advice I needed I think