names and menu

Author: zzeppozz

sphinx/aws/authentication.rst renamed to sphinx/aws/authentication.md

@@ -1,62 +1,17 @@
-Authentication
-###########################
+# Authentication
 
-
-Notes to be Organized and Completed
----------------------------------------
-
-Authentication
-.........................
-
-* Give EC2 instance a role, access to S3, etc, NOT an AWS key, pass instance profile
-  (contains role, role contains privileges. Role must have permission to read secret)
-* Role, create
-
-  * What kind of thing, service, i.e. EC2, lambda, SAML assertion?
-  * What permissions?  Can use or edit AWS managed permissions policy, What can it do,
-    JSON defines,
-  * Trust relationship, AssumeRole
-  * User can get roles through Group or permission/policy document directly
-  * Access Advisor - see what has been used or not, and pare down the permissions
-
-* Security group (ports, inbound, outbound)
-
-  * Can include all traffic from another SG, need to do that for both SGs
-
-* Parameter store (cheaper) stores less secret info, define config for a project,
-  need read parameter policy on the role using it, no additional charge for standard
-  parameters, up to 10k, less than 4k,
-
-  * Secure parameters , will encrypt them, can use KMS key, need to add to your policy doc
-  * Can make public parameters
-
-* Secrets - 0.40/mo per secret 0.05/10,000 accesses
-* Temporary credentials with IAM Roles?  Vs Access keys for long-term access?
-* Identities = AWS resources (EC2 instance, lambda functions)
-* Secrets for roles/identities for initiating contact/processes
-
-  * https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html
-  * APIkey/secret, user/password, private key, token, certificate …
-  * Create a role to manage the secrets
-  * Create a role to retrieve secrets - grant the role permission to access only select
-    secrets, give that role to the code/process of interest
-
-Allow S3 access from EC2 instance
--------------------------------------------
+## Allow S3 access from EC2 instance
 
 * Create a role for the instance, with permissions for whatever it will use (i.e.
   read/write for specific bucket folders,  read secret, Redshift, etc):
   AmazonRedshiftAllCommandsFullAccess, AmazonS3ReadOnlyAccess, SecretsManagerReadWrite
 * Assign that role to the instance
-*
 
 https://repost.aws/knowledge-center/ec2-instance-access-s3-bucket
 
-Troubleshooting
-------------------------
+## Troubleshooting
 
-EC2 slowly or never responds
-...................................
+### EC2 slowly or never responds
 
 "EBS throughput is under-provisioned""
 
@@ -75,17 +30,51 @@ Storage interface, and Network interface.
 
 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resize-limitations.html
 
-EC2 stops responding during docker compose
-.................................................
+### EC2 stops responding during docker compose
 
 => [front-end base-front-end 4/6] RUN npm install
 
+## Questions remaining
 
-
-Questions remaining
----------------------------------------
 * Roles for “workload”
 * Travis: How to assign broad privileges to a process, run it, then identify the minimum
   privileges it needs?
 * Temporary access roles vs static
-* Access Control ???
+* Access Control ???
+
+## Notes to be Organized and Completed
+
+### Authentication
+
+* Give EC2 instance a role, access to S3, etc, NOT an AWS key, pass instance profile
+  (contains role, role contains privileges. Role must have permission to read secret)
+* Role, create
+
+  * What kind of thing, service, i.e. EC2, lambda, SAML assertion?
+  * What permissions?  Can use or edit AWS managed permissions policy, What can it do,
+    JSON defines,
+  * Trust relationship, AssumeRole
+  * User can get roles through Group or permission/policy document directly
+  * Access Advisor - see what has been used or not, and pare down the permissions
+
+* Security group (ports, inbound, outbound)
+
+  * Can include all traffic from another SG, need to do that for both SGs
+
+* Parameter store (cheaper) stores less secret info, define config for a project,
+  need read parameter policy on the role using it, no additional charge for standard
+  parameters, up to 10k, less than 4k,
+
+  * Secure parameters , will encrypt them, can use KMS key, need to add to your policy doc
+  * Can make public parameters
+
+* Secrets - 0.40/mo per secret 0.05/10,000 accesses
+* Temporary credentials with IAM Roles?  Vs Access keys for long-term access?
+* Identities = AWS resources (EC2 instance, lambda functions)
+* Secrets for roles/identities for initiating contact/processes
+
+  * https://docs.aws.amazon.com/secretsmanager/latest/userguide/hardcoded.html
+  * APIkey/secret, user/password, private key, token, certificate …
+  * Create a role to manage the secrets
+  * Create a role to retrieve secrets - grant the role permission to access only select
+    secrets, give that role to the code/process of interest

sphinx/aws/automation_todo.rst renamed to sphinx/aws/automation_todo.md

@@ -1,19 +1,15 @@
-Automation TODO
-#####################
+# Automation TODO
 
-TODO:
-======
+## TODO:
 
 * triggering processes in Redshift, Glue, instantiating EC2 instances, etc
 * Logging of multi-resource workflows to debug problems - may be simple, but any tips
   would be appreciated
 
 
-Notes to be Organized and Completed
----------------------------------------
+## Notes to be Organized and Completed
 
-Automation
-.....................
+### Automation
 
 * Initiate a stored procedure in Redshift and pass it a parameters
 * Billing and Cost management - Cost Explorer
@@ -23,9 +19,7 @@ Automation
 * https://aws.amazon.com/blogs/big-data/building-an-event-driven-application-with-aws-lambda-and-the-amazon-redshift-data-api/
 
 
-
-Logging
-................
+### Logging
 
 * Cloudtrail monitoring - can do your work, then it will tell you what permissions
   you’ve been using, control - log in , log out, authentication, administrative, action,

sphinx/index.rst

@@ -11,9 +11,11 @@ Welcome to Specify Developer documentation!
 .. toctree::
    :maxdepth: 1
    :caption: Launching a Release:
-   
-   processes/release_process
-   processes/release_notes
+
+   processes/github_guidelines_and_processes
+   processes/create_release_notes
+   processes/release_process_for_hosted_users
+   processes/support_guidelines
 
 .. toctree::
    :maxdepth: 1