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

they’re in the schema for a provider: eg <https://github.com/pulumi/pulumi-aws/blob/master/provider/cmd/pulumi-resource-aws/schema.json>

Thank you for the pointer. This helps in finding the actual names manually. The format of the tokens seems to be a bit different when comparing native provider vs TF-bridged provider, e.g. aws:ec2/internetGateway:InternetGateway vs aws-native:ec2:InternetGateway, is this a general pattern or just specific for some providers?

Anyway, I was thinking about handling the import a bit more programmatically.
However, I noticed that Former2 (<https://former2.com>) now generates Pulumi code from AWS infrastructure, so that will address some usability aspects already for import. Just need to tweak the generated code a bit.