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

The pulumi aws provider is bridged from the terraform provider so unless it’s in there, it won’t be in the pulumi one afaik

If it’s in the cloud control api, then you might find it in the aws-native package 

Hi Eduard,

for the `aws-classic` provider, the creation of  a unique client-token is done by Terraform (<https://github.com/hashicorp/terraform-plugin-sdk/blob/main/helper/resource/id.go>) as it is the "user" calling the API.

For the `aws-native`, I am currently unsure how the cient-token gets handled to ensure the Idempotency of the supported API calls.

I am asking about <https://github.com/pulumi/pulumi-aws|https://github.com/pulumi/pulumi-aws>

No that's what we call the classic aka bridge from TF

So normally in this, the terraform sdk should be taking care to set the client token on the calls.

Hmm, do I have an option to provide it by myself?

I am not 100 sure, but I did not see an option. The code above should be taking care, that you have a unique token every time