{"id":79710,"date":"2021-09-20T03:40:45","date_gmt":"2021-09-20T09:10:45","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=79710"},"modified":"2021-09-20T03:40:45","modified_gmt":"2021-09-20T09:10:45","slug":"chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/","title":{"rendered":"Chaos Engineering and AWS Fault Injection Simulator &#8211; Supratip Banerjee"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">In May 2017, at London&#8217;s two of the busiest airports, British Airways grounded all of its flights. <\/span><span style=\"font-weight: 400;\">That day 75,000 passengers of British airways were impacted because of an IT failure. <\/span><span style=\"font-weight: 400;\">Airline investigations reported that it was the case of poor resilience and lack of proper disaster recovery after a power surge at a UK-based data center.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The CEO of British Airways recently explained how that one IT failure cost the company 80 Million Pounds!<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Even in your companies, failures are bound to happen.<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">\u201cMany unknown factors can not be anticipated in the regular testing scenario for application failure. So this raises the ultimate question &#8211; <\/span><\/i><b><i>Is regular testing sufficient?<br \/>\n<\/i><\/b><i><span style=\"font-weight: 400;\">What if your system was rebooted by mistake? Or your access management was compromised?<br \/>\n<\/span><\/i><i><span style=\"font-weight: 400;\">These kinds of problems cannot be calculated and solved in regular tests.\u201d<\/span><\/i><\/p>\n<p style=\"text-align: right;\"><i><span style=\"font-weight: 400;\">&#8211; Suratip Banerjee, Solutions Architect at Principal Global Services, at a webinar with Whizlabs on Chaos Engineering and AWS Fault Injection Simulator.<\/span><\/i><\/p>\n<p><span style=\"font-weight: 400;\">These failures cause costly outages for companies. The outages hurt customers trying to shop, transact business, and get work done. Even brief outages can impact a company&#8217;s bottom line, so the cost of downtime is becoming a KPI for many engineering teams.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In 2017, 98% of the organizations said that a single hour of downtime would cost their business almost a million dollars. <\/span><span style=\"font-weight: 400;\">That is a huge risk.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">So companies need a solution to this challenge and waiting for the next outage is not an option to meet the challenges head-on.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Hence, you need <strong><em>Chaos Engineering<\/em><\/strong>.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">On 12 September 2021, Whizlabs hosted a webinar on Chaos Engineering and AWS FIS.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Suratip Banerjee, who was the featured speaker, explained in detail all the aspects of Chaos Engineering, AWS FIS, and their benefits.<\/span><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_76 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #ea7e02;color:#ea7e02\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #ea7e02;color:#ea7e02\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><ul class='ez-toc-list-level-2' ><li class='ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#What_Is_Chaos_Engineering\" >What Is Chaos Engineering?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Benefits_of_Chaos_Engineering\" >Benefits of Chaos Engineering<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-1'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Principles_of_Chaos_Engineering\" >Principles of Chaos Engineering<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Steady_State\" >Steady State<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Hypothesis\" >Hypothesis<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Design_The_Experiment\" >Design The Experiment\u00a0\u00a0<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Verify_and_Learn\" >Verify and Learn<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Fix\" >Fix<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#AWS_FIS\" >AWS FIS<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Components_of_AWS_FIS\" >Components of AWS FIS\u00a0<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Action\" >Action<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Target\" >Target<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Experiment_Template\" >Experiment Template<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.whizlabs.com\/blog\/chaos-engineering-and-aws-fault-injection-simulator-supratip-banerjee\/#Experiment\" >Experiment<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"What_Is_Chaos_Engineering\"><\/span><b>What Is Chaos Engineering?<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Chaos engineering is the process of stressing an application in a test or production environment.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It is conducted by creating disruptive events such as server outage, API throttling, or latency. Then the system\u2019s response is observed. Finally, we implement our improvements, and we do that to prove or disprove the assumptions of our system capability to handle these disruptive elements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">These experiments have the added benefit of helping teams build muscle memory in resolving outages, akin to a fire drill. By breaking things on purpose we surface unknown issues that could impact our systems and customers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead of letting these events happen at 3 am or on weekends, we create them in a controlled environment during working hours when all our teams and engineers are ready to tackle the issue.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Benefits_of_Chaos_Engineering\"><\/span><b>Benefits of Chaos Engineering<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Customer:<\/b><span style=\"font-weight: 400;\"> The increased availability and durability of service means no outages disrupt the customer&#8217;s day-to-day lives.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Business:<\/b><span style=\"font-weight: 400;\"> Chaos Engineering can help prevent losses in revenue and maintenance costs, create happier and more engaged engineers, improve on-call training for engineering teams, and improve the SEV (incident) Management Program for the entire company.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Technical:<\/b><span style=\"font-weight: 400;\"> The insights from chaos experiments can mean a reduction in incidents, reduction in on-call burden, increased understanding of system failure modes, improved system design, faster mean time to detection for SEVs, and reduction in repeated SEVs. Exposes monitoring observability and alarm blind spots. Improves recovery time, operation scales, and more.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">After the use of chaos engineering, 47% of businesses reported increased availability, and 45% reported reduced Mean To Time Ratio(MTTR)!<\/span><\/p>\n<h1><span class=\"ez-toc-section\" id=\"Principles_of_Chaos_Engineering\"><\/span><b>Principles of Chaos Engineering<\/b><span class=\"ez-toc-section-end\"><\/span><\/h1>\n<p><span style=\"font-weight: 400;\">The key to performing Chaos Engineering is to understand its principles and then follow a well-planned process based on these principles.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Steady_State\"><\/span><span style=\"font-weight: 400;\">Steady State<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It refers to the performance of the system in a normal state.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Initially, you have to search for measurable results that link operating metrics and customer experience. For the output to be in the steady state, the behavior of the system observed should be predictable, but vary greatly if failure is introduced.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Hypothesis\"><\/span><span style=\"font-weight: 400;\">Hypothesis<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">\u201cWhat if this Load Balancer breaks?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cWhat if this database stops?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">\u201cWhat if latency increases by 300ms?\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Sit with your team and after brainstorming, pick out one scenario that is most likely to happen or should be prioritized. This hypothesis must not be too complicated. It should be placed upon the part of the system that you believe to be resilient.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Design_The_Experiment\"><\/span><span style=\"font-weight: 400;\">Design The Experiment\u00a0\u00a0<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The best ways to begin with the experiment phase are:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Start small<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make it closest to the production<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Minimize the blast radius\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Have an emergency STOP!\u00a0<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Verify_and_Learn\"><\/span><span style=\"font-weight: 400;\">Verify and Learn<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">At this stage, you analyze the result of the experiment. You can evaluate your report with respect to these pointers:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time to detect<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time for notification and escalation\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time to public notification\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time for graceful degradation to kick in\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time for self-healing to happen<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time for recovery &#8211; Partial and full<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time to all clear and stable<\/span><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Fix\"><\/span><span style=\"font-weight: 400;\">Fix<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It is the concluding stage of your engineering experiment. Here you fix and learn from the failures that the system faced during the experiment.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"AWS_FIS\"><\/span><b>AWS FIS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Fault injection experiments are the fundamental part of chaos engineering.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A Fault Injection Simulator(FIS) simplifies the process by creating real-world conditions that are required to uncover the possible failures in the application.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The AWS FIS is a completely managed service that helps you to improve an application&#8217;s performance, observability, and resilience by conducting failure injection tests on AWS.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Each AWS FIS experiment targets a specific set of AWS resources and performs a set of actions on them.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Components_of_AWS_FIS\"><\/span><b>Components of AWS FIS<\/b><span style=\"font-weight: 400;\">\u00a0<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Action\"><\/span><span style=\"font-weight: 400;\">Action<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Actions are the fault injection actions executed during an experiment.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Actions include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fault type\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duration\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Targeted resources\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timing relative to any other actions\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fault specific parameters such as rollback behavior, or the portion of the request to throttle<\/span><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Target\"><\/span><span style=\"font-weight: 400;\">Target<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">A target defines one or more resources on which an Action is to be carried out. You define targets while creating an experiment template.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When you define a target, you particularize the following:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The resource type<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource IDs, tags, and filters<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Selection mode (e.g. ALL, RANDOM)<\/span><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Experiment_Template\"><\/span><span style=\"font-weight: 400;\">Experiment Template<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">An experiment template is a blueprint of your experiment. It contains the Action target and STOP conditions for that experiment. So, after you create an experiment template you can use it to run an experiment.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Experiment templates include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Actions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Targets<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stop condition alarms<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM role<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Description\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tags<\/span><\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Experiment\"><\/span><span style=\"font-weight: 400;\">Experiment<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Experiments are snapshots of the experiment template when it was first launched by a couple of additions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Experiments include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Snapshot of the experiment\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Creation and start time\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Status\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Execution ID\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Experiment template ID\u00a0<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IAM role ARN<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">To see the actual working of AWS FIS along with a detailed explanation of Chaos Engineering and its process, you can watch our intensive webinar. Here, our featured speaker and expert, Suratip Banerjee, has thoroughly covered Chaos Engineering, its process, challenges, relevant industry scenario, and AWS FIS procedure.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To learn about the above topics in detail and more, you can watch our recorded webinar here:<\/span><\/p>\n<div class=\"ast-oembed-container \" style=\"height: 100%;\"><iframe title=\"Whizlabs Webinar | Chaos Engineering and AWS FIS | Supratip Banerjee\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube.com\/embed\/7-Hy2Q4-aCg?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/div>\n","protected":false},"excerpt":{"rendered":"<p>In May 2017, at London&#8217;s two of the busiest airports, British Airways grounded all of its flights. That day 75,000 passengers of British airways were impacted because of an IT failure. Airline investigations reported that it was the case of poor resilience and lack of proper disaster recovery after a power surge at a UK-based data center. The CEO of British Airways recently explained how that one IT failure cost the company 80 Million Pounds! Even in your companies, failures are bound to happen. \u201cMany unknown factors can not be anticipated in the regular testing scenario for application failure. So [&hellip;]<\/p>\n","protected":false},"author":169,"featured_media":79714,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[29],"tags":[],"class_list":["post-79710","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-webinar"],"uagb_featured_image_src":{"full":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee-150x150.png",150,150,true],"medium":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee-300x171.png",300,171,true],"medium_large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"1536x1536":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"2048x2048":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"profile_24":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",24,14,false],"profile_48":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",48,27,false],"profile_96":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",96,55,false],"profile_150":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",150,86,false],"profile_300":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",300,171,false],"tptn_thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee-250x250.png",250,250,true],"web-stories-poster-portrait":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",560,320,false],"web-stories-publisher-logo":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",96,55,false],"web-stories-thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/09\/Chaos-Engineering-and-AWS-Fault-Injection-Simulator-\u2013-Supratip-Banerjee.png",150,86,false]},"uagb_author_info":{"display_name":"Girdharee Saran","author_link":"https:\/\/www.whizlabs.com\/blog\/author\/girdharee\/"},"uagb_comment_info":0,"uagb_excerpt":"In May 2017, at London&#8217;s two of the busiest airports, British Airways grounded all of its flights. That day 75,000 passengers of British airways were impacted because of an IT failure. Airline investigations reported that it was the case of poor resilience and lack of proper disaster recovery after a power surge at a UK-based&hellip;","_links":{"self":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79710","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/users\/169"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/comments?post=79710"}],"version-history":[{"count":4,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79710\/revisions"}],"predecessor-version":[{"id":79715,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79710\/revisions\/79715"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media\/79714"}],"wp:attachment":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media?parent=79710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/categories?post=79710"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/tags?post=79710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}