This message was deleted.
# awss
sparse-intern-71089
05/31/2022, 10:27 PMThis message was deleted.
l
little-cartoon-10569
05/31/2022, 10:28 PMThere's a few ways to interpret your question. Can you clarify? Are you hoping to run Pulumi on an EC2 instance?
c
curved-kitchen-24115
05/31/2022, 10:28 PMYes
curved-kitchen-24115
05/31/2022, 10:29 PMTypically I have run pulumi from my localhost / work laptop. However I'm hoping I can migrate this to our remove development workstations that we run in EC2.
l
little-cartoon-10569
05/31/2022, 10:30 PMThe AWS CLI does this implicitly, but Pulumi doesn't. There's instructions on how to set it up explicitly here: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-metadata.html
c
curved-kitchen-24115
05/31/2022, 10:30 PM@little-cartoon-10569 I'll give it a go. File this under TIL
👍 1
l
little-cartoon-10569
05/31/2022, 10:31 PMYou may also need to set AWS_PROFILE to be the profile you create with that info? Not 100% on that...
c
curved-kitchen-24115
05/31/2022, 10:48 PMRE: AWS_PROFILE the docs state that - but it seems if it's the default profile you don't have to do that.
Ultimately, I think this is not what I want. The problem then devolves into trust relationships which get's a bit chicken:egg-esque because the instance itself is managed by pulumi.
AWS_ACCESS_KEY here I come! Thanks anyways @little-cartoon-10569
l
little-cartoon-10569
05/31/2022, 11:02 PMYou might want to consider using this technique to get a base profile, then assuming an explicit role from there?
2 Views