Fred Damstra [afs macbook] bf5415b5b6 Upgrades VPCs to v3.2.14 - Latest with VPC endpoint modification 3 years ago
..
005-iam fc64fd1df8 VMRay Deploys to Prod 3 years ago
006-account-standards 62d4bf076f Reenabled Customer CMK for cloudwatch and flowlogs in Malware Account 3 years ago
006-account-standards-regional fc64fd1df8 VMRay Deploys to Prod 3 years ago
007-backups 020a066431 Updates backups to latest 3 years ago
010-vpc-vmray bf5415b5b6 Upgrades VPCs to v3.2.14 - Latest with VPC endpoint modification 3 years ago
023-dns-resolver-instance f6509ccb11 Adds a resolver instance to the VMRay VPC 3 years ago
044-VMRay-Instances db14427089 Updates VMRay to Allow VNC Access 3 years ago
072-salt-master-inventory-role fc64fd1df8 VMRay Deploys to Prod 3 years ago
README.md f6509ccb11 Adds a resolver instance to the VMRay VPC 3 years ago
account.hcl 8214325898 Updates vmray to 3.2.0 for Dedicated Drive 3 years ago

README.md

mdr-prod-malware

Account for hosting vmray and/or other malware detonation.

NOTE ON DNS

DNS resolvers exist in this account, in the vpc 010... However, the vpc relies on having dns resolvers to set the DHCP options.

So chicken/egg.

Here's how to do it.

1) Create the vpc with the default var.dns_servers. 2) Create the resolver 3) Update the VPC, overriding var.dns_servers with the IP from #2