Skip to main content

Use Case for AWS RDS should use ARM Instances

  1. Configure AWS RDS should use ARM Instances
  2. Use Case for AWS RDS should use ARM Instances
  3. Triage Guides by Violation Type
    1. Triage AWS RDS should use ARM Instances NON_ARM_PROCESSOR

AWS RDS Graviton2 Instances

Introduction​

This policy ensures that all Amazon RDS instances are using the Graviton2 (arm64) processor. Graviton2 processors provide better performance and cost efficiency, offering up to 19% better performance at 20% lower cost compared to other processor options.

Pros​

  • Cost Savings: By using Graviton2 processors, you can reduce the cost of running RDS instances by up to 20%.
  • Improved Performance: Graviton2 processors deliver up to 19% better performance, leading to faster database operations and better overall application performance.

Cons​

  • Migration Effort: If your existing instances are not using Graviton2, you may need to perform a migration, which involves some effort and planning.
  • Compatibility: Ensure that your applications and dependencies are compatible with the arm64 architecture before migrating to Graviton2.

How the Policy Works​

This policy evaluates whether each RDS instance is using a Graviton2 processor by examining the instance class name. Instance classes starting with 'db.m6g' or 'db.r6g' indicate that the instance is using a Graviton2 processor.

Variables​

  • None: This policy does not require any additional variables.

Violation Types​

  • NON_GRAVITON_PROCESSOR: Indicates that the RDS instance is not using a Graviton2 processor.

Conclusion​

Using Graviton2 processors for your RDS instances can yield significant cost savings and performance improvements. This policy helps ensure that all your RDS instances are optimized by using Graviton2 processors.