Ensure that the number of Elastic MapReduce (EMR) cluster instances (master and core instances) provisioned in your AWS account has not reached the limit quota established by your organization for the EMR workload deployed. By default, Cloud Conformity sets a threshold value of 5 for the maximum number of provisioned instances, however, you have the capability to adjust this threshold based on your organization requirements upon enabling this rule. Once you define your own threshold for the maximum number of Elastic MapReduce instances that you need to run across all AWS regions, Cloud Conformity engine will start to continuously check your account for EMR instances and when the number of instances reach the specified count (threshold) you will get notified via communication channels configured within your Cloud Conformity account. If the EMR 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 EMR instances based on your requirements.
This rule can help you with the following compliance standards:
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.
Monitoring and setting limits for the maximum number of Elastic MapReduce cluster instances provisioned within your AWS account will help you to manage better your EMR compute resources, prevent unexpected charges on your AWS bill and act fast to mitigate attacks. For example, users within your organization can create more EMR instances than the number established in the company policy, exceeding the monthly budget allocated for cloud computing resources. Furthermore, if your AWS account security has been compromised and the attacker is able to create a large number of EMR resources within your account, you risk to accrue a lot of AWS charges in a short period of time and this can affect your business.
Note: The threshold for the maximum number of EMR instances per AWS account set for this conformity rule is 5 (default value).
To determine the number of Elastic MapReduce (EMR) instances (master and core instances) currently available within your AWS account, perform the following:
Remediation / Resolution
To build an AWS support case in order to limit the number of provisioned Elastic MapReduce cluster instances based on your requirements, perform the following actions:Note: Requesting a limit for the number of EMR instances per region using the AWS API via Command Line Interface (CLI) is not currently supported.
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:
EMR Instances Counts
Risk level: Medium