Fix CRLY.01146: Enforce HTTPS for Elasticsearch Domain#45
Open
curly-review[bot] wants to merge 1 commit intomasterfrom
Open
Fix CRLY.01146: Enforce HTTPS for Elasticsearch Domain#45curly-review[bot] wants to merge 1 commit intomasterfrom
curly-review[bot] wants to merge 1 commit intomasterfrom
Conversation
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.
Issue Details
ID: CRLY.01146
Severity: HIGH
File: sam/cfn/cfn-elasticsearch-domain.json
Remediation Summary
Description
The current configuration of the Elasticsearch Domain does not enforce HTTPS, which can expose sensitive data to potential interception. To enhance security, HTTPS should be enforced for all data in transit.
Steps
AWS::Elasticsearch::Domainresource in your CloudFormation template to include theTLSSecurityPolicyproperty.TLSSecurityPolicyproperty to a policy that enforces HTTPS, such asPolicy-Min-TLS-1-2-2019-07.Here is an example of how to update the CloudFormation template: