Is ok to have multiple Serverless replications in DMS using the same source endpoint migrating the same table more than once?

Yes, it is generally acceptable to have multiple AWS DMS Serverless replications using the same source endpoint and migrating the same table more than once. However, there are some important considerations to keep in mind:

1. Resource utilization: Each serverless replication will consume resources independently. While AWS DMS Serverless automatically manages capacity, having multiple replications of the same data may lead to increased resource usage and potentially higher costs.

2. Storage limitations: AWS DMS Serverless provides a static 100GB allocated storage for each replication. If your replications collectively require more memory than this, due to factors like long-running transactions or caching, you might encounter issues.

3. Workload partitioning: In some cases, partitioning your workload into separate serverless replications can be beneficial. For example, you might want to separate replications involving LOBs (Large Objects) or partition by table requirements.

4. Performance impact: Multiple replications reading from the same source tables could potentially impact the performance of the source database, depending on its capacity and current load.

5. Consistency: Ensure that your multiple replications are configured consistently to avoid discrepancies in the migrated data.

While it's technically possible to have multiple serverless replications using the same source endpoint and migrating the same table more than once, it's important to carefully consider your specific use case and requirements. You should evaluate whether this approach is the most efficient and cost-effective for your migration needs.
Sources
Working with AWS DMS Serverless - AWS Database Migration Service
AWS DMS Serverless limitations - AWS Database Migration Service