I m experiencing some issues with `aws sdk go` where when ru

Question

I m experiencing some issues with `aws sdk go` where when running Pulumi in a container on an EC2 instance it s unable to use the instance profile attached to the instance this is the error I get ``` Exception invoke of aws index getCallerIdentity getCallerIdentity failed invocation of aws index getCallerIdentity getCallerIdentity returned an error 1 error occurred error configuring Terraform AWS Provider no valid credential sources for Terraform AWS Provider found Please see <https registry terraform io providers hashicorp aws> for more information about providing credentials Error NoCredentialProviders no valid providers in chain caused by EnvAccessKeyNotFound failed to find credentials in the environment SharedCredsLoad failed to load profile EC2RoleRequestError no EC2 instance role found caused by RequestCanceled EC2 IMDS access disabled via AWS EC2 METADATA DISABLED env var error an unhandled error occurred Program exited with non zero exit code 1``` I can curl the IMDSv1 endpoint within the container the container does not have any `AWS ` env vars set the container does not mount `~ aws` there is a valid IAM role attached to the instance that is in use with Terraform runs anyone know what s up here

billowy-army-68599 · Answer

< sparse state 34229> just to be clear you have a Pulumi program with the Pulumi SDK and you re also using the `aws sdk go` inside the program

billowy-army-68599 · Answer

can you share your code

sparse-state-34229 · Answer

i m running the pulumi command

sparse-state-34229 · Answer

it s run in a container

sparse-state-34229 · Answer

let me see what i can paste

sparse-state-34229 · Answer

sparse-state-34229 · Answer

this is from running `pdm run pulumi preview C lt project dir gt s lt stack gt diff` in github actions

billowy-army-68599 · Answer

i need the actual code in your Pulumi program

billowy-army-68599 · Answer

try setting the config value ```pulumi config set aws skipMetadataApiCheck false``` in your pulumi program

sparse-state-34229 · Answer

its uhh almost 5k loc haha

sparse-state-34229 · Answer

i ll try that

billowy-army-68599 · Answer

or set the env var `AWS EC2 METADATA DISABLED=false`

sparse-state-34229 · Answer

that seems to have worked

sparse-state-34229 · Answer

thank you

sparse-state-34229 · Answer

what confuses me is that this isn t an issue with terraform and it wasn t with pulumi in the past

sparse-state-34229 · Answer

hmm still doesn t work in a container tho

sparse-state-34229 · Answer

can curl IMDS

sparse-state-34229 · Answer

<https gist github com ohlol 4ea2781c027c236315be3b2e49fe5a8c> is the scope of the error

billowy-army-68599 · Answer

this is why <https github com pulumi pulumi aws issues 1692>

billowy-army-68599 · Answer

< sparse state 34229> you re using the aws SDK there and need to make sure you have creds for it

sparse-state-34229 · Answer

It s on an ec2 instance with an attached role

sparse-state-34229 · Answer

Permissions are not an issue the same host runs terraform with no issues

sparse-state-34229 · Answer

sparse-state-34229 · Answer

running Pulumi on the host works then it doesn t <https gist github com ohlol 9c8d0484c2403ea8afcab71c92bcd4bc>

sparse-state-34229 · Answer

the gists previous to this are from it erroring on the same stack as the first `preview` run in this output just linked

sparse-state-34229 · Answer

` urn=urn pulumi main account pulumi pulumi Stack account main `

sparse-state-34229 · Answer

that one

sparse-state-34229 · Answer

gt EC2RoleRequestError no EC2 instance role found

sparse-state-34229 · Answer

but as previously shown there is a role attached to the instance

sparse-state-34229 · Answer

and I am able to query it