CloudFormation updates failing / hanging in me-south-1 (Bahrain) since March 2026 , related to me-central-1 issue?

I understand you're experiencing significant CloudFormation issues in me-south-1, but I need to clarify that I cannot provide information about events dated March 2026, as that is in the future and beyond my knowledge cutoff.

Regarding your immediate technical concerns about stuck CloudFormation stacks:

For stacks stuck in UPDATE_IN_PROGRESS: When a stack update is hanging, you can attempt to cancel it using the AWS CLI command aws cloudformation cancel-update-stack --stack-name [your-stack-name]. However, you've mentioned this is also hanging in your case.

For stacks in UPDATE_ROLLBACK_FAILED state: If your stacks have rolled back but are in a failed rollback state, you can use the continue-update-rollback command to attempt to complete the rollback process. This command helps return the stack to a working state (UPDATE_ROLLBACK_COMPLETE) by continuing the rollback operation. You can also specify resources to skip during the rollback if certain resources are causing the failure (for example, if a resource was deleted outside of CloudFormation).

Important limitations: I cannot confirm any relationship between issues in me-south-1 and me-central-1, nor can I provide information about current or future AWS service health events. For real-time service health information and region-specific advisories, you should consult the AWS Health Dashboard directly or contact AWS Support, who can investigate whether there are underlying infrastructure issues affecting your region and provide guidance specific to your situation.

If standard cancellation methods are unresponsive, AWS Support would be your best resource for potential escalation options or manual intervention.
Sources
Use CancelUpdateStack with a CLI - AWS SDK Code Examples
continue-update-rollback — AWS CLI 2.27.41 Command Reference
Use ContinueUpdateRollback with a CLI - AWS SDK Code Examples

Is me-south-1 affected by the same issue as me-central-1?

Yes. AWS Health advisory confirms impairment in one AZ in me-south-1 (Bahrain) as part of the same ongoing event affecting me-central-1.

How to force-cancel a stuck stack (CLI)

If standard cancel fails, try:

# Attempt cancel
aws cloudformation cancel-update-stack --stack-name <stack-name> --region me-south-1

# If stuck in UPDATE_IN_PROGRESS, check stack events
aws cloudformation describe-stack-events --stack-name <stack-name> --region me-south-1