fix(serve): support aliased hub content names in private hub deploys

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR

[e-davidson]

Issue

Deploying a JumpStart model from a private hub via ModelBuilder.from_jumpstart_config(hub_name=...) fails with ResourceNotFound when the hub's ModelReference was created with a custom HubContentName. The CreateHubContentReference API accepts an aliased name, but the SDK always looks up hub content by model_id, so aliased references are unreachable.

This is the remaining defect after #5985 (hub_arn derivation) and #6036 (model_reference_arn propagation / HubAccessConfig).

Fix

Optional hub_content_name on JumpStartConfig, threaded through from_jumpstart_config; when set, _build_for_jumpstart resolves hub content by the reference's actual name (3 files, +17 lines).

Test coverage

This PR also adds the regression coverage that would have caught the HubAccessConfig regression that shipped in v3.15.1-v3.16.0:

Unit (tests/unit/test_private_hub_artifact_resolution.py, extends the #5985 file):

• model_reference_arn propagation regression test guarding the Fix private hub #6036 fix (supersedes the subset assertions added there)
• CreateModel payload chain test: drives the real unmocked path _build_for_jumpstart -> _prepare_container_def_base and asserts the container definition carries S3DataSource.HubAccessConfig.HubContentArn for hub builds and omits it for public builds
• hub_content_name lookup + config threading tests
• Shared setup hoisted to a module-level _build_jumpstart_builder() helper per package convention

Integration (tests/integ/test_private_hub_artifact_resolution.py, slow_test, self-provisioning with full teardown):

• test_deploy_with_no_s3_execution_role: creates an execution role with zero S3 permissions, deploys from a private hub, asserts the created Model carries HubAccessConfig (the service-side brokered-access contract unit tests cannot reach)
• test_deploy_with_aliased_hub_content_name: deploys a reference named differently from the model_id

Verification (red -> green at every layer)

Layer	Baseline v3.16.0	With fix
Unit (17 tests)	4 discriminating tests FAIL	17/17 pass
Integ, live us-east-1	2 FAIL	2 pass (38s), both with the zero-S3 role

Live runs used a real private hub + ModelReference and an IAM role with no S3 permissions; all resources (hub, references, role, endpoints) cleaned up.

Replaces #6035, which predated #6036 and carried a now-redundant duplicate of the propagation fix.

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

[zhaoqizqwang]

All the added unit tests and integ tests have passed, merging the PR