Add AWS cli to codespaces

[evanharmon]

May require creating a custom image for codespaces.

Tasks:

• [x] add aws cli
• [x] confirm aws cli available
• [x] create AWS IAM policy to manage own security credentials and enforce MFA on long term creds
• [x] attach manage security creds policy to ADMIN group
• [x] confirm MFA required when aws cli commands run in codespace
• [x] add AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_IAM_USER, AWS_ACCOUNT_ID to codespace secrets in github profile settings NOT at repo level
• [x] create dotfile repo
• [x] add aws-creds bash function to dotfiles repo (controls get-session-token call with mfa)
• [x] attach dotfiles to codespaces in github profile
• [x] confirm access key id and secret key set
• [x] confirm aws-creds function file available source ~/.aws-creds.bash
• [x] test aws-creds 111111 replacing with a valid MFA token
• [x] update headspace notes on aws iam policies aws iam policies

[evanharmon]

Docs:

• Personalize Codespaces
• Managing Encrypted Secrets
• Codespaces prebuilds
• IAM Policy Requiring MFA on long term cred keys
• AWS config docs for setting mfa_serial

[evanharmon]

Caveats:

codespace had to be deleted and re-created in order to pickup dotfile repo hook up

aws-creds bash function overwrites AWS environment variables. This prevents the script from being re-usable after the session token expires. Current instructions are to exit terminal in codespaces and launch a new terminal. This will re-populate original AWS environment variables from github profile level codespaces secrets

.aws-creds.bash has to be sourced every time. Putting off more dot file shell setup