- Newest
- Most votes
- Most comments
The issue you’re facing seems to be a common one when using AWS SageMaker’s SDK with custom algorithms. The AlgorithmName parameter in the create_model_package function can accept both an ARN (Amazon Resource Name) and a name. However, the behavior differs based on whether the algorithm is from the marketplace or a custom one.
For marketplace algorithms, the ARN works, but the name doesn’t. For custom algorithms, the name works, but the ARN doesn’t. This discrepancy can cause confusion and issues when using the SageMaker SDK, as it automatically passes the ARN, which fails for custom algorithms.
Unfortunately, there isn’t a straightforward solution to this issue as it seems to be a limitation with the SageMaker SDK itself. One potential workaround could be to manually create the model package using the AWS CLI or the AWS Management Console, specifying the algorithm’s name instead of the ARN for custom algorithms.
Relevant content
- asked 2 years ago
- Accepted Answerasked a year ago
- Accepted Answerasked 5 years ago
- AWS OFFICIALUpdated 17 days ago
- AWS OFFICIALUpdated 17 days ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago