|
il y a 3 ans | |
---|---|---|
.. | ||
cloud-init | il y a 3 ans | |
README.md | il y a 3 ans | |
amis.tf | il y a 4 ans | |
certificate.tf | il y a 3 ans | |
constants.tf | il y a 3 ans | |
ecr.tf | il y a 3 ans | |
elb.tf | il y a 3 ans | |
employee_ips.tf | il y a 3 ans | |
globals.tf | il y a 3 ans | |
main.tf | il y a 3 ans | |
outputs.tf | il y a 5 ans | |
rds.tf | il y a 3 ans | |
vars.tf | il y a 3 ans | |
waf.tf | il y a 3 ans |
Builds and configures the instances that host the customer portal website. NOTE: the grain ec2_tags:Name and the pillar aws_registry_account are required for portal salt state to complete successfully.
New Portal Server setup steps
HELP! I destroyed then recreated the AWS IAM Portal Role and now Vault will not let me log in!!
In Vault disable the auth method
vault auth disable aws
Then in terraform reapply the config.
VAULT_TOKEN=<fromvault> TF_VAR_okta_api_token=YOURTOKENHERE TF_VAR_okta_oidc_client_secret=YOURSECRETHERE terragrunt-local apply -target=vault_auth_backend.aws -target=vault_aws_auth_backend_client.aws -target=vault_aws_auth_backend_role.portal
Vault apparently caches the AWS response for the portal IAM role.
https://blog.gruntwork.io/a-guide-to-automating-hashicorp-vault-3-authenticating-with-an-iam-user-or-role-a3203a3ee088 It is important to note that although the Vault Role is configured with the IAM principal ARN, what Vault actually checks against is a unique internal ID from AWS. So if you destroy and recreate your IAM Role, Vault will reject the login attempt.