Ensure that the number of Amazon OpenSearch cluster nodes (including dedicated master nodes) provisioned in your AWS cloud account has not reached the limit quota established by your organization for the OpenSearch workload deployed. By default, Trend Micro Cloud One™ – Conformity sets a threshold value of 50 for the maximum number of provisioned cluster nodes, however, you can adjust this threshold based on your AWS cloud resource policy upon enabling the rule. Once you define your own threshold for the maximum number of OpenSearch cluster nodes that you need to run across all AWS regions, the Conformity engine will start to continuously scan your account for cluster nodes and when the number of nodes reach the specified threshold you will get notified via the communication channels configured within your Conformity account. If the OpenSearch compute capacity limit quota defined for your AWS account is reached, you can raise an AWS support case where you can request to limit the number of provisioned Amazon OpenSearch cluster nodes.
This rule can help you with the following compliance standards:
- APRA
- MAS
For further details on compliance standards supported by Conformity, see here.
This rule can help you work with the AWS Well-Architected Framework.
This rule resolution is part of the Conformity Security & Compliance tool for AWS.
optimisation
Monitoring and configuring limits for the number of OpenSearch cluster nodes provisioned within your AWS cloud account will help you to manage better your OpenSearch resources, prevent unexpected charges on your AWS bill, and act fast to mitigate attacks that can use OpenSearch resources. For example, users within your organization can create more OpenSearch cluster nodes than the number established in the company resources policy, exceeding the monthly budget allocated for cloud computing resources. Another example could be a misconfiguration in your Amazon CloudFormation template that can lead to launching more cluster nodes than required. Also, if your AWS account security is compromised and the attackers have the capability to provision a large number of OpenSearch cluster nodes in order to run their malicious data analytics tools, you risk to accrue a lot of AWS charges in a short period of time.
Note: The threshold for the maximum number of OpenSearch cluster nodes per AWS account set for this conformity rule is 50 (default).
Audit
To determine the number of Amazon OpenSearch cluster nodes (data and dedicated master nodes) available within your AWS account, perform the following actions:
Remediation / Resolution
To ensure that the provisioning of Amazon OpenSearch cluster nodes is limited to a certain number, perform the following actions:
Note: Creating a support case to request OpenSearch node count limitations using the AWS Command Line Interface (AWS CLI) is not currently supported.References
- AWS Documentation
- Amazon OpenSearch Service FAQs
- Amazon OpenSearch Service quotas
- What is Amazon OpenSearch Service?
- AWS Command Line Interface (CLI) Documentation
- es
- list-domain-names
- describe-elasticsearch-domain
Unlock the Remediation Steps
Free 30-day Trial
Automatically audit your configurations with Conformity
and gain access to our cloud security platform.
You are auditing:
Total Number of Cluster Nodes
Risk Level: Medium