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

Thank you, I submitted a PR: <https://github.com/pulumi/pulumi-awsx/pull/412>

`To specify your own subnet configuration you can do the following:`

and code looks exactly the same as first example, it just has azs as a parameter

I think the author wanted to show here how to add a custom subnet by using new Subnet….

why do you think so? it looks okay to me, also in line with the third example

example1: ```
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";

const vpc = new awsx.ec2.Vpc("custom", {
   ...
   subnets: [{ type: "public" }, { type: "private" }],
});
```

example2: ```
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";

const vpc = new awsx.ec2.Vpc("custom", {
   cidrBlock: "10.0.0.0/16",
   numberOfAvailabilityZones: 3,
   subnets: [{ type: "public" }, { type: "private" }, { type: isolated }],
});
```

text in the middle `To specify your own subnet configuration you can do the following:`

only difference in subnets is that isolated was added

not sure, but I don’t see how that is ‘own subnet’, I was more expecting a direct access to subnet class from awsx

maybe the text isn't perfect? let's ask <@UB9JVTW07>