Переглянути джерело

Adds IPs to vpc-private-servers to support legacy resources

Duane Waddle 4 роки тому
батько
коміт
6a374c60b7
1 змінених файлів з 6 додано та 1 видалено
  1. 6 1
      prod/env.hcl

+ 6 - 1
prod/env.hcl

@@ -37,7 +37,12 @@ locals {
                                "10.80.101.197/32", # legacy repo
                                "10.80.1.107/32",   # legacy smtp
                              ],
-    "vpc-private-services" = [ "10.40.28.0/22" ],                 # Private Services - fm-shared-search, qcompliance, phantom, etc.
+    "vpc-private-services" = [
+                               "10.40.28.0/22",                  # Private Services - fm-shared-search, qcompliance, phantom, etc.
+                               "10.80.101.221/32",               # Phantom - legacy account production
+                               "10.80.0.0/16",                   # the whole legacy infra VPC, so the sync lambda can sync (this is temp)
+                                                                 # (wes made me do it honest)
+                             ],
 
     # "old" mappings before architecture planning... we should eliminate these.
     "bastions" = [ "10.80.101.133/32", "10.40.20.0/22" ], # vpc-access in mdr-prod-c2-gov