This message was deleted.

hey Harrison, We can definitely help. Can you provide more information about the changes you’re seeing ?

sure! to start the newer deployment has the s3 bucket ‘Block public access’ turned on where the old has it turned off

can you share code? screenshots? anything that could help us debug?

here is what we have for the bucket:

export const appAssetsBucket = new aws.s3.Bucket(`${config.commonName}-assets`, {
  acl: "private",
  tags: Object.assign({ Name: `${config.commonName}-assets` }, commonTags)
});

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/

awesome! that’s a good place to start looking down