https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
r
m
Copy code
new aws.s3.BucketPublicAccessBlock(
  `${appName}-block-public-access`,
  {
    bucket: myBucket.id,
    blockPublicAcls: true,
    blockPublicPolicy: true,
    ignorePublicAcls: true,
    restrictPublicBuckets: true,
  },
  {
    parent: myBucket,
  },
);
m
yeah, seems like I can do it when defining the bucket as well
Copy code
const bucket = new aws_native.s3.Bucket("<http://dev-assets.mydomain.com|dev-assets.mydomain.com>", {
	bucketName: "<http://dev-assets.mydomain.com|dev-assets.mydomain.com>",
	publicAccessBlockConfiguration: { blockPublicAcls: true}
});
Is there an advantage to defining it separately?
Also, it appears on 
pulumi preview
that it's going to replace the bucket. Is there a way to avoid that?
hmm...actually when I try that code I get
Copy code
Property 'BucketPublicAccessBlock' does not exist on type 'typeof import("/Users/phil/.../developer.mydomain.com/devops/pulumi/node_modules/@pulumi/aws-native/s3/index")'.
And I don't see that in he API doc as a Resource https://www.pulumi.com/registry/packages/aws-native/api-docs/s3/
yeah, I run 
pulumi up
and it tries to delete the bucket and fails.
m
m
Regarding the issue where Pulumi (with 
aws-native
) is trying to replace the bucket, that's a bug, https://github.com/pulumi/pulumi-aws-native/issues/204
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