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

Hello <@U05AZF5B7SQ>, the <https://www.pulumi.com/registry/packages/aws-native/|AWS Native> provider is still in preview. This provider follows the availability of resources offered in the new <https://aws.amazon.com/cloudcontrolapi/|AWS Cloud Control API>. If the resource is not available in the native provider, this (most likely) means it is not offered yet via this new AWS api. Please use the <https://www.pulumi.com/registry/packages/aws/|AWS Classic> provider in such cases. There is no problem mixing both providers in the same Pulumi project.

Hi <@UK4HNFLCB>,

Thanks for taking the time to respond. :pray:

I didn't realise both providers could be used side by side in a Pulumi project—I'll look further into that today.

Regarding the specific resource I'm having issues with (an SQS queue), the <https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/supported-resources.html|AWS Cloud Control API docs> state that `AWS::SQS::Queue` is indeed a supported resource type.

As it's a supported resource, could there be another reason why I'm seeing that `Resource type aws-native:sqs:Queue not found` error message?

Cheers!