Switch to AWS Graviton Instances to Reduce Compute Costs

Quick Answer

Graviton is the right lever here because the two constraints in the scenario, no architecture-specific licensing restriction and a requirement to avoid custom operational scripts, both point toward a change that only requires re-evaluating the underlying instance family rather than rearchitecting how the workload runs. Since the software is open source and not tied to a particular CPU architecture, it can generally run on Graviton's ARM-based instances without code changes, and AWS provides native support for them, so no custom scripts or special handling are needed to make the switch. The 'after performance testing' qualifier matters too: price-performance gains are workload-dependent, so validating that the application behaves correctly and performs well on ARM before committing is part of doing this safely, not an optional step. This is a cleaner win than something like manually re-tuning instance sizes or building automation to manage a more complex scaling setup, because it reduces cost at the infrastructure layer without adding operational surface area. When a question emphasizes a workload with no architecture lock-in and asks for lower compute cost while avoiding new operational complexity, that combination is a strong signal that a Graviton migration, rather than a scripted or architectural workaround, is the intended answer.