This message was deleted.

sparse-intern-71089

08/14/2020, 12:27 AM

This message was deleted.

little-cartoon-10569

08/14/2020, 12:29 AM

Is there a way to set

bucket-owner-full-control

, or specify a different backend role, or anything that lets one stack read output from the other?

billowy-army-68599

08/14/2020, 12:35 AM

you'd need to do something out of band with the bucket policy here, its not natively supported

little-cartoon-10569

08/14/2020, 12:36 AM

Is there a way to set

"s3:x-amz-acl": "bucket-owner-full-control"

on all calls to s3:PutObject? This isn't my area of expertise...

billowy-army-68599

08/14/2020, 12:41 AM

i've never run into this personally, so not totally sure, but this seems to get the job done? https://aws.amazon.com/premiumsupport/knowledge-center/s3-bucket-owner-access/

billowy-army-68599

08/14/2020, 12:41 AM

I'm surprised you're hettig this with two AWS profiles in the same account

little-cartoon-10569

08/14/2020, 1:12 AM

The profiles are in different accounts. The bucket has a policy to allow writes from the "foreign" account.

little-cartoon-10569

08/14/2020, 1:14 AM

That link describes what I want to happen: how do I get Pulumi to use that when uploading the state files?

little-cartoon-10569

08/14/2020, 1:16 AM

I think the way to go will be to use a single profile for all Pulumi interactions, and to use providers which explicitly change profile based on what they're doing / which account they're using. I'm guessing that the provider used for a resource has nothing to do with the changes to state? They're always done using the default provider / profile?

Open in Slack

Previous Next

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.