I’ve just gone through the AWS getting started tutorial (https://www.pulumi.com/docs/get-started/aws/) and at the end it points towards Crosswalk for AWS (https://www.pulumi.com/docs/guides/crosswalk/aws/). However i’m also aware of the AWS classic package (https://www.pulumi.com/registry/packages/aws/) and the newer AWS Native (https://www.pulumi.com/registry/packages/aws-native/). As a Pulumi newbie who intends to target AWS (mainly ECS/Fargate and related services) and prefers to use Python, what is the recommend path?

I would use the native provider (and drop down to the classic provider if there's something you need that's not present in native) because native will have the fastest support for new features.

Thanks you Josh

Make sure to read what Native Provider offers thoroughly. Even if they say it supports a "service" it does not mean the whole API. That said Native provider is catching up quickly. So you may choose stability vs new features.

Thanks Jan, I tend to view Native+Classic as one combined option vs Crosswalk and the feedback here seems to be to go for the former rather than that latter. I’m not really sure what Crosswalk is/was intended for or how strategic it is for Pulumi (hence my question here!) and was confused as the getting started tutorial seems to hint that Crosswalk is the way to go which threw me, and I suspect others. It may be useful if the tutorial had some wording to help newbies decide which option is right for them.

I think that Crosswalk is/was intended to compete with CDK and offer higher-level abstractions on top of the classic provider and release of Native has probably impacted it. I still hope that Pulumi can get to the CDK level regarding IAM Roles because IMO CDK has the best IAM API.