Vivek Lakshmanan

Thanks @sudermanjr - I will bring this up for prioritization. Does seem like a valuable feature. Do you have a workaround at the moment?

Thanks for opening the issue @danielbichuetti. Seems surprising since we do lookup the amiID corresponding to the amiType - which I believe you are providing to indicate this is arm64:...

Additionally, `TestAccAwsProfile` is also failing.

I am not able to reproduce this issue. I tried with a fresh PULUMI_HOME as well as a docker setup as defined in the bug. In both cases the provider...

Tried to repro this with @bob-bins. We confirmed that baseline use cases worked fine in docker. I will keep this open since something about the way @bob-bins' project is set...

Reopened at @liamawhite's request. Possible link with https://github.com/pulumi/pulumi/issues/7702.

In this case the error was because the subnet Ids not being specified while a vpcid was. Regardless, the error message is highly cryptic and completely inactionable.

> Is this an instance of [pulumi/pulumi-terraform-bridge#311](https://github.com/pulumi/pulumi-terraform-bridge/issues/311)? Its certainly related but I think even a more useful error message from the underlying provider (pulumi-aws) in this case won't be useful...

Note the above example will require https://github.com/pulumi/pulumi/pull/6224

While I haven't tried to reproduce this, looking at the code base, I don't think this is a complete surprise, given the complex interactions leading to the creation of the...