add posts to resilience wave

[setheliot]

Content Pull Request Checklist

Please check to make sure your content submission meets the following requirements by adding an x between the brackets:

• [x] The title of this pull request reflects the title of my content.
• [x] I have reviewed the Content Review Checklist.
• [x] This pull request contains one piece of content (post or page).

By submitting this pull request, I confirm I own this content, have permission to use each image included in this content, and that it will be released under the CC BY-SA 4.0 SA License. Notwithstanding the above, if you provide source code text within your content piece, you are providing such source code under the MIT-0 license.

[buildon-publication-bot[bot]]

Congratulations on submitting your Content Draft! Below is a rough outline of the process:

Content Draft (you're here) -> Review by reviewer -> You implement changes, if requested -> Final Review by reviewer

[buildon-publication-bot[bot]]

Automated Validation Results

Preview results

Your pull request contains some content that can be previewed:

• 👁️‍🗨️ /concepts/building-an-observability-strategy-for-resilience
• 👁️‍🗨️ /concepts/concepts/how-to-design-and-implement-an-effective-incident-response-strategy
• 👁️‍🗨️ /concepts/should-know-resilience
• 👁️‍🗨️ /posts/amazon-search-chaos-engineering-journey
• 👁️‍🗨️ /posts/build-and-manage-a-resilient-service-using-aws-sdks
• 👁️‍🗨️ /posts/building-a-multi-region-serverless-iot-system
• 👁️‍🗨️ /posts/chaos-engineering-2-minutes
• 👁️‍🗨️ /posts/chaos-engineering-pipeline
• 👁️‍🗨️ /posts/cost-conscious-disaster-recovery
• 👁️‍🗨️ /posts/fix-gray-failures-fast-using-automation-and-route53-arc-zonal-shift
• 👁️‍🗨️ /posts/how-amazon-does-devops-in-real-life
• 👁️‍🗨️ /posts/how-search-uses-chaos-engineering
• 👁️‍🗨️ /posts/levelling-up-your-releases-a-deep-dive-into-blue-green-deployments
• 👁️‍🗨️ /posts/protect-your-data/01-protect-your-data-in-Amazon-RDS-against-disaster
• 👁️‍🗨️ /posts/scaling-your-application-data-patterns
• 👁️‍🗨️ /posts/six-ways-to-know-your-apps-are-resilient
• 👁️‍🗨️ /posts/what-happened-to-my-car
• 👁️‍🗨️ /posts/when-should-i-failover
• 👁️‍🗨️ /posts/where-do-i-put-my-backups-in-the-cloud
• 👁️‍🗨️ /posts/zero-dataloss-dr-using-rds
• 👁️‍🗨️ /tutorials/building-multi-region-disaster-recovery-for-amazon-appstream2-0
• 👁️‍🗨️ /tutorials/ddb-globaltables-lag

[buildon-publication-bot[bot]]

Congratulations! 🎉

Your posts have now been published. In a few seconds they will be accessible at:

• 🗒 /concepts/building-an-observability-strategy-for-resilience
  • 🗒 /concepts/concepts/how-to-design-and-implement-an-effective-incident-response-strategy
  • 🗒 /concepts/should-know-resilience
  • 🗒 /posts/amazon-search-chaos-engineering-journey
  • 🗒 /posts/build-and-manage-a-resilient-service-using-aws-sdks
  • 🗒 /posts/building-a-multi-region-serverless-iot-system
  • 🗒 /posts/chaos-engineering-2-minutes
  • 🗒 /posts/chaos-engineering-pipeline
  • 🗒 /posts/cost-conscious-disaster-recovery
  • 🗒 /posts/fix-gray-failures-fast-using-automation-and-route53-arc-zonal-shift
  • 🗒 /posts/how-amazon-does-devops-in-real-life
  • 🗒 /posts/how-search-uses-chaos-engineering
  • 🗒 /posts/levelling-up-your-releases-a-deep-dive-into-blue-green-deployments
  • 🗒 /posts/protect-your-data/01-protect-your-data-in-Amazon-RDS-against-disaster
  • 🗒 /posts/scaling-your-application-data-patterns
  • 🗒 /posts/six-ways-to-know-your-apps-are-resilient
  • 🗒 /posts/what-happened-to-my-car
  • 🗒 /posts/when-should-i-failover
  • 🗒 /posts/where-do-i-put-my-backups-in-the-cloud
  • 🗒 /posts/zero-dataloss-dr-using-rds
  • 🗒 /tutorials/building-multi-region-disaster-recovery-for-amazon-appstream2-0
  • 🗒 /tutorials/ddb-globaltables-lag