You can also deploy a copy of Microsoft Windows Server 2012 R2 with full dual stack network support in AWS. You can provide dual stack DNS for nodes in your VPC with this, but DHCP (v4 and v6) is provided by AWS, so you should not try to deploy the Microsoft DHCP here.
The basic OS can be deployed with resources in the AWS Free Tier, but will run very slowly. To do anything “real” with Windows Server, you will need to step up to one of the higher models (which are not free).
Windows Server can provide Dual Stack DNS (for internal use). Since AWS provides DHCPv4 and DHCPv6 to the VPC (and in fact assigns addresses to the instances using it), you do not want to deploy DHCP in an AWS instance of Windows Server. There is a separate writeup of how to deploy Dual Stack DNS and DHCP for Windows Server 2012 R2 (ignore the section on DHCP in this case – that is for VirtualBox or hardware deployments). You can even deploy AD in your instance, and make use of it as a network directory from other MS instances, or as a general purpose LDAP server.