Rename doc files

Author: Peter Benjamin

docs/01-RESTACKER_INTRO.md

@@ -0,0 +1,18 @@
+# INTRODUCTION
+
+The Control-Plane pattern/architecture is designed to mitigate and limit risk/exposure if an account were to be compromised.  
+In DevSecOps, we call this **Blast Radius**.
+
+## CONTROL PLANE
+In a typical Control-Plane architecture, an account is designated as the Control Plane.  
+It does not have any instances (e.g. EC2, RDS ...etc).  
+The main purpose of this account is to maintain users and roles.
+
+## TARGET PLANE
+The target plane, or account, will host the instances, databases, and any other AWS services needed.  
+The roles in this account trusts roles from the Control Plane/Account
+
+## WORKFLOW
+In a Control-Plane architecture, the workflow for performing operations on the Target Account will look like this:
+ - Authenticate against the Control Account to obtain an AWS STS token.
+ - Pass that STS token to the next Target Account to assume a specific role (e.g. Read-Only, Deploy-Admin, Incident-Response ...etc).

docs/02-RESTACKER_YML.md

@@ -0,0 +1,71 @@
+# RESTACKER.YML
+This is the configuration file for Restacker CLI.  
+See the sample [here](../source/restacker-sample.yml).
+
+## STRUCTURE
+In order for Restacker to work as expected, the following key:value pairs are required:
+- `:default:`: specifies the default location/plane for all Restacker operations. This is intended to save you from having to specify the required `-l <location>` everytime.
+  - `:label:`: the name of the default location.
+- `:ctrl: &ctrl_default`: default configuration for the Control Account
+  - `:label:`: name of the account
+  - `:role-name:`
+  - `:role-prefix:`
+  - `:bucket:`: S3 Bucket configuration to read/consume files from.
+    - `:name:`: Bucket name
+    - `:prefix:`: **optional** bucket prefix/path
+    - `:ami_key:`: **optional** name of object on S3 that contains list of approved AMIs
+- `:Account_Name:`: name of target account
+  - `:region:`: default region to deploy instances in (e.g. `us-west-2`)
+  - `:ctrl:`: control account for this account
+    - `<<: *ctrl_default`: if the control account is the default account specified in `&ctrl_default`, then just insert default configurations here
+  - `:target:`: the target account configuration
+    - `:label:`: name of target account
+    - `:account_number:`: target account number
+    - `:role_name:`: target role name
+    - `:role_prefix:`: target role prefix
+
+## Example Restacker Configuration:
+```
+:default:
+  :label: myapp1
+
+:ctrl: &ctrl_default
+  :label: ctrlAcct
+  :account_number: '123456789012'
+  :role_name: ctrl-ctrl-DeployAdmin
+  :role_prefix: "/dso/ctrl/ctrl/"
+  :bucket:
+    :name: kaos-installers
+    :prefix: cloudformation
+    :ami_key: latest_amis
+
+:ctrlAcct:
+  :region: us-west-2
+  :ctrl:
+    <<: *ctrl_default
+  :target:
+    <<: *ctrl_default
+
+:myapp1:
+  :region: us-west-2
+  :ctrl:
+    <<: *ctrl_default
+    :role_name: ctrl-myapp1-DeployAdmin
+  :target:
+    :label: myapp1
+    :account_number: '098765432123'
+    :role_name: myapp1-dso-DeployAdmin
+    :role_prefix: "/dso/human/"
+
+:myapp2:
+  :region: us-west-2
+  :ctrl:
+    <<: *ctrl_default
+    :role_name: ctrl-myapp2-DeployAdmin
+  :target:
+    :label: myapp2
+    :account_number: '123098456765'
+    :role_name: myapp2-dso-DeployAdmin
+    :role_prefix: "/dso/human/"
+
+```

docs/03-PARAMETERS_YML.md

@@ -0,0 +1,6 @@
+# PARAMETERS.YML
+Configurations to be passed to the CloudFormation template.
+
+<!-- Explain each Parameter here -->
+
+**NOTE:** Any Environment variable that you'd like to persist past boot, place them here, **not** in `userdata.sh`

docs/04-USERDATA_SH.md

@@ -0,0 +1,2 @@
+# USERDATA.SH
+Configuration needed only during instance-creation stage