What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Amazon Web Services reportedly waived all usage-related charges incurred in its ME-CENTRAL-1 Region during March 2026 after a reported March 1 drone strike disrupted AWS facilities in the Middle East. The relief was described as automatic for affected customers, but it was not a free month of AWS worldwide: the reported waiver names one region, one month, and usage-related charges.
The incident and billing decision were reported by Network World. AWS also reportedly said that billing and usage data was not deleted, even though March usage would not appear normally in Cost Explorer or Cost and Usage Reports after the waiver was processed.
As an Amazon Associate I earn from qualifying purchases.
What AWS actually waived
The quoted AWS customer notice covered all usage-related charges in ME-CENTRAL-1 for March 2026. That is materially narrower than “Amazon waived an entire month of AWS charges.” It does not establish that AWS made every account free for March or erased every type of invoice item.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBased on the available reporting, customers should distinguish the regional waiver from:
#1 Best Overall
- Usage generated in other AWS Regions;
- Support-plan fees;
- AWS Marketplace or third-party purchases;
- Taxes and other account-level charges;
- Reserved capacity or Savings Plans commitments; and
- Charges whose treatment depends on a contract, reseller, or consolidated-billing arrangement.
The available report does not publish a complete eligibility policy or a definitive list of excluded billing categories. The safest interpretation is that qualifying usage in the named region and month was waived automatically, while customers remain responsible for verifying how the adjustment was applied to their accounts.
ME-CENTRAL-1 is not the same as ME-SOUTH-1
The reported attack damaged or disrupted AWS facilities in ME-CENTRAL-1 in the United Arab Emirates and ME-SOUTH-1 in Bahrain. However, the quoted waiver specifically names ME-CENTRAL-1. The available reporting does not establish that Bahrain received an identical March-wide waiver.
That distinction matters for customers with workloads in both regions. A company should not assume that disruption in both locations means the same billing treatment applied in both locations.
What happened to AWS infrastructure?
According to AWS service-health information relayed by Network World, the March 1 strikes caused structural damage, power-delivery disruption, fire-suppression activity, and water damage. Reported effects included problems involving EC2, S3, DynamoDB, Lambda, Kinesis, CloudWatch, RDS, the AWS Management Console, and the command-line interface.
The incident has been reported as involving Iranian drone attacks. Claims about the facilities’ alleged military or intelligence role should remain attributed to the sources making them; the available material does not independently establish that motive.
Why March usage may disappear from normal billing reports
AWS reportedly clarified that waived March usage would not appear normally in Cost Explorer or Cost and Usage Reports once the waiver was processed. That can look like missing accounting data, but it is different from saying the records were destroyed.
AWS reportedly said the underlying billing and usage data remained available upon request. The available report does not specify the request procedure, retention period, file format, or whether every resource-level and timestamp field would be available.
This distinction is important because cloud billing data often supports more than payment. It can help teams:
- Attribute resources to departments and projects;
- Reconcile internal budgets and chargebacks;
- Identify unexpected or idle infrastructure;
- Reconstruct resource activity during an incident;
- Support audits and compliance reviews; and
- Investigate security events.
Cloud-finance commentator Cory Quinn described the AWS bill as a potentially important infrastructure record, but that is expert commentary rather than a universal legal or technical definition.
What affected customers should do
- Review AWS communications. Check account email, billing notices, and the Billing console for the applicable adjustment.
- Confirm the scope. Verify the covered month, region, linked account, and whether the adjustment is shown as a waiver, credit, or omitted usage.
- Check other charges. Review usage outside ME-CENTRAL-1, support, Marketplace, tax, commitment, and reseller charges separately.
- Preserve available reports. Export Cost Explorer views and available Cost and Usage Reports before relying on normal historical access.
- Request underlying records. Ask AWS, the account team, or a reseller how to obtain March billing and usage data if ordinary reports omit it.
- Reconcile independently. Compare the data with CloudTrail, application logs, Kubernetes records, infrastructure-as-code state, resource inventories, and internal allocation records.
- Preserve compliance evidence. Keep exports, logs, approvals, and correspondence needed for audits, security investigations, or insurance claims.
- Review recovery design. Confirm that backups and replicas exist outside the affected failure domain and that restoration has actually been tested.
Why the waiver is unusual—but not an SLA guarantee
Ordinary AWS service-level credits are generally tied to published service commitments and formulas. The reported March waiver appears broader than a conventional service-specific SLA credit, but the available reporting does not establish that it was formally issued under an SLA.
Customers should therefore avoid treating this decision as evidence that AWS will automatically reimburse every future regional outage. Its scope may depend on the customer communication, account structure, contract, and affected region.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The cloud-resilience lesson
The incident illustrates why a cloud region is not the same thing as an invulnerable physical shelter. A multi-region design may still share network, identity, DNS, logistics, provider, or geopolitical dependencies. A second AWS Region may also be insufficient if it lies within a related physical or conflict-risk area.
Organizations reviewing resilience should ask:
- Can critical workloads run outside the primary geography?
- Are backups stored in a genuinely independent failure domain?
- Are DNS, certificates, secrets, identity, queues, and deployment systems recoverable?
- Are recovery quotas, images, permissions, and third-party integrations ready?
- Can the organization operate with another provider or on-premises environment if necessary?
- Has failover been tested against the required recovery-time and recovery-point objectives?
Services such as AWS Billing and Cost Management, AWS Backup, and AWS Elastic Disaster Recovery may support parts of this work, but none automatically creates geographic independence. Multi-cloud can reduce provider concentration while adding duplicated tooling, skills, security controls, networking, data-transfer costs, and operational complexity.
What remains unclear
The public reporting does not fully answer several practical questions:
- The complete eligibility criteria and any contract exceptions;
- Whether ME-SOUTH-1 received equivalent relief;
- Which billing categories were included or excluded;
- How customers should request underlying billing records;
- How long those records will remain available; and
- Whether all affected services received identical treatment.
Until AWS provides a broader public policy or account-specific documentation, customers should rely on their own AWS notices, billing records, account team, or reseller rather than assume that every AWS charge was removed.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
