Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/young-ook/terraform-aws-fis

Terraform Module: AWS FIS
https://github.com/young-ook/terraform-aws-fis

aws chaos-engineering resilience terraform

Last synced: about 5 hours ago
JSON representation

Terraform Module: AWS FIS

Awesome Lists containing this project

README 

        
# AWS Resilience Hub - Fault Injection Service (FIS)

[AWS Resilience Hub](https://aws.amazon.com/resilience-hub/) is a service that provides actionable recommendations to improve resilience of applications. And [AWS Fault Injection Service](https://aws.amazon.com/fis/) is a fully managed service for running fault injection experiments on AWS that makes it easier to improve an application’s performance, observability, and resiliency. Fault injection experiments are used in chaos engineering, which is the practice of stressing an application in testing or production environments by creating disruptive events, such as sudden increase in CPU or memory consumption, observing how the system responds, and implementing improvements. For more details, please visit [what is](https://docs.aws.amazon.com/fis/latest/userguide/what-is.html) page.



![aws-fis-overview](images/aws-fis-overview.png)

![aws-fis-workflow](images/aws-fis-workflow.png)



## Reliability

In statistics and psychometrics, reliability is the overall consistency of a measure. A measure is said to have a high reliability if it produces similar results under consistent conditions.



## Resiliency

Resiliency is the ability for a system to recover from a failure induced by load, attacks, and failures. A resilient workload has the capability to recover when stressed by more requests for service, attacks either accidental through a bug, or deliberate through intention, and failure of any component in the workload's components.



## Chaos Engineering

### Why Chaos Engineering

There are many reasons to do chaos engineering. We see teams transitioning in this way to reduce incidents, lower downtime costs, train their teams, and prepare for critical moments. Practicing chaos engineering allows you to detect problems before they become accidents and before customers are affected. And chaos engineering is useful for reducing downtime costs because it allows teams to have a resilient architecture. While the number of companies operating at Internet scale increases and high-traffic events such as sales or launches increase, the cost of downtime will become more expensive. Additionally, this continuous practice of chaos engineering gives teams more confidence every day as they build their own applications and systems. It takes less time to fire-fighting and more time to create and create value.



### How to do Chaos Engineering

To implement Chaos Engineering, one should follow the scientific method to implement experiments:

1. Observe your system

1. Baseline your metrics

1. Define Steady State

1. Form a Hypothesis with Abort Conditions (Blast Radius)

1. Run Experiment

1. Analyze Results

1. Expand Scope and Re-Test

1. Share Results



![chaos-engineering-flywheel](images/chaos-engineering-flywheel.png)



## Getting started

### AWS CLI

:warning: **This module requires the aws cli version 2.5.8 or higher**



Follow the official guide to install and configure profiles.

- [AWS CLI Installation](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html)

- [AWS CLI Configuration](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html)



After the installation is complete, you can check the aws cli version:

```

aws --version

aws-cli/2.5.8 Python/3.9.11 Darwin/21.4.0 exe/x86_64 prompt/off

```



### Terraform

Terraform is an open-source infrastructure as code software tool that enables you to safely and predictably create, change, and improve infrastructure.



#### Install

This is the official guide for terraform binary installation. Please visit this [Install Terraform](https://learn.hashicorp.com/tutorials/terraform/install-cli) website and follow the instructions.



Or, you can manually get a specific version of terraform binary from the websiate. Move to the [Downloads](https://www.terraform.io/downloads.html) page and look for the appropriate package for your system. Download the selected zip archive package. Unzip and install terraform by navigating to a directory included in your system's `PATH`.



Or, you can use [tfenv](https://github.com/tfutils/tfenv) utility. It is very useful and easy solution to install and switch the multiple versions of terraform-cli.



First, install tfenv using brew.

```

brew install tfenv

```

Then, you can use tfenv in your workspace like below.

```

tfenv install 

tfenv use 

```

Also this tool is helpful to upgrade terraform v0.12. It is a major release focused on configuration language improvements and thus includes some changes that you'll need to consider when upgrading. But the version 0.11 and 0.12 are very different. So if some codes are written in older version and others are in 0.12 it would be great for us to have nice tool to support quick switching of version.

```

tfenv list

tfenv install latest

tfenv use 

```



# Experiments

- [AWS FIS Blueprint](https://github.com/Young-ook/terraform-aws-fis/tree/main/examples/blueprint)

- [Application Modernization with Spinnaker](https://github.com/Young-ook/terraform-aws-spinnaker/tree/main/examples/aws-modernization-with-spinnaker)

- [Chaos Engineering with AWS FIS Hands-on Lab](https://catalog.us-east-1.prod.workshops.aws/workshops/7379e94f-6981-4dd8-bb46-8ec4aff3a825/ko-KR)



# Known Issues

## Unknown parameter

You might see error like belows if your aws cli does not support log configuration parameter of aws fis command. Upgrade your aws cli when you see that. This module requires aws cli version 2.5.8 or higher.

```

module.awsfis.null_resource.awsfis-init (local-exec): Parameter validation failed:

module.awsfis.null_resource.awsfis-init (local-exec): Unknown parameter in input: "logConfiguration", must be one of: clientToken, description, stopConditions, targets, actions, roleArn, tags

```



# Additional Resources

## Chaos Engineering

- [Chaos Engineering (카오스 엔지니어링)](https://youngookkim.tistory.com/48)

- [Yahoo Japan Chaos Engineering Practices in Production Environments](https://speakerdeck.com/techverse_2022/yahoo-japan-practices-chaos-engineering-in-production-environments)



## Disaster Recovery (DR)

- [Disaster Recovery of Workloads on AWS](https://youtu.be/cJZw5mrxryA)

- [RPO and RTO: Understanding the Differences](https://www.enterprisestorageforum.com/management/rpo-and-rto-understanding-the-differences/)



## Distributed System

- [Exponential Backoff And Jitter](https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/)



## Google Site Reliability Engineering (SRE)

- [SRE Books](https://sre.google/books/)



## Netflix

- [Project Nimble: Region Evacuation Reimagined](https://netflixtechblog.com/project-nimble-region-evacuation-reimagined-d0d0568254d4)



## Well-Architected

- [Azure Well-Architected](https://learn.microsoft.com/en-us/azure/well-architected/)

- [AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/)

- [AWS Well-Architected Lab](https://wellarchitectedlabs.com/)

- [AWS Well-Architected Framework - Reliability](https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/welcome.html)

- [AWS Well-Architected Framework - Operational Excellence](https://docs.aws.amazon.com/wellarchitected/latest/operational-excellence-pillar/welcome.html)



## Builder's Library

- [Ensuring rollback safety during deployments](https://aws.amazon.com/builders-library/ensuring-rollback-safety-during-deployments/)

- [Instrumenting distributed systems for operational visibility](https://aws.amazon.com/builders-library/instrumenting-distributed-systems-for-operational-visibility/)

- [Reliability, constant work, and a good cup of coffee](https://aws.amazon.com/builders-library/reliability-and-constant-work)

- [Building dashboards for operational visibility](https://aws.amazon.com/builders-library/building-dashboards-for-operational-visibility/)

- [Making retries safe with idempotent APIs](https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/)

- [Automating safe, hands-off deployments](https://aws.amazon.com/builders-library/automating-safe-hands-off-deployments/)



## Whitepapers

- [Disaster Recovery of Workloads on AWS: Recovery in the Cloud](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-workloads-on-aws.html)

- [Disaster Recovery of On-Premises Applications to AWS](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-of-on-premises-applications-to-aws/abstract-and-introduction.html)

- [Operational Readiness Reviews (ORR)](https://docs.aws.amazon.com/wellarchitected/latest/operational-readiness-reviews/wa-operational-readiness-reviews.html)