Submit feedback on
Unnecessary Multi-AZ Deployment for Non-Production EC2 Instances
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Unnecessary Multi-AZ Deployment for Non-Production EC2 Instances
Swapna Samuel
Service Category
Compute
Cloud Provider
AWS
Service Name
AWS EC2
Inefficiency Type
Misconfigured Redundancy
Explanation

Multi-AZ deployment is often essential for production workloads, but its use in non-production environments (e.g., development, test, QA) offers minimal value. These environments typically do not require high availability, yet still incur the full cost of redundant compute, storage, and data transfer. This results in unnecessary spend without operational benefit.

Relevant Billing Model

EC2 is billed based on instance runtime and size, with additional charges for inter-AZ data transfer and supporting infrastructure (e.g., EBS volumes, load balancers). Multi-AZ deployments double resource usage and introduce cross-AZ networking costs.

Detection
  • Review EC2 instances in non-production environments for Multi-AZ configuration
  • Check for Auto Scaling Groups or load balancers distributing traffic across multiple Availability Zones
  • Evaluate network transfer charges between Availability Zones
  • Verify with workload owners whether fault tolerance is required for the environment
Remediation
  • Reconfigure EC2 workloads in non-production environments to use a single Availability Zone
  • Avoid distributing instances or traffic across multiple AZs unless justified by a specific requirement
  • Establish environment-based architectural guidelines to limit Multi-AZ usage
Submit Feedback