Evidence search
Search
Search titles, summaries, topics, providers, authors, and the full open-access corpus.
Results for “Failover”
19 publicationsRoll out configuration changes as carefully as code
Flags, policy rows, generated files and customer settings triggered several global outages between 2024 and 2026. Seven primary incident reports show how each change slipped past its safeguards, and which controls their authors adopted afterward.
Resilience · Amazon Web Services / Microsoft Azure / Google Cloud / Cloudflare / CrowdStrike · By Cloud Security DeskFind the AWS global control planes in your recovery path
Thirteen AWS control planes run in us-east-1 or us-west-2, and ordinary calls from other Regions still reach them. Audit runbooks, SDK settings and the last exercise, then swap each dependency for a data-plane operation.
Resilience · Amazon Web Services · By Cloud Security DeskTune managed WAF rules without opening a bypass
Fix a managed WAF false positive by changing one rule for one route, then decide what happens to the request body bytes AWS WAF, Azure WAF and Cloud Armor never inspect.
Workload security · Amazon Web Services / Microsoft Azure / Google Cloud · By Cloud Security DeskPlan for an outage at your CDN or edge provider
When the CDN, WAF and edge provider fails, traffic can move to a regional WAF, a second CDN or the origin, and each keeps less protection. Decide early whether a second path is worth securing.
Resilience · Microsoft Azure / Cloudflare / Amazon Web Services / Google Cloud · By Cloud Security DeskPlan Azure disaster recovery for a region without a pair
Thirteen Azure regions have no pair and eight more pair with a restricted-access region. This guide shows which built-in geo-redundancy disappears, what replaces it service by service, and how to choose the recovery region.
Resilience · Microsoft Azure · By Cloud Security DeskContain failures with cell-based architecture and shuffle sharding
Cells limit a failure to the tenants behind one partition only when routing, data and change delivery are partitioned too. Here is how to choose the key, size cells and check the shuffle-sharding arithmetic.
Resilience · AWS / Microsoft Azure / Slack · By Cloud Security DeskDesign health checks that remove broken instances without causing outages
A health check is an automated decision to remove capacity. Keep load balancer checks local, learn what your platform does when every target fails, and set probe timing from documented defaults.
Resilience · Amazon Web Services / Microsoft Azure / Google Cloud / Kubernetes · By Cloud Security DeskPlan for the backlog that follows a regional cloud outage
AWS fixed the DNS fault behind its October 2025 us-east-1 outage within three hours, yet recovery ran into the afternoon. Design retries, queues and capacity automation for that second phase.
Resilience · Amazon Web Services · By Cloud Security DeskChoose a multi-region database consistency model before you need failover
The replication model decides which writes survive a Region failure. Compare asynchronous and quorum options in DynamoDB, Aurora, Spanner and Cosmos DB by recovery point, write latency and the reconciliation each one leaves you.
Resilience · Amazon Web Services / Google Cloud / Microsoft Azure · By Cloud Security DeskHandle Azure OpenAI rate limits without retry storms
Separate deployment quota, short request bursts and bounded client retry behavior.
AI systems · Azure · By Cloud Security DeskPlan Kubernetes drains around the disruption budget
Review selector scope, current status, unhealthy Pod handling and replacement capacity before treating a blocked drain as a reason to bypass availability controls.
Resilience · Kubernetes · By Cloud Security DeskDiagnose NAT gateway port exhaustion before adding capacity
Match allocation errors to destination tuples and gateway mode before changing connection pools, addresses or routes.
Resilience · AWS · By Cloud Security DeskDesign RDS IAM authentication around the connection pool
Generate IAM database tokens for the physical connections that need them, and keep token validity separate from the lifetime of an already-established SQL session.
Workload security · AWS · By Cloud Security DeskFind the shared dependencies behind a cloud outage
Use the June 2025 Google Cloud and Cloudflare reports to review shared runtime, control, identity and recovery dependencies without turning one outage into a provider ranking.
Resilience · Google Cloud / Cloudflare / AWS · By Cloud Security DeskRecovery objectives that match the cloud service
Define the business function, outage clock, recoverable data and dependency assumptions before choosing a cloud disaster-recovery architecture.
Resilience · AWS / Azure / Google Cloud / NIST · By Cloud Security DeskPrepare cloud workloads for hybrid post-quantum TLS
Hybrid support in a library is not proof that every TLS hop uses it. Verify negotiation, compatibility and fallback while keeping certificate authentication separate.
Workload security · IETF / NIST / OpenSSL / Cloudflare · By Cloud Security DeskThe bottlenecks that shape a cloud DDoS response
Distinguish bandwidth, packet processing, connection state and application work before choosing a DDoS response or assuming the whole service path is protected.
Resilience · AWS / Azure / Google Cloud / Cloudflare · By Cloud Security DeskWhere DNS failover loses control of the clock
Separate authoritative routing, resolver caches, stale answers, runtime caching and existing connections when describing what DNS failover can achieve.
Resilience · AWS / Cloudflare / Oracle · By Cloud Security DeskMake regional failover work without new infrastructure
Prepare capacity, dependencies, and the routing control path before an incident, then measure when clients reach an accepted recovery service.
Resilience · AWS · By Cloud Security Desk