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

is this when it is running in AWS, or when it is running locally?

you said it is in a container - I'm wondering if it is related to the options that you need to enable to tell it to look in a certain place for AWS creds, on the AWS provider.

The error happens in a container, running on GKE

it cannot “launch” the aws binary insude of the container

but manually, inside the container, I can

I'm thinking it is related to this then: <https://github.com/pulumi/pulumi-aws/issues/1359>

You need some combination of `SkipMetadataApiCheck` and `SkipGetEc2Platforms` to be set to `false`. The defaults were changed because performing those checks every run was a performance hit so the defaults were changed to `true` recently

Fairy sure it is not related to credentials, this is before it needs credentials. It cannot launch the AWS binary. Nothing in that issue is close to the error I’m seeing.

I'm seeing `getting credentials:` in the original error you mentioned as well as this `unable to load schema information from the API server` so maybe I'm not seeing the same thing you are

```exec: fork/exec /usr/local/bin/aws: no such file or directory```


but /usr/local/bin/aws is there and i can run the aws binary shelled into the container

Yes I roger that. I was thinking that maybe it was looking locally for creds because the API check for creds and the inferred EC2 check for creds were disabled by default. Anyways, sorry If I led you astray. Good luck!

Ok, /usr/local/bin/aws is a symlink, i modified the path so it chose the real binary first

```# which aws
/usr/local/aws-cli/v2/current/bin/aws```
but out of the automation api i still get

```fork/exec /usr/local/bin/aws: no such file or directory```


OH MY GOD… Since yesterday i’ve been deploying changed containers to one env, and testing it in another env. :man-facepalming::skin-tone-2: