aws / aws/sagemaker-python-sdk

SageMaker Bring Your Own Container on local mode - ProcessingOutput is not linked to local filesystem

Open
#3,083 7 comments 0 reactions 0 assignees View on GitHub
component: local mode component: pysdk-team Docker type: feature request
Dominant language
Python
Stars
2.3k
Forks
1.3k
Avg merge
1d 22h
Merged PRs (30d)
35

Description

**Describe the feature you'd like**
During the work with SageMaker BYOC on local mode (with Python SDK), we encountered the situation where the outputs of the container are staged into the SageMaker default artifact bucket. Then the SDK does not download those artifacts into the local file system.

**How would this feature be used? Please describe.**
We want that SDK will download the artifacts created automatically into the local file system.

**Describe alternatives you've considered**
We had to create a mechanism to download those files by ourselves:
![Lack_of_impl_on_S3_outputs_download](https://user-images.githubusercontent.com/14873156/165520867-4f54f67c-b502-4250-98ae-b032a374d41c.png)
In the following snippet of code, we used [https://github.com/aws-samples/amazon-sagemaker-local-mode/blob/main/scikit_learn_bring_your_own_container_local_processing/scikit_learn_bring_your_own_container_local_processing.py ](https://github.com/aws-samples/amazon-sagemaker-local-mode/blob/main/scikit_learn_bring_your_own_container_local_processing/scikit_learn_bring_your_own_container_local_processing.py) as a reference (also used the output_config dictionary)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.