DHCP Options set is a VPC construct, it can not be associated with a subnet. Please see below note from the documentation; although you can create multiple custom DHCP options set, each VPC can have MAX 1 DHCP options set associated with it.
A custom DHCP option set enables you to customize your VPC with your own DNS server, domain name, and more. You can create as many additional DHCP option sets as you want. However, you can only associate a VPC with one set of DHCP options at a time
Appreciate the quick response, @Tushar_j! So I guess the only way to work around to using DHCP in multiple subnets in the same VPC is to put the subnets in different VPCs then. Thank you.
Routing network traffic between two EC2 instances in the same subnet to a firewall appliance in another VPCAccepted Answerasked 6 months ago
Does Image Builder support build and test an image in a private VPC subnet without internet access?Accepted Answerasked 5 months ago
Recreate a default VPC within my Classic PlatformAccepted Answerasked a month ago
VPC subnet routing.Accepted Answerasked 6 months ago
Associating DHCP options with a subnet instead of VPC?Accepted Answerasked 23 days ago
VPC Interface Endpoint Limitation on one subnet per Availability Zone for "Enable Private DNS Name"Accepted Answerasked 5 years ago
AWS Client VPN - my systems are in different subnets that are in different VPCsasked 7 months ago
How do we correctly link the DC Gateway into the VPC, is a VG required?Accepted Answerasked a year ago
Subnets associated with a route table show as not associated with any RTasked 3 years ago
Error in CodeBuild: VPC_CLIENT_ERROR: Unexpected EC2 error: error while getting DHCP options for VPCasked 7 days ago