This message was deleted.

Hi, Where do you expect the feedback to be posted? (Should have read whole message 🤦‍♂️ ) In any case, my experience was pretty short because of 2 issues: 1. First 2 resources I was trying to create to setup (was trying to create a ECS cluster, so it's Vpc, Sgs, ECS cluster, IAM roles, don't remember what exactly was missing) were not available and immediately having to fall back to "AWS classic" felt strange. Especially when it is advertised as "having support for resources from day 1". 2. https://github.com/pulumi/pulumi-aws-native/issues/1052 It is marked as "annoyance" but in fact it is real issue (at least for me). API leads code to be extremely verbose (I use python) and all you can see is just class names everywhere. For me it is important that code is concise and clear. I can live with problem 1 and use aws classic to "backfill" for resources missing in native if API was better. Also the fact that Crosswalk modules use classic provider doesn't add confidence in it... Otherwise I'm really happy that I was tipped about Pulumi (thought to use Terraform in the beginning) 👍

@cuddly-nightfall-71097 Thanks so much for that feedback! The native provider is currently still in preview. This feedback is helpful to make plans for the future roadmap. 👍