ElastiCache Non-Graviton Instance
Graviton node types are priced lower than the equivalent x86 types for the same node size.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Move the ElastiCache node to Graviton. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- ElastiCache on AWS
- The fix, by hand
- Verify the engine version is current (Redis ≥6.x, Memcached ≥1.6.x).
- Open ElastiCache → select cluster → Modify → Node type → pick the cache.*g equivalent (cache.r6g.large etc.).
- Apply immediately for cluster-mode-enabled Redis (online); for cluster-mode-disabled apply during a maintenance window.
- Verify client reconnection + cache hit ratio post-migration.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1517- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.