Copying a Comprehend Custom Model Between AWS Accounts with ImportModel and a Resource-Based Policy

Why the Answer Is Correct

Amazon Comprehend provides the ImportModel API operation specifically for copying a custom model, and its documentation states that the source model can be in your own AWS account or another one, which is exactly the cross-account transfer this question requires. The only supporting work is a resource-based IAM policy in Account A that grants Account B permission to access the model, and then the ImportModel call in Account B completes the copy. That makes this the least-development-effort path because it uses the service's own transfer operation rather than moving and re-registering artifacts manually. The vote was unanimous at 100 for B. Saransundar laid out the three-step procedure of exporting from Account A, creating the resource-based policy to grant Account B access, and calling ImportModel in Account B, and GiorgioGss quoted the ImportModel reference noting the source model can be in another account.

Why the Other Options Are Wrong

Using Amazon S3 to make a copy and transferring it to Account B (A) only moves the underlying artifact; the model still has to be imported and registered as a Comprehend custom model in the target account, and the option describes no such step, so it does not complete the copy at the service level. Using AWS DataSync to replicate the model (C) is a mismatch because DataSync is designed to replicate files and datasets between storage locations, not to transfer a service-managed custom model resource between accounts. Creating a Site-to-Site VPN connection to transfer the model (D) establishes network connectivity between the accounts but provides no mechanism to import the model into Comprehend in Account B, so the model would arrive as bytes rather than as a usable custom model.

Community Comment Notes

The community was unanimous at 100 for B, and the comments focus on the mechanics of the supported path. Saransundar enumerated the exact three steps, which is effectively the operational runbook for this transfer. GiorgioGss cited the ImportModel API reference for the decisive point that the source model may live in another AWS account, and dduenas cited the Comprehend documentation page on copying and importing custom models, confirming that this is the documented approach rather than a workaround.