Fix CRLY.01060: Encrypt Elasticsearch data at rest #40
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.
Issue Details
ID: CRLY.01060
Severity: HIGH
File: sam/cfn/cfn-elasticsearch-domain.json
Remediation Summary
Description
The security finding indicates that data stored in the Elasticsearch domain is not encrypted at rest. This poses a risk as it leaves sensitive data vulnerable to unauthorized access.
Steps
To ensure the data stored in the Elasticsearch domain is securely encrypted at rest, you need to add the
EncryptionAtRestOptionsproperty to theAWS::Elasticsearch::Domainresource in your CloudFormation template.Here is the updated CloudFormation template snippet with the required changes: