https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
Yep. I have this exact problem. It's being tracked here: https://github.com/pulumi/pulumi/issues/4665
👍 1
c
yuck. Ok was hoping this would work since I am putting this in a pipeline to manage multiple accounts..
I mean technically I could within the program to an STS Assume role, but that is extra code that really shouldnt be needed.
just need the boto3 import for python
meh then you add a bunch of extra code cause pulumi doesn't recognize it
b
just out of interest, does it work with the 
AWS_PROFILE
environment variable?
the linked issue is related to the secrets providers, which is a slightly different issue than the engine execution
s
try that?
maybe not super relevant
c
@billowy-army-68599 no I tried both setting just Environment Variable and aws:profile, then also setting both
b
hmm that's interesting, I
I have a similar setup and it seems to work fine
c
I can manually using the same config do an STS:Assume Role call and get back temp creds. Just Pulumi isn't recognizing the Profile to assume
using v2.2.1
Cred FIle
Untitled
b
Can you open an issue in Pulumi/pulumi for this, I’d like to track it
c
ok
b
I’m also assuming you’re using the aws provider?
c
Yes. Version 2.4.0
python 3.7.7
m
I think I am hitting the same issue. Fresh Pulumi / awscli installed. I have profiles configured correctly, and the Pulumi stack configured to use a working profile. Consistently seeing:
s
You should print the getcallidentity accountid see if you are working in the expected account @microscopic-article-39213
m
@chilly-hairdresser-56259 Attempting to call 
aws.getCallerIdentity
fails with the same error as above: The 
pulumi diagnostic
line prints out the named profile I want to use, which confirms to me that Pulumi knows about the named profile configured, but it does not seem to be using it. Using that named profile with aws-cli directly works fine ala: 
aws s3 ls --profile=<profile name>
Happy to try other things to help debug.
c
Im going to start looking at this again today, try to figure out if maybe I am doing something wrong and comment on the github issue if I find anything.
@billowy-army-68599 I put in place a work around with aws-vault, not ideal, but it works. @microscopic-article-39213
👍 1
b
thanks, I didn't get time to look at this yet, but would appreciate a comment on the issue with your workaround
👍 1
c
will do thanks
29 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by