No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Sorry for the trouble, <@U019S6HADQU>. We added some extra type checks in the Python SDK in v2.9.0, which mistakenly errors when some internal values are returned from the engine during previews. The issue has been addressed in <https://github.com/pulumi/pulumi/pull/5251> and should be released soon. In the meantime you can pin to earlier versions of the `pulumi` and `pulumi-aws` packages: `pulumi` `2.8.2` and `pulumi-aws` `3.1.0`.

I ended up doing essentially that this weekend.

thanks for confirming that you are aware of the issue

The fix has been released in version `2.9.2` of the `pulumi` package, which will work with `pulumi-aws` version `3.2.1`.

hmmm… I am still seeing the issue. Is there a ticket tracking this that I can add feedback to?

specifically when specifying `thresholds={"critical": 500, "warning": 250},` on a Monitor resource in datadog.

This looks like a bug in the Datadog provider. The same issue happens in C# programs, it’s just now showing up in Python due to the type checks that were added. During previews, `thresholds` is coming back as a list containing a map, but it is expected to be just a map. I’ve opened <https://github.com/pulumi/pulumi-datadog/issues/73> and am looking into it.