mirror of
https://github.com/nickpoida/og-aws.git
synced 2025-02-15 03:11:57 +00:00
Add section detailling testing with random instance termination (#158)
* Add section detailling testing with random instance termination Includes Netflix "Chaos Monkey" and BBC "chaos-lambda". * #158: Change to unicode quotes and minor grammar changes
This commit is contained in:
parent
dcfe4f7335
commit
e1014b3a04
1 changed files with 1 additions and 0 deletions
|
@ -509,6 +509,7 @@ This guide is about AWS, not DevOps or server configuration management in genera
|
|||
### Tips
|
||||
|
||||
- **NTP and accurate time:** If you are not using Amazon Linux (which comes preconfigured), you should confirm your servers [configure NTP correctly](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-time.html#configure_ntp), to avoid insidious time drift (which can then cause all sorts of issues, from breaking API calls to misleading logs). This should be part of your automatic configuration for every server. If time has already drifted substantially (generally >1000 seconds), remember NTP won’t shift it back, so you may need to remediate manually (for example, [like this](http://askubuntu.com/questions/254826/how-to-force-a-clock-update-using-ntp) on Ubuntu).
|
||||
- **Testing immutable infrastructure:** If you want to be proactive about testing your service’s ability to cope with instance termination or failure, it can be helpful to introduce random instance termination during business hours, which will expose any such issues at a time when engineers are available to identify and fix them. Netflix’s [Simian Army](https://github.com/Netflix/SimianArmy) (specifically, [Chaos Monkey](https://github.com/Netflix/SimianArmy/wiki/Chaos-Monkey)) is a popular tool for this. Alternatively, [chaos-lambda](https://github.com/bbc/chaos-lambda) by the BBC is a lightweight option which runs on AWS [Lambda](#lambda).
|
||||
|
||||
Security and IAM
|
||||
----------------
|
||||
|
|
Loading…
Reference in a new issue