AWS outage: ctrl:advisory on disruption and response

Today’s AWS outage is a reminder that even major cloud platforms can fail. If your data protection sits only on one provider, you need a plan B. Verify backups, diversify storage, and test recovery so you’re not caught off guard. No provider is immune. https://hubs.li/Q03Pp3_00

The recent AWS outage highlighting Signal's reliance on dominant cloud providers underscores a critical issue in the tech landscape: centralized infrastructure. As cybersecurity and cloud experts, we must advocate for diversified solutions that empower resilience. It's essential for IT leaders to strategically assess their cloud partnerships and invest in alternatives that promote security, reliability, and innovation. In a world where dependency is nearly unavoidable, building a robust framework can mitigate risks and drive success.

This week’s AWS outage was a reminder of how dependent most of us are on just a small handful of infrastructure providers. Even if you thought your company was safe because they don’t use AWS directly, you may now realize many of your high or critical vendors do: which means you’re still affected when it goes down. This is where a fourth-party vendor list becomes crucial. Knowing who your vendors rely on helps you understand your real exposure when major platforms experience downtime. This list gives your team faster visibility during incidents, helps you communicate clearly with internal teams and customers, and gives you a more realistic view of your operational resilience. Seem daunting? Try starting with your high and critical vendors: the ones whose downtime would most impact your company or customers. Review their SOC 2 reports or other security documentation to identify which cloud or infrastructure providers they depend on. You might be surprised how often the same names appear again and again: AWS, Cloudflare, Google Cloud, Stripe, MongoDB, or even OpenAI. Even one of these having a bad day can ripple across your entire workflow. So, who do your vendors rely on?

🚨 The AWS outage was a reminder: even the biggest cloud platforms aren't immune to disruption. This is why Disaster Recovery isn't optional - it's essential. Whether you're in healthcare, finance or retail, your cloud strategy must account for the unexpected... 💾 Keeping a copy of your data outside the public cloud is a survival strategy. 🔐 Private cloud providers like CT offer resilient, tailored architectures. 🤝 When outages hit, direct access to support matters. Let's talk about building a cloud strategy that's not just scalable, but survivable. Read more in our latest blog 👇 https://lnkd.in/eR3eSpmX #Cybersecuritymonth

Resilience doesn't just happen; you have to build it intentionally. Set up your systems across multiple regions, use separate DNS providers, and regularly test your backup plans. Don't put all your eggs in one basket. The recent AWS outage in US-EAST-1 proved this point. A networking and DNS issue took down services that were too dependent on a single region, even though they were in the cloud. The lesson? If everything's connected to one place, a single problem can turn into a major outage.

Just going to leave this here......https://lnkd.in/ejgAYYqm service level agreements for aws. The biggest and most quoted reason for electing to use cloud - availability. And the sheer amount of people who question cloud or network provider unavailability as a risk! In one week, we have had vodaphone and aws outages! Resiliency is not when you put all your eggs in someone else's basket....

Security patches are ending, compliance exposure is rising, and infrastructure costs are climbing. But here’s the good news migrating to Atlassian Cloud with Clovity brings: ✅ Continuous updates & FedRAMP compliance ✅ Cloud automation & AI-driven efficiency ✅ Up to 40% cost reduction Don’t let delay turn into downtime. #AtlassianCloud #Clovity #CloudMigration #AtlassianPartner #DigitalTransformation #CloudSecurity #FedRAMP #Compliance

NEW: Microsoft Entra introduces soft deletion and restoration for cloud security groups! This feature allows deleted groups to be restored within 30 days, preserving their settings, ownership, and membership, reducing the need to rebuild access models from scratch. 𝐖𝐡𝐞𝐧 𝐭𝐡𝐢𝐬 𝐰𝐢𝐥𝐥 𝐡𝐚𝐩𝐩𝐞𝐧: Public preview: Rollout began in late in October 2025 and is expected to complete by early November 2025. General availability (Worldwide): Rollout begins in late February 2026 and is expected to complete by early March 2026.

Microsoft Azure went offline today due to an inadvertent configuration change affecting Azure Front Door (AFD), which disrupted DNS and routing services globally. • Outage began: ~11:40 a.m. ET • Full recovery: By 7:30 p.m. ET, services were restored across all regions. Experts warn that resilience gaps remain in cloud infrastructure, even among top providers like Microsoft and AWS. This incident highlights the risks of centralized internet dependencies.

Companies relying on software-as-a-service systems dependent on AWS experienced outages, akin to a widespread internet disruption. External losses, such as reputational damage or lost revenue due to outages, are typically not recoverable. If a system built on AWS experiences a nine-hour outage, the resulting damage must be absorbed. While negotiating with cloud computing providers is advisable, obtaining cash compensation for incurred damages and extraneous factors like reputational harm is unlikely. The extensive reach of AWS highlights its systemic importance, impacting numerous major systems and even other cloud providers. #CloudComputing #AWS #SoftwareAsAService #SystemOutage #TechResilience