TL;DR: Chaos Monkey was developed in 2010 at Netflix and released into wild in 2012 is part of the Simian Army, wildly popular among devoted followers. Built on principles of chaos engineering, the army increases resiliency to failure by injecting constant failure to the system.
Chaos Monkey was developed specifically for AWS where it will randomly ...
Some additions to your own answer to this question ...
The article about "How chaos boosts performance" describes a few more of these monkeys, i.e.:
10-18 Monkey: finds configuration and run time problems in instances that serve customers in multiple regions.
Chaos Kong: simulates an outage of an Amazon region.
Remark: The same ...
Have a look for DevOps Engineer roles and check out the list of technologies that they are seeking. Typically you'll need automation scripting skills (like Bash, Python or PowerShell), configuration management skills (like Chef, Puppet or Ansible) and some fundamental experience maintaining and configuring a Build/Release pipeline. For this, look to get ...
Thankfully, since Site Reliability Engineering developed internally at Google and only recently has started to make its way into the broader community, it is fairly well-defined. What isn't, though, is web operations (or "systems administration" - as an example of the lack of clarity, you use both in your question). It's difficult to discuss the ...
One Server to rule them all, One Server to find them,
One Server to bring them all and in the outage bind them
You, Sauron, forged this One Server, in the Darkness of Mount Doom your Datacenter in a desire to rule All applications.
Hopefully the Fellowship of Devops did unite to tell you:
After a long fight, Frodo the Chaos Monkey has been able to melt ...
Make a list of DevOps tools that seem to be popular, download, follow the manual, and just do it.
This will give you a good running start with the tools closer to the "Ops" side, and - if you manage to also pick up why and what for these tools are used - will make you a worthy member of most teams. You can pick ...
Create an IAM role in prod with all the permissions you'd like the devs to have.
When you want devs to have prod access, add the sts:AssumeRole permission to their IAM group.
When it's time to revoke access, remove the sts:AssumeRole permission.
More details in my blog article here.
Keep learning other requirements for devops engineering. such as:
Operating System concepts (Process management, threads and concurrency, POSIX basics, I/O management, file systems, memory storage, ...)
as a devops engineer you need to know everything about the operating systems and how they work. to know everything about the operating systems, first you ...