Make PublicAccessBlockConfiguration optional for cdk bootstrap
See original GitHub issueWe would like to deploy the cdk bootstrap stack without the PublicAccessBlockConfiguration
property.
Use Case
Setting this property is restricted in our organization account.
Proposed Solution
Possible solution:
cdk bootstrap --without-public-access-block-configuration
Other
- 👋 I may be able to implement this feature request
- ⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Bootstrapping - AWS Cloud Development Kit (AWS CDK) v2
Bootstrapping is the process of provisioning resources for the AWS CDK before you ... You can make small modifications to the template before...
Read more >awslabs/aws-cdk - Gitter
I'm trying to run cdk bootstrap --toolkit-bucket-name myBucket , but our environment requires certain tags. Is there a way I can specify tags...
Read more >AWS CDK Toolkit - npm
AWS CDK Toolkit ; cdk deploy, Deploy a stack into an AWS account ; cdk watch, Watches a CDK app for deployable and...
Read more >Exploring Amazon's Cloud Development Kit (CDK)
AWS CDK can create the necessary roles and least-permissions policies ... To deploy our sample application, we will need to bootstrap the AWS...
Read more >Production-Ready CDK - Bootstrapping - Luminis
In CDK v1, the default template is the legacy one, and the modern one is optional as you need to use the context...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@eladb, my company did not give s3 put permission to our organization access key for security reasons. “–without-public-access-block-configuration” it would be nice solution.
@hoegertn it is not that the bucket is public, these rules are managed on the account level and we only have limited access to what we can do within the account. Part of our permission boundary is that we can’t perform
s3:PutPublicAccessBlock
which means that the cdk bootstrap stack fails with the following error: