Conversation
OfekShimko
approved these changes
Apr 12, 2026
talazuri
approved these changes
Apr 12, 2026
Saarett
pushed a commit
that referenced
this pull request
Apr 12, 2026
…heck CKV_AWS_70 (#7514) add aws:VpceAccount to recognized condition keys in check CKV_AWS_70
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Description
Customer is experiencing a false positive with Checkov policy CKV_AWS_70 ("Ensure S3 bucket does not allow an action with any Principal").
The policy currently fails whenever an AWS resource policy uses the aws:VpceAccount condition key to restrict access.
In this PR the condition aws:VpceAccount is being added to the conditions list in policy CKV_AWS_70.
Fixes PCSUP-30968
Checklist: