boto3 icon indicating copy to clipboard operation
boto3 copied to clipboard

In Sagemaker Boto3, I'm not able to look for the API's that can get the TrialComponentARN of the Model Package

Open KeyanatGiggso opened this issue 1 year ago • 3 comments

Describe the bug

In Sagemaker Notebook, When I register a Model able to see those details in the Model Registry Tab as follows, image Also, the Trial Component ARN which as follows in Sagemaker UI, image

Where is the Boto3 API for scraping those Trial Component ARN from Model Package?

Expected Behavior

To get the Trial Component ARN of the Model Package using the DescribeModelPackage

Current Behavior

It just scrapes the Artifacts and other stuffs, but not this one?

Reproduction Steps

Register a Model in sagemaker UI, and try to scrape the describe_model_package

Possible Solution

Kindly provide what is the relevant API for my problem

Additional Information/Context

No response

SDK version used

Boto3

Environment details (OS name and version, etc.)

jupyter notebook, Windows 10

KeyanatGiggso avatar Aug 26 '22 03:08 KeyanatGiggso

Hi @KeyanatGiggso thanks for reaching out. I think you may want to use list_trial_components. That will return the TrialComponentArn for each trial component. Or if you have the name of the trial component then you could run describe_trial_component. Would either of those commands help with what you're trying to accomplish?

tim-finnigan avatar Aug 26 '22 16:08 tim-finnigan

No @tim-finnigan, I was asking about the Registered Models with its Trial components ARN, I'm not getting in the describe_registered_model API for sure, where else can be bought those details?

KeyanatGiggso avatar Aug 28 '22 18:08 KeyanatGiggso

Hi @KeyanatGiggso thanks for following up. The available boto3 Sagemaker commands are listed here in the documentation. (There is also the sagemaker-python-sdk which may be better suited for what you're trying to accomplish). If what you're trying to do isn't currently an option then we can reach out to the Sagemaker team with the feature request.

tim-finnigan avatar Sep 01 '22 02:09 tim-finnigan

Since we haven't heard back in a while I'm going to close this issue. Please refer to the comment above for more information. For further assistance on issues related to SageMaker you could also consider asking the re:Post community or reach out through AWS Support. Thanks!

tim-finnigan avatar Nov 18 '22 19:11 tim-finnigan