Skip to content

Upgrade sagemake sdk from v2 to v3#4875

Open
pdifranc wants to merge 1 commit intoaws:defaultfrom
pdifranc:upgrade_hpo_pytorch_to_v3
Open

Upgrade sagemake sdk from v2 to v3#4875
pdifranc wants to merge 1 commit intoaws:defaultfrom
pdifranc:upgrade_hpo_pytorch_to_v3

Conversation

@pdifranc
Copy link
Contributor

upgrade pytorch container to 2.x

Issue #, if available:

Description of changes:

upgrade sagemaker from v2 to v3 and upgrade pytorch container image used in training and inference

Testing done:

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

  • I have verified that my PR does not contain any new notebook/s which demonstrate a SageMaker functionality already showcased by another existing notebook in the repository
  • I have read the CONTRIBUTING doc and adhered to the guidelines regarding folder placement, notebook naming convention and example notebook best practices
  • I have updated the necessary documentation, including the README of the appropriate folder as well as the index.rst file
  • I have tested my notebook(s) and ensured it runs end-to-end
  • I have linted my notebook(s) and code using python3 -m black -l 100 {path}/{notebook-name}.ipynb

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

upgrade pytorch container to 2.x
@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

"local_dir = \"data\"\n",
"MNIST.mirrors = [\n",
" f\"https://sagemaker-example-files-prod-{region}.s3.amazonaws.com/datasets/image/MNIST/\"\n",
"base_url = f\"https://sagemaker-example-files-prod-{region}.s3.amazonaws.com/datasets/image/MNIST/\"\n",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommendation generated by Amazon CodeGuru Reviewer. Leave feedback on this recommendation by replying to the comment or by reacting to the comment using emoji.

Potential S3 bucket sniping vulnerability detected. This rule has identified S3 bucket references that could be vulnerable to bucket sniping attacks. Bucket sniping occurs when an attacker registers an S3 bucket name after finding it referenced in code but not yet created. This can lead to data exposure, malicious content hosting, or service disruption.

Recommendations:

  1. Create all referenced S3 buckets immediately
  2. Use organization-specific prefixes for bucket names
  3. Verify bucket ownership before use
  4. Consider using AWS Organizations S3 bucket naming rules

Discovered: datasets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants