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

Also, I know AWS native provider was initially <https://www.pulumi.com/blog/announcing-aws-native/|started by Pulumi in 2021> as a separate project, but I guess the latest iteration of it is just derived from the <https://registry.terraform.io/providers/hashicorp/awscc/latest|awscc> provider (<https://www.hashicorp.com/en/blog/terraform-aws-cloud-control-api-provider-now-generally-available|made GA in May 2024>), am I correct?

`aws-native` does not derive from the TF awscc provider, it's a Pulumi-native provider for the AWS Cloud Control API

In other words, `aws-native` is to Pulumi what `awscc` is to TF

So they don't have the same interface? You too Cloud Control API and wrote some Pulumi components from scratch around them? Or you built your own automation that generates Pulumi components from it?

I'm just a Pulumi user, so I don't have any insights into development beyond what is publicly visible. You can see at <https://github.com/pulumi/pulumi-aws-native> that the SDK is generated from the AWS Cloud Control API spec, which gives you access to everything that AWS makes available through cloud control.