-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aws-s3] Enforce AWS Foundational Security Best Practice #10969
[aws-s3] Enforce AWS Foundational Security Best Practice #10969
Comments
This adds an option to enforce aws foundational best practices for s3 buckets. Closes aws#10969 Signed-off-by: Christopher Mundus <chris@kindlyops.com>
This adds an option to enforce aws foundational best practices for s3 buckets. Closes aws#10969 Signed-off-by: Christopher Mundus <chris@kindlyops.com>
Instead of adding enforcement options to all resources I would love to have an aspect for this that traverses all resources in the stack. |
This is a great idea and I think a good way to handle this may be by using Aspects. Here is a rough sketch:
This would allow for a more flexible approach and update the checks in one spot as opposed to the individual resource. Feel free to let me know if you think using Aspects would work out or if there are any limitations you may know of and I will update my PR. Thanks! |
Commented on the PR. I suggest we add the |
Hi! I updated my PR for the s3 bucket specific enforceSSL option. You raise some good questions as far as how this would be implemented across CDK. My original thought was it would be enabled per resource that is addressed with the AWS Foundational Security Best Practice with a public property along the lines of I am not 100% sure how Aspects would come into play besides maybe checking for compliance of the AWS FSBP and perhaps throwing an error or warning. I have some test code that checks for s3 compliance working here and it would only be a matter of figuring out where this code would live and how this gets enabled (assuming cli flag or maybe we change the error to warnings and it can be enabled by default?):
That being said I totally understand if the team feels that this is out of scope for CDK to provide these kinds of helpers. 👍 |
This adds an option to enforce ssl for s3 buckets. Closes #10969 Signed-off-by: crashGoBoom <crashGoBoom@users.noreply.github.com> Replaces the PR #10970 as it was created with an ORG fork which is not compatible with the required option "Allow edits by maintainers". FYI @NetaNir ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
It would be nice to have the ability to enforce AWS Foundational Security Best Practice through CDK.
Use Case
When creating s3 buckets AWS FSBP should be followed.
Proposed Solution
And behind the scenes it will block all public access and enforce data transmission over HTTPS.
A PR is ready to go which introduces a simple way of adding these controls for s3 buckets.
Other
This is really just to get the conversation started around enforcing the AWS FSBP controls as a default for CDK and perhaps this could be a first step into helping prevent AWS users from using defaults which are not secure.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: