It really boils down to just these 2 options.
This assumes that there is network connectivity either Site-to-Site VPN or DirectConnect between your on-premises environment and AWS without overlapping CIDR ranges. For this, just stand up new EC2 instances and dc promo them as additional domain controllers in your forest. Once the new DCs are fully operational, you can set their IP into the DHCP option set for the VPC.
If you don't plan to connect the two environments, then you can use the AWS Application Migration Service or VM Import/Export to make block-level duplicates of the on-premise servers, even keeping the on-premise IP addresses (if the network topology allows it).
aws smb for windows not connecting to active directory made by AWS directorasked 2 years ago
Domain Controller Migration from On-premise to AWSasked 4 months ago
Two way trust with on-prem domain fails on AWS sideasked 7 months ago
Restore best practice for AWS Backup and Windows domain joined EC2 instances?asked 8 months ago
Joining an AWS Managed Microsoft AD to an existing domainAccepted Answer
Lift and Shift Windows 7 and 10 osasked a month ago
Migrating On premise windows Domain controller to AWS EC2asked a month ago
Is it possible and OK to migrate Windows Server 2008 and SQL 2008 R2 as isasked 3 years ago
Accessing AWS FSX from a windows EC2 that is not joined to the same domain.asked 4 months ago
Autoscaling windows ec2 and autojoin to domainAccepted Answer