Anton Tayanovskyy

I have some updates on this issue. There are actually two issues: one is being unable to use pulumilocal helper that sets `aws:endpoints` - the issue persists and still reproduces...

The good news is that we should be able to release an awsx update shortly that is built against the latest AWS provider and is able to recognize aws:endpoints. This...

https://github.com/pulumi/pulumi-aws/issues/4004 relevant issue in pulumi-aws to track the root cause of being unable to use AWSX with newer settings for LocalStack.

Digging a little bit further and getting some help from @justinvp from the core team, there is now a supported way to use a different version of pulumi-aws package with...

Ah that's a good note. Super tricky. Perhaps we could avoid this just by being really systematic about only ever recording on CI (not locally), but I guess then again...

Possibly related: https://github.com/pulumi/pulumi-awsx/issues/300 https://github.com/pulumi/pulumi-awsx/issues/391 https://github.com/pulumi/pulumi-awsx/issues/354

Following the links I've found this prior art: https://github.com/pulumi/terraform-provider-aws/pull/59 One possibility here is to raise default timeouts again.

https://github.com/pulumi/terraform-provider-aws/pull/59 I've found has some prior art on editing default timeouts. Perhaps we could increase the values found in https://github.com/hashicorp/terraform-provider-aws/blob/master/internal/service/ecs/service.go#L50

I'm leaving this in the tracker to accumulate upvotes, and if it does we can circle back to pulumi-aws and increase default timeouts by patching upstream. For the moment issues...

Looks like in #1118 a transformation was added to send customTimeouts 30min.