- Newest
- Most votes
- Most comments
When you create a DMS replication subnet group, you need to specify at least two subnets that are in separate Availability Zones, and all subnets must be in the same VPC.
AWS DMS doesn't explicitly document a specific subnet selection strategy when multiple subnets are included in a subnet group. When you create a replication subnet group, you only specify the subnets, and AWS DMS determines the VPC on your behalf (as each subnet is linked to exactly one VPC).
Unlike some other AWS services that have documented subnet selection strategies (such as Amazon EMR, which evaluates subnets based on available IP addresses), DMS doesn't provide clear documentation on how it chooses between available subnets in a subnet group.
If you're concerned about IP address availability across your subnets, especially since they're shared with other services like EKS and have limited IP addresses, it would be prudent to:
- Monitor your subnet IP utilization
- Ensure you have sufficient IP addresses available across all subnets
- Consider using larger CIDR blocks for your subnets if possible
- Include multiple subnets across different Availability Zones in your subnet group to increase the likelihood of having available IP addresses
If you need a more predictable IP allocation strategy, you might want to create separate subnet groups with specific subnets designated for DMS usage to better control where your DMS resources are placed.
Sources
Setting up a network for a replication instance - AWS Database Migration Service
Enhance your workload resilience with new Amazon EMR instance fleet features | AWS Big Data Blog
Creating a subnet group for an AWS DMS migration project - AWS Database Migration Service
Relevant content
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
