https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
hey Harrison, We can definitely help. Can you provide more information about the changes you’re seeing ?
a
sure! to start the newer deployment has the s3 bucket ‘Block public access’ turned on where the old has it turned off
and there is also ‘Object Ownership’ which is set to bucket owner enforced instead of ‘Object writer’
there may be others that I haven’t discovered
b
can you share code? screenshots? anything that could help us debug?
a
here is what we have for the bucket:
Copy code
export const appAssetsBucket = new aws.s3.Bucket(`${config.commonName}-assets`, {
  acl: "private",
  tags: Object.assign({ Name: `${config.commonName}-assets` }, commonTags)
});
trying to remove and readd now
b
ah, this is an account level setting defined by AWS https://aws.amazon.com/about-aws/whats-new/2022/12/amazon-s3-automatically-enable-block-public-access-disable-access-control-lists-buckets-april-2023/ This is being rolled out through AWS accounts and it looks like one of your accounts has it, one does not. That’s out of Pulumi’s control If you wish to have different settings, you need to define them with: https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketpublicaccessblock/ https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketownershipcontrols/
👍 1
a
awesome! that’s a good place to start looking down
appreciate the point in the right direction @billowy-army-68599. Will try that out and see how it goes
2 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