Skip to content

fix: Networking vpc_config AttributeError and telemetry region fallba… - #5839

Merged
mujtaba1747 merged 2 commits into
aws:masterfrom
aviruthen:fix/networking-vpc-config-and-region
May 19, 2026
Merged

mujtaba1747 merged 2 commits into
aws:masterfrom
aviruthen:fix/networking-vpc-config-and-region

Conversation

@aviruthen

Copy link
Copy Markdown
Collaborator

Issue #, if available:

Fixes two bugs:

  1. AttributeError: 'Networking' object has no attribute 'vpc_config' — ModelBuilder._initialize_network_config() directly accesses self.network.vpc_config, but the Networking class (from sagemaker.core.training.configs) doesn't have that attribute. The else branch correctly handles Networking by reading subnets/security_group_ids directly, but execution never reaches it.
  2. Telemetry uses us-west-2 despite region override — The _telemetry_emitter decorator on @classmethod methods (like from_jumpstart_config) resolves args[0].sagemaker_session from the class descriptor (which is None), then falls back to a hardcoded us-west-2 default session. Customers with restricted network environments see timeouts on sts.us-west-2.amazonaws.com and sm-pysdk-t-us-west-2.s3.us-west-2.amazonaws.com.

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mujtaba1747
mujtaba1747 merged commit ac53dc4 into aws:master May 19, 2026
11 of 21 checks passed

This branch was previously deployed

1 inactive deployment
auto-approve — e874e4e9 Deployed May 19, 2026 by mujtaba1747 via wait-for-approval #907
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