Determine if the Elasticsearch (ES) instances (including dedicated master instances) provisioned in your AWS account have the desired instance type established by your organization based on the workload deployed. Cloud Conformity provides you with the ability to define the desired Elasticsearch instance types based on your workload requirements upon enabling this conformity rule.
This rule can help you with the following compliance standards:
This rule can help you work with the AWS Well-Architected Framework
This rule resolution is part of the Cloud Conformity Security & Compliance tool for AWS
Setting limits for the type of Amazon Elasticsearch instances provisioned in your AWS account will help you address organizational compliance requirements and prevent unexpected charges on your AWS bill.
Note 1: You can also limit your Elasticsearch cluster instances to the desired instance type using AWS Organizations service by implementing your own Service Control Policy on the master account. A Service Control Policy (SCP) is a type of policy that you can use to manage your organization. SCPs enable you to restrict what resources, services and actions the users, groups, and roles in those AWS accounts can use.
Note 2: The desired Elasticsearch instance type used as example within this rule is c4.large.elasticsearch. To meet your organizational requirements, you will need to configure this rule with your own desired instance type.
To determine if the Elasticsearch (ES) instances launched in your AWS account have the desired instance type, perform the following:
Remediation / Resolution
To limit the new AWS Elasticsearch cluster instances to the desired type, create an AWS support case where you explain why you need this type of limitation. For any existing Elasticsearch clusters launched without using the desired instance type, just update their configuration by changing the Instance type and Dedicated master instance type config parameters to the desired type (e.g. c4.large.elasticsearch).
To create the required AWS support case, perform the following actions:
Unlock the Remediation Steps
Gain free unlimited access
to our full Knowledge Base
Over 750 rules & best practices
Get started for FREE
You are auditing:
Elasticsearch Desired Instance Type
Risk level: Medium