Browse Source

Removes threatq lambda from Vault

Brad Poulton 3 years ago
parent
commit
d5a16a71d4
2 changed files with 0 additions and 24 deletions
  1. 0 11
      base/vault-configuration/main.tf
  2. 0 13
      base/vault-configuration/policies.tf

+ 0 - 11
base/vault-configuration/main.tf

@@ -114,17 +114,6 @@ resource "vault_aws_auth_backend_role" "portal-data-sync-lambda-role" {
   token_policies                  = ["portal"]
 }
 
-# resource "vault_aws_auth_backend_role" "threatq-data-sync-lambda-role" {
-#   backend                         = vault_auth_backend.aws.path
-#   role                            = "threatq-data-sync-lambda-role"
-#   auth_type                       = "iam"
-#   bound_iam_principal_arns        = ["arn:${var.aws_partition}:iam::${var.aws_account_id}:role/threatq-data-sync-lambda-role"]
-#   #inferred_aws_region             = "us-gov-east-1"
-#   token_ttl                       = 60
-#   token_max_ttl                   = 86400
-#   token_policies                  = ["threatq"]
-# }
-
 
 #----------------------------------------------------------------------------
 # AppRole Auth

+ 0 - 13
base/vault-configuration/policies.tf

@@ -82,19 +82,6 @@ resource "vault_policy" "portal" {
   policy = data.vault_policy_document.portal.hcl
 }
 
-# #threatq
-# data "vault_policy_document" "threatq" {
-#   rule {
-#     path         = "threatq-lambda*"
-#     capabilities = ["create", "read", "update", "delete", "list", "sudo"]
-#     description  = "threatq-lambda"
-#   }
-# }
-
-# resource "vault_policy" "threatq" {
-#   name   = "threatq"
-#   policy = data.vault_policy_document.threatq.hcl
-# }
 
 #salt-master should be able to only create tokens
 data "vault_policy_document" "salt-master" {