Blogs

Various Non-EC2 Services it is applicable for:

• Amazon RDS
• Amazon Elasticache
• Amazon ElasticSearch

Why move PulmCrit- Timed & titrated use of steroid in COVID-19? tren ace max president trump signs drug pricing executive orders: how will they impact pharma and providers? to Graviton2?

The following are some of the reasons for moving to Graviton2:

• Graviton2 instances provide seven times the performance, four times the number of compute cores, two times larger private caches per core, five times faster memory, and two times faster floating-point performance per core over the first-generation AWS Graviton processors.
• Graviton2 processors feature always-on fully encrypted DDR4 memory and are 50% faster per core encryption performance.
• AWS RDS Graviton2 instances provide up to 52% price/performance improvement for RDS open-source databases depending on the database engine, version, and workload. They also provide up to 35% price/performance improvement for Aurora depending on database size.
• AWS Elasticache Gravitron2 instances provide up to 45% price/performance improvement over previous generation instances.
• AWS Elasticsearch Service Graviton2 instances provide up to 44% price/performance improvement over previous generation instances.

 
Benefits of Graviton2 over Graviton:

Source: AWS
 

Steps to modify

Amazon RDS

• Upgrade the database (if necessary):
  • Determine if the current database version meets the minimum required version for moving to Graviton2.
  • Upgrade the database engine to the required minimum version.
• Modify the instance types:
  • Modify the instance class of your instances to the appropriate Graviton2 instance.
• Validate and confirm that the application works correctly.
• Rollback (if required).

Amazon Elasticsearch

• Upgrade the ES version(if necessary):
  • Determine if the current ES version meets the minimum required version for moving to Graviton2.
  • Upgrade the ES version to the required minimum version(7.9).
• Modify the instance types:
  • Modify the data nodes instance type to Graviton2
  • Modify the instance type of dedicated master nodes as well.
• Validate and confirm that the application works correctly.
• Rollback (if required).

Amazon Elasticache

• Upgrade the Elasticache engine version (if necessary):
  • Determine if the current Elasticache version meets the minimum required version for moving to Graviton2.
  • Upgrade the Elasticache engine to the required minimum version (Redis 5.0.6 and Memcached version 1.5.16).
• Modify the instance types:
  • Modify the Node type to the appropriate Graviton2 instance.
• Validate and confirm that the application works correctly.
• Rollback (if required).