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

<@U013C0K64TH>
• what pulumi-awsx version are you using?
• what kubectl version are you using?
• what aws cli version are you using?

All from the docker image
```aws version: aws-cli/2.7.10 Python/3.9.11 Linux/5.4.109+ exe/x86_64.debian.11 prompt/off```
```node version: v16.15.1```
```kubectl version: Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:22:29Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}```
```Kustomize Version: v4.5.4```
```pulumi version: v3.35.0```
cc: <@UCWG26BH7>

that's the problem. please update to `0.40.0`

if we go to 0.40.0 for the eks-provider, is it required that we go `v5.x.x` for the aws provider? that v5 aws upgrade has a lot of big new things that make upgrading challenging

yes, but we kept this backwards compatible

across most of the breaking changes in the terraform provider