-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
feat(aws-s3): adds s3 bucket aws fsbp option #10970
Conversation
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
This adds an option to enforce aws foundational best practices for s3 buckets. Closes aws#10969 Signed-off-by: Christopher Mundus <chris@kindlyops.com>
29e7863
to
bd5b894
Compare
Hi @ crashGoBoom! Generally we prefer to encode best practices as defaults in the L2 constructs. Individual properties, such as the the |
Removes enforceSecurityBestPractice property and only uses SSL statement enforcement. Signed-off-by: Christopher Mundus <chris@kindlyops.com>
Pull request has been modified.
Signed-off-by: Christopher Mundus <chris@kindlyops.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one comment about the doc. Feel free to tag me so I can merge this once updated! Thanks!
Signed-off-by: Christopher Mundus <chris@kindlyops.com>
Pull request has been modified.
Signed-off-by: Christopher Mundus <chris@kindlyops.com>
@NetaNir Hi! This has been updated. Let me know if there is anything else. Thanks so much! |
@Mergifyio update |
Command
|
Hi @crashGoBoom see mergify comment above, you will need to update your branch so I can merge it. |
Ok I just updated sorry about that! @NetaNir |
Co-authored-by: Neta Nir <neta1nir@gmail.com>
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@NetaNir ok looks like it should be ready to go now. |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Hmm, looks like this might have failed to allow access since this PR is coming from an ORG repo instead of a user repo. I am not seeing the options to allow changes to be pushed to this fork so I am guessing thats what it is. @NetaNir Any ideas if its possible to use this org fork or should this PR be closed and opened with my user instead of our org? Thanks and sorry for the hassle! |
Closed in favor of #12804 |
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*
This adds an option to enforce aws foundational best practices for s3 buckets.
Closes #10969
Signed-off-by: Christopher Mundus chris@kindlyops.com
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license