How to Copy an Amazon Comprehend Custom Model Across Accounts?
An ML engineer has an Amazon Comprehend custom model in Account A in the us-east-1 Region. The ML engineer needs to copy the model to Account В in the same Region. Which solution will meet this requirement with the LEAST development effort?
Community Insight
The question tests cross-account sharing of an Amazon Comprehend custom model; the trap is assuming model artifacts must be manually moved through S3 or replicated with a data-transfer service.
Amazon Comprehend custom models can be shared across AWS accounts in the same Region by using a resource-based IAM policy and the ImportModel API. This page establishes that option B is the least-development-effort solution, not S3 copying, DataSync, or a VPN.
Choosing Amazon S3 because it is commonly used to move ML artifacts ignores that Comprehend provides ImportModel with a resource-based IAM policy specifically for cross-account custom model copies, while S3 transfer adds manual work.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon Comprehend provides the ImportModel API specifically to bring a custom model into an account, and AWS documentation states the source model can be in your AWS account or another one. The cross-account flow requires a resource-based IAM policy in Account A that grants Account B access to the model, then Account B calls ImportModel for the same Region. This uses managed Comprehend functionality, so the ML engineer does not need to move model artifacts manually or build networking infrastructure. Among the options, it is the only solution that directly performs a Comprehend custom model copy with minimal development effort. Saransundar's comment summarizes the export, resource-based policy, and ImportModel sequence.Why the Other Options Are Wrong
Copying the model through Amazon S3 sounds plausible because S3 is common for artifacts, but it does not provide a Comprehend-aware import and forces manual artifact handling. AWS DataSync is a data transfer service for files and object storage, not a mechanism for replicating Comprehend custom models between accounts. A Site-to-Site VPN creates private network connectivity, which is unnecessary for an AWS API-based cross-account model share and does not itself copy the model. These alternatives either address the wrong layer or add significant operational work compared with ImportModel.Community Comment Notes
GiorgioGss points to the ImportModel API documentation and quotes that "The source model can be in your AWS account or another one." Ranneh likewise says to use the Comprehend ImportModel API to share models between accounts within the same Region. dduenas shares the custom-copy import documentation link, reinforcing that this is the documented cross-account path. The comment consensus aligns with option B, and the official API behavior supports that verdict.Official Reference
Exam Strategy
For least-development-effort cross-account model sharing, look for a managed API plus a resource-based IAM policy rather than artifact copying or network setup. Options that require S3 transfers, DataSync, or VPNs add unnecessary work for an AWS service-to-service copy.
Frequently Asked Questions
Why is an S3 copy not the least-effort way to move a Comprehend custom model?
Comprehend custom models are shared through the ImportModel API; manually copying artifacts in S3 does not carry the model's Comprehend metadata and adds development work.
Does Comprehend ImportModel require both accounts to be in the same Region?
Yes, importing a Comprehend custom model requires the source and destination to be in the same Region, matching this scenario in us-east-1.
Related Analysis
Practice All MLA-C01 Questions
Access 115 questions with complete answers and detailed explanations.
View Full MLA-C01 Practice Test →