How to Copy an Amazon Comprehend Custom Model Across Accounts?

MLA-C01 By islever Editorial Last updated

Secure AWS resources.

Short answer

B Create a resource-based IAM policy in Account A and use the Amazon Comprehend ImportModel API in Account B to copy the custom model.

Question

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?
  1. Use Amazon S3 to make a copy of the model. Transfer the copy to Account B.
  2. Create a resource-based IAM policy. Use the Amazon Comprehend ImportModel API operation to copy the model to Account B. Correct Answer
  3. Use AWS DataSync to replicate the model from Account A to Account B.
  4. Create an AWS Site-to-Site VPN connection between Account A and Account В to transfer the model.

Key Takeaways

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.

Common mistake: 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.

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

These links open the official vendor documentation in a new tab.

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.

More MLA-C01 FAQ →

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. Saransundar 👍 4 Answered B
    Amazon Comprehend - ImportModel API to facilitate the transfer of custom models between AWS accounts. STEPS: 1. Exporting the model from Account A. 2. Creating a resource-based IAM policy in Account A to grant access to Account B. 3. Using the ImportModel API in Account B to import the model.
  2. GiorgioGss 👍 2 Answered B
    https://docs.aws.amazon.com/comprehend/latest/APIReference/API_ImportModel.html "The source model can be in your AWS account or another one."
  3. Ranneh 👍 1 Answered B
    use the comprehend importmodel API to share models between accounts within the same region
  4. dduenas 👍 1 Answered B
    https://docs.aws.amazon.com/comprehend/latest/dg/custom-copy-importing.html

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Choosing LightGBM in SageMaker for Fraud Detection with Class Imbalance and Correlated Features

S-grade

Processing Mixed CSV JSON XLSX Parquet Files in One S3 Folder with DataBrew and Outputting Apache Parquet

S-grade

Rebuilding the Model Monitor Baseline After a Model Update Causes Data Quality Violations

S-grade

Orchestrating SageMaker ML Workflows as DAGs in Studio with ML Lineage Tracking for Governance

S-grade

Practice All MLA-C01 Questions

Access 115 questions with complete answers and detailed explanations.

View Full MLA-C01 Practice Test →

← Back to MLA-C01 Study Guide