Error running pulumi-aws in CI environment when assuming a role for credentials

The code would effectively be doing the following:

const provider = new aws.Provider("provider-name", {
    skipCredentialsValidation: false,
	skipMetadataApiCheck: false,
	region: <region name>,
	profile: <empty string>,
})

This is working in 3.23.0 but not in 3.29.1 and would be using an IAM Role to get the credentials. The error message is:

 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. Deprecated.
     	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

[stack72]

Hi all

Based on the investigation work by @DavidHe1127 and @leezen, I was able to find that there was indeed a bug in named providers that stopped values being used that were not the default

I was able to fix that in https://github.com/pulumi/pulumi/pull/6496

This work has made it’s way down to the pulumi-aws provider as v3.32.1 and we believe this now means that you can set your values as expected and you should be able to authenticate in an EC2 environment with the iam role.

Your code would need to be something like this:

const prov = new aws.Provider("named-provider", {
    region: "us-west-2",
    skipMetadataApiCheck: false,
    skipGetEc2Platforms: false,
});

and it will pick up the creds

I am going to close this issue out BUT IF THERE ARE ANY FURTHER ANOMOLIES then please do comment and we can reopen and investigate further if needed

Thanks again for your patience here and we can’t thank you enough for helping us track down this bug

Paul

[stack72]

Hi @dferretti

If these config values work for you, then I will also add a guide to the README to suggest ### Running Pulumi-Aws in CI environments so that others don’t get bitten

P.