Frederick Damstra 3d9a018c0c Merge pull request #269 from mdr-engineering/feature/ftd_na_WAFv2_for_Portal 3 tahun lalu
..
cloud-init 1ddc24fbfa Final Updates for Portal 4 tahun lalu
README.md 1ddc24fbfa Final Updates for Portal 4 tahun lalu
amis.tf 19b6f1bfc5 Adds Portal to GC 4 tahun lalu
certificate.tf fb25b7c56a Adds lifecycle policy to aws_acm_certificates 3 tahun lalu
ecr.tf c4faf2a12d Adds s3_binaries policy to portal instance profile 3 tahun lalu
elb.tf 19364e7516 Adds NATGW for Scanners 4 tahun lalu
main.tf ff9749f931 Adds outbound SMTPS for Portal 4 tahun lalu
outputs.tf 55da096763 Adds init Customer Portal 5 tahun lalu
rds.tf 842895b4b6 Updates Portal WAF to WAF v2 3 tahun lalu
vars.tf 19364e7516 Adds NATGW for Scanners 4 tahun lalu
version.tf 826dc0b5be Updates Terraform Version Requirements to 0.13 4 tahun lalu
waf.tf 842895b4b6 Updates Portal WAF to WAF v2 3 tahun lalu

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. 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.