https://pulumi.com logo
#general
Title
# general
v

victorious-wall-1075

02/17/2022, 5:02 PM
When I try to use pulumi with MinIO backend AND try to configure AWS:ec2 instance, I see issues resulting from clash in the AWS key and credentials//
Copy code
[default]
aws_access_key_id = MyKey
aws_secret_access_key = MySecret

[minio]
aws_access_key_id = minioadmin
aws_secret_access_key = minioadmin
I am setting AWS_PROFILE=minio so the backend can use the minio profile. However, this collides with AWS operations as pulimi tries to use the same key with AWS and fails.. If set the profile to default the backend calls fail.. How do I get around this?
l

limited-rainbow-51650

02/17/2022, 5:30 PM
Have a look at this section: https://www.pulumi.com/registry/packages/aws/installation-configuration/#set-up-multiple-profiles You can pass
profile
explicitely if you create a provider in your code for the EC2 resources: https://www.pulumi.com/registry/packages/aws/api-docs/provider/ Use the environment variables to let pulumi pick up the credentials for the minio backend.
🙌 1
👀 1
v

victorious-wall-1075

02/18/2022, 4:20 AM
@limited-rainbow-51650 this works! thank you very much.
can you please add this to the section on S3/Minio backend section in the docs. It might help others who are using S3 backend + trying to configure AWS
👍 1
3 Views