{
"Version": "2012-10-17",
"Statement": {
"Effect": "Allow",
"Action": "sts:AssumeRole",
"Resource": "arn:aws:iam::123456789012:role/*"
}
Compliance
For compliance: ("-" = removed; "+" = added):
-
- DOD CSM Levels 1-5 (Superceded)
-
- [DODSRG Levels 2 and 4]
[Greg Knieriemen's Blog The REAL State of Cloud] (https://community.hds.com/people/gknieriemen/blog/2016/06/07/the-real-state-of-cloud)
It’s a false argument that presumes there is only one way to “cloud.” It doesn’t consider how businesses value, use and consume cloud resources.
Method:
sudo yum update
sudo yum install curl-devel expat-devel gettext-devel openssl-devel perl-devel zlib-devel
sudo yum install asciidoc xmlto docbook2X
sudo yum install gcc autoconf
sudo ln -s /usr/bin/db2x_docbook2texi /usr/bin/docbook2x-texi
wget https://github.com/git/git/archive/v2.8.4.zip
Current as of: August, 2016
Passing SA Pro:
- get ACloudGuru 5 certification bundle. (Disclaimer: I have no financial interest in ACloudGuru.)
- work through Associate courses. Take and pass all Associate exams.
- work through SA Pro course
- take the SA Pro Sample exam. Note that answers are provided for version from the Japan site. Download the PDF. The answers are at the end of each question.
- take SA Pro Practice exam. If you get 75% or higher, just take the SA Pro exam.
Resources for AWS questions, in opinionated order of usefulness:
- AWS docs
- The Open Guide to Amazon Web Services
- Google, but you have to have the right search terms because of the number of results that come up
- StackOverflow, can be good with fuzzier terms, but you may go down a rabbithole of links
- AWS forums, but target the specific forum and beware of old answers
- Reddit AWS sub is ok, but it helps to ask a "good" question" with enough context
- Reddit DevOps can be ok, but is filled with opinion presented as facts
- Reddit sysadmin can be ok, but be prepared for a lot of Reddit culture and more random opinions
- og-aws/answers Slack channel
Episode: 10 Apr 2019
http://www.thecloudcast.net/2019/04/network-reliability-engineering-nre-nre.html
Interesting show and a great idea to reduce the barriers to entry for networking folks wanting to learn automation skills, but the idea of focusing narrowly on network reliability engineering as a take off from site reliability engineering really seems to perpetuate the network silo. The concept is “Site RE,” and expressly not Dev RE, Ops RE, Net RE, Security RE… More on this in the later discussion of frustration about getting an API key.
Around 16:00 there’s discussion about the inadvisability of putting a new release of networking system software on a prod device because it’s expected to be buggy. Paraphrasing, Automation is about reliability, not about going faster. This idea isn’t really explored. It’s not clear why the goal can’t be both better reliability and iterating faster or even if one reinforces the other.
Around 17:15,
A few comments on the Heavy Networking 442: The Source Of Truth Shall Set You Free (To Automate) podcast.
There's never enough time to discuss every detail that might be worth exploring, of course.
In the discussion of the three sources of truth, I wasn't clear:
- if the data in the Netbox data repository was versioned so that a bad config could be reverted
- what's the repository for the remaining cloud services