Skip to content

fix(jumpstart): add eusc-de-east-1 buckets and name JumpStart in the bucket error - #6242

Open
evakravi wants to merge 1 commit into
aws:master-v2from
evakravi:fix/jumpstart-neo-bucket-v2
Open

fix(jumpstart): add eusc-de-east-1 buckets and name JumpStart in the bucket error#6242
evakravi wants to merge 1 commit into
aws:master-v2from
evakravi:fix/jumpstart-neo-bucket-v2

Conversation

@evakravi

@evakravi evakravi commented Sep 8, 2026

Copy link
Copy Markdown
Member

Problem

In eusc-de-east-1, the sample notebook cell JumpStartModel(model_id="deepseek-llm-r1-distill-llama-8b", model_version="*", hub_name="SageMakerPublicHub") fails with ValueError: Unable to get content bucket for Neo in eusc-de-east-1 region. The model does not use Neo.

The v2 region configuration has no eusc-de-east-1 entry, so get_jumpstart_content_bucket raises for the region. Its error names Neo, a copy of the Neo accessor message. v3 got the region entry in #5615.

Solution

Add the public and gated JumpStart buckets for eusc-de-east-1 to the region configuration, with no Neo bucket. Name JumpStart in the get_jumpstart_content_bucket error. #6243 corrects the same error text in v3.

Tests

Unit tests read the eusc-de-east-1 public and gated buckets and match the JumpStart error text. The three tests fail on origin/master-v2 and pass on this branch.

SAGEMAKER_SUPPRESS_V2_WARNING=1 PYTHONPATH=src python -m pytest -s -vv tests/unit/sagemaker/jumpstart/test_utils.py::TestBucketUtils

Result: 12 passed in 1.93s.

integ-tests on master-v2 fails without this change. SageMaker rejects the ml.t2.medium fixture with ValidationException: Deprecated instance type "T2" since 2026-09-03, test_jumpstart_gated_model gets InsufficientInstanceCapacity, and the build_jar teardown deletes hello-spark-java.jar under xdist. Those tests are outside this change. The codestyle-doc-tests findings are in unchanged files.

Merge Checklist

  • I read the contribution guide.
  • The change is backward compatible.
  • The commits use the repository commit-message format.
  • The change creates no S3 or STS client.
  • The change has regression coverage and adds no dependency.

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

Comment thread src/sagemaker/jumpstart/utils.py Outdated
@evakravi evakravi changed the title fix(jumpstart): decouple JumpStart buckets from Neo fix(jumpstart): support EU Sovereign Cloud without Neo Sep 9, 2026
@evakravi evakravi changed the title fix(jumpstart): support EU Sovereign Cloud without Neo fix(jumpstart): use Neo only for models with speculative-decoding draft-model configs Sep 9, 2026
@evakravi
evakravi force-pushed the fix/jumpstart-neo-bucket-v2 branch from 759b466 to db71db2 Compare September 9, 2026 17:45
evakravi added a commit to evakravi/sagemaker-python-sdk that referenced this pull request Sep 9, 2026
`get_jumpstart_content_bucket` named Neo in its error for a region without a JumpStart entry. In v2 this message is the user-visible failure for `deepseek-llm-r1-distill-llama-8b` in `eusc-de-east-1` (aws#6242). Name JumpStart in the error.

The integration test loads the DeepSeek public metadata from `eusc-de-east-1` with an unsigned S3 client.

---
X-AI-Prompt: What is the minimal source change that fixes the EU Sovereign Cloud JumpStart error?
X-AI-Tool: claude-code
@evakravi evakravi changed the title fix(jumpstart): use Neo only for models with speculative-decoding draft-model configs fix(jumpstart): add eusc-de-east-1 buckets and name JumpStart in the bucket error Sep 9, 2026
…bucket error

`JumpStartModel` for `deepseek-llm-r1-distill-llama-8b` in `eusc-de-east-1` failed with `ValueError: Unable to get content bucket for Neo in eusc-de-east-1 region.` The region configuration had no `eusc-de-east-1` entry, and the JumpStart bucket accessor named Neo in its error. The model does not use Neo.

Add the public and gated JumpStart buckets for `eusc-de-east-1`. Name JumpStart in the error.

---
X-AI-Prompt: What is the minimal source change that fixes the EU Sovereign Cloud JumpStart error?
X-AI-Tool: claude-code
@evakravi
evakravi force-pushed the fix/jumpstart-neo-bucket-v2 branch from db71db2 to 408069a Compare September 10, 2026 13:14
evakravi added a commit to evakravi/sagemaker-python-sdk that referenced this pull request Sep 10, 2026
`get_jumpstart_content_bucket` named Neo in its error for a region without a JumpStart entry. In v2 this message is the user-visible failure for `deepseek-llm-r1-distill-llama-8b` in `eusc-de-east-1` (aws#6242). Name JumpStart in the error.

---
X-AI-Prompt: What is the minimal source change that fixes the EU Sovereign Cloud JumpStart error?
X-AI-Tool: claude-code
@evakravi
evakravi deployed to auto-approve September 10, 2026 13:14 — with GitHub Actions Active
@evakravi
evakravi force-pushed the fix/jumpstart-neo-bucket-v2 branch from 408069a to aee2dba Compare September 10, 2026 18:26
@evakravi
evakravi deployed to auto-approve September 10, 2026 18:54 — with GitHub Actions Active
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.

1 participant