This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
As lead solutions architect for the AWS Well-Architected Reliability pillar , I help customers build resilient workloads on AWS. Figure 2 shows the four strategies for DR that are highlighted in the DR whitepaper. All requests are now switched to be routed there in a process called “failover.” Multi-site active/active.
The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. What if the very tools that we rely on for failover are themselves impacted by a DR event? Failover plan dependencies and considerations. What are the dependencies that we’ve baked into this failover plan?
In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Increase resiliency. In the following sections, we show you the steps we took to improve system resiliency for our example company. Conclusion.
This architecture pattern follows the option of the “Multi-Account Decentralized” model as described in the whitepaper Hybrid Cloud DNS options for Amazon VPC. This architecture provides the following benefits: Resilient and scalable. Failover routing policy is set up in the PHZ and failover records are created.
We organize all of the trending information in your field so you don't have to. Join 25,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content