|
@@ -20,32 +20,28 @@
|
|
|
- `vim ~/.vault-token`
|
|
|
- The DNS in the Terraform Vault provider will be used. To test connectivity be sure to run this command: `export VAULT_ADDR=https://internal-vault-alb-test-778772793.us-gov-east-1.elb.amazonaws.com`. Replace the ALB address with the current ALB DNS address. This is due to Golang DNS not updating when connected to XDR over VPN. Vault binary is written in Go.
|
|
|
- Why not use the accenturefederal address? This is due to golang DNS issues.
|
|
|
- - Download the vault binary ( might not be needed? Is the binary in the TF provider? )
|
|
|
+ - Download the Vault binary ( might not be needed? Is the binary in the TF provider? )
|
|
|
- `terragrunt apply`
|
|
|
- Might need this command as well. See main.tf in module for more information.
|
|
|
- `vault write auth/aws/config/client sts_endpoint=https://sts.us-gov-east-1.amazonaws.com sts_region=us-gov-east-1`
|
|
|
- - The Terraform Vault provider will look at ~/.vault-token for the token and the bash variables for the address to connect to.
|
|
|
+ - The Terraform Vault provider will look at ~/.vault-token for the token and the bash variables for the address to connect to. You can also add it to the command line (see below).
|
|
|
- Revoke the root token
|
|
|
- `vault token revoke <root-token>`
|
|
|
- Distribute Vault shareds to the appriopriate individuals.
|
|
|
- Export/Import secrets
|
|
|
- https://github.com/adamdecaf/vault-backend-migrator
|
|
|
-
|
|
|
+- This module is dependent on AWS Secrets Manager for creds to authenticate to OKTA via OIDC and OKTA auth.
|
|
|
For additional Vault documentation see these locations:
|
|
|
|
|
|
https://github.mdr.defpoint.com/mdr-engineering/infrastructure-notes/blob/master/Vault%20Notes.md
|
|
|
|
|
|
https://github.mdr.defpoint.com/mdr-engineering/msoc-infrastructure/blob/develop/salt/fileroots/vault/README.md
|
|
|
|
|
|
-## To apply without putting your junk in the terragrunt.hcl
|
|
|
-
|
|
|
-THIS SECTION INCOMPLETE
|
|
|
+## To apply Terraform Changes without putting credentials in the terragrunt.hcl
|
|
|
|
|
|
-1. `VAULT_TOKEN`: Login to vault, and click your name dropdown, then copy secret. You'll need it more than once.
|
|
|
-1. `TF_VAR_okta_api_token`: Find this in the prod vault (even for test)
|
|
|
-1. `TF_VAR_okta_oidc_client_secret`: Find this in the prod vault (even for test)
|
|
|
+- `VAULT_TOKEN`: Login to vault, and click your name dropdown, then copy token. You'll need it more than once.
|
|
|
|
|
|
Then apply:
|
|
|
```
|
|
|
-VAULT_TOKEN=<fromvault> TF_VAR_okta_api_token=YOURTOKENHERE TF_VAR_okta_oidc_client_secret=YOURSECRETHERE terragrunt apply
|
|
|
+VAULT_TOKEN=<fromvault> terragrunt apply
|
|
|
```
|