Skip to main content

Use Case for AWS Elasticsearch Domains should leverage ARM instances

  1. Configure AWS Elasticsearch Domains should leverage ARM instances
  2. Use Case for AWS Elasticsearch Domains should leverage ARM instances
  3. Triage Guides by Violation Type
    1. Triage AWS Elasticsearch Domains should leverage ARM instances NON_ARM_INSTANCE_TYPE_DETECTED

Use Case for AWS Elasticsearch ARM Instance Checker

The AWS Elasticsearch ARM Instance Checker policy is designed to help organizations identify and track AWS Elasticsearch instances that are not using ARM-based instance types. This policy is particularly useful for optimizing costs and performance, as ARM instances can provide better price to performance ratio compared to their non-ARM (Intel or AMD) counterparts.

Pros of Using this Policy​

  • Cost Efficiency: ARM instances can be more cost-effective than traditional x86 instances.
  • Performance: ARM instances may offer better performance for certain applications.
  • Modernization: Encourages the adoption of newer, potentially more energy-efficient architecture.

Cons of Using this Policy​

  • Compatibility: Some applications might not be fully compatible with ARM architectures.

How the Policy Works​

The policy function retrieves the instance type of the provided AWS Elasticsearch domain and reports it. The observation is evaluated by the policy expression to determine if the instance type is a non-ARM instance.

Variables​

  • There are no variables with defaults needed as the policy checks for non-ARM instance types, which is a binary condition.

Violation Type IDs​

  • NON_ARM_INSTANCE_TYPE_DETECTED: Indicates that the Elasticsearch instance is running on a non-ARM instance.