This message was deleted.
# generals
sparse-intern-71089
08/14/2020, 12:27 AMThis message was deleted.
l
little-cartoon-10569
08/14/2020, 12:29 AMIs there a way to set
bucket-owner-full-controlb
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
l
little-cartoon-10569
08/14/2020, 12:36 AMIs there a way to set
"s3:x-amz-acl": "bucket-owner-full-control"b
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
l
little-cartoon-10569
08/14/2020, 1:12 AMThe 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 AMThat 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 AMI 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?