#500 Added new rule for Kendra Index KmsKeyId #501
Merged
Conversation
This file contains 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
phelewski
force-pushed
the
feature/500_kendra_index_kms_key_id
branch
from
4942f85 to
1fbe9d6
Compare
pethers
added a commit
to Hack23/sonar-cloudformation-plugin
that referenced
this pull request
Jan 2, 2021
|
@arothian can you please review this ? |
arothian
approved these changes
Jan 18, 2021
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.
Closes #500
Adds new rule to check and ensure that a
KmsKeyIdis set when creating aAWS::Kendra::Indexresource. Also ensures that theServerSideEncryptionConfigurationproperty is declared as that is required to specify theKmsKeyIdsub-property.