Startseite Erkunden Hilfe
Registrieren Anmelden
AFS
/
xdr-terraform-modules
2
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Struktur: 1a04527d29
Branches Tags
xdr-terraform-m...
/
base
/
customer_portal
Fred Damstra [afs macbook] 494d0f892f Adds WAF rule to protect /admin Paths vor 3 Jahren
..
cloud-init 1ddc24fbfa Final Updates for Portal vor 4 Jahren
README.md e532d854b5 Migrates Portal Lambda to Queue Based vor 3 Jahren
amis.tf 19b6f1bfc5 Adds Portal to GC vor 4 Jahren
certificate.tf fb25b7c56a Adds lifecycle policy to aws_acm_certificates vor 4 Jahren
ecr.tf c4faf2a12d Adds s3_binaries policy to portal instance profile vor 4 Jahren
elb.tf 19364e7516 Adds NATGW for Scanners vor 4 Jahren
main.tf 47be882d36 Adds Support for Instance Tags to Most Instance Modules vor 3 Jahren
outputs.tf 55da096763 Adds init Customer Portal vor 5 Jahren
rds.tf 819389c8c3 Updates Portal RDS version to 12.8 vor 3 Jahren
vars.tf 494d0f892f Adds WAF rule to protect /admin Paths vor 3 Jahren
waf.tf 494d0f892f Adds WAF rule to protect /admin Paths vor 3 Jahren

README.md

xdr customer portal instances

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

  • test.version # are we on the correct salt version?
  • saltutil.sync_all
  • saltutil.refresh_modules # refresh grains
  • saltutil.refresh_pillar # refresh pillars
  • pillar.get aws_registry_account # This one is needed
  • slsutil.renderer salt://docker/portal.sls # Does this render properly?
  • grains.get environment # make sure "test" is present
  • state.sls os_modifications # get some base stuff out of the way
  • grains.get ec2_tags:Name # make sure customer-portal is present for highstate to work
  • state.highstate # push everything including docker and docker images

Vault Auth Issues

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.