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

• Crosswalk _should_ support your needs, regardless of your use case. It's designed to encapsulate things for the most common use cases (stuff you'd nearly always want, like a VPC across 3 AZs), but also to be production-ready and flexible. Would be interested to hear more about your use case.
• AWS Classic will be supported for quite some time to come.
• Can you provide an example of a simple-ish AWS Native use case that was taking a long time? It's my understanding that AWS Native is more performant than Classic.

Thanks for your reply Josh, that’s good to hear about the future of AWS Classic. I’ll get back to you about the other details tomorrow.

AWS Native being slower than AWS Classic:

This consistently takes around a minute to run ‘pulumi up’ on using e.g. eu-north-1:

```from pulumi_aws_native import s3

s3.Bucket('native-898324jmksdgkhfgdnbfghlkhrtlkwerkwerjt')```
And this takes about 5 seconds:

```from pulumi_aws import s3

s3.Bucket('classic-898324jmksdgkhfgdnbfghlkhrtlkwerkwerjt')```
For this experiment I used the Pulumi service as the backend.

Ah, found: <https://github.com/pulumi/pulumi-aws-native/issues/217>

I did some other instantiation timing tests using AWS Native/Cloud Control:

ec2.VPC: 20 seconds
ec2.Subnet: 10 seconds
ecr.Repository: 4 seconds

So I guess there is a wide performance variation when using the AWS Cloud Control API. These consistently take a few seconds using AWS Classic.