Fred Damstra [afs macbook] 3756f155c0 Updates modules with affected AWS 4.0 field names to v4.0.10		3 lat temu
..
005-iam	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
006-account-standards	3756f155c0 Updates modules with affected AWS 4.0 field names to v4.0.10	3 lat temu
006-account-standards-regional	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
007-aws-scheduler	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
007-backups	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
010-vpc-vmray	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
023-dns-resolver-instance	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
044-VMRay-Instances	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
072-salt-master-inventory-role	3c3caaf6da Updates Tags and CyberRange TF	3 lat temu
README.md	f6509ccb11 Adds a resolver instance to the VMRay VPC	3 lat temu
account.hcl	09a9331fe2 Revert "Upgrade TF and TG for Test env"	3 lat temu

mdr-test-malware

For hosting vmray and 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