ah crap just spent time migrating to awsnsative to realize a lot of stuff isnt working security groups, subnets etc.. is there an ETA for this being usable, at least the core component of AWS being able to be provisioned, totally got the wrong impression from the blog post of day 1 support etc

I've had the same problem, though I did not spent that much time on it. I do not think there is an ETA, so best thing you can do is to follow the changelog for now https://github.com/pulumi/pulumi-aws-native

Sorry for the confusion there. Do you have any suggestion for making the current state of resource coverage clearer? As for ETA, it will depend on AWS adding support for the resources in their Cloud Control API. Generally speaking, any new resources should be available immediately, but the work to add existing resources is ongoing. Last I heard, it will probably be early next year before they have substantial coverage for existing resources.

Strange that it currently has support for vpcs but not subnets or security groups

Yeah, I guess the ball is in AWS's park here, Im just eager because existing AWS sdk is almost unworkable for me (bugs like https://github.com/pulumi/pulumi/issues/8163 - i.e. lookup a resource that doesnt exist, stack run completes swallowing the error, all resources defined after the lookup 'deleted' (if not being careful with preview).. awsnative works flawlessly in this scenario