Skip to content

fix: add us-west-2 to Nova supported regions#5782

Merged
mollyheamazon merged 5 commits intoaws:masterfrom
pilgd-aws:fix/nova-region-gating-pdx
Apr 21, 2026
Merged

fix: add us-west-2 to Nova supported regions#5782
mollyheamazon merged 5 commits intoaws:masterfrom
pilgd-aws:fix/nova-region-gating-pdx

Conversation

@pilgd-aws
Copy link
Copy Markdown
Contributor

@pilgd-aws pilgd-aws commented Apr 21, 2026

Problem

NOVA_REGIONS in finetune_utils.py was hardcoded to ['us-east-1'], causing all trainers (SFTTrainer, DPOTrainer, RLVRTrainer, RLAIFTrainer) to raise a ValueError when instantiated in us-west-2, even though the SageMaker service supports Nova fine-tuning there.

Fix

Added us-west-2 to NOVA_REGIONS. Updated test__validate_model_region_availability_nova_invalid_region to use eu-west-1 (a genuinely unsupported region) and added us-west-2 to the valid-region test.

Testing

Nova fine-tuning in us-west-2 (PDX) has been verified working via the SageMaker console UI workflow — the PySDK should match service-level availability.

Unit tests run locally:

AWS_DEFAULT_REGION=us-east-1 python -m pytest tests/unit/train/common_utils/test_finetune_utils.py -v
55 passed in 3.08s

mollyheamazon
mollyheamazon previously approved these changes Apr 21, 2026
@mollyheamazon
Copy link
Copy Markdown
Contributor

@mollyheamazon mollyheamazon merged commit 27cb74f into aws:master Apr 21, 2026
3 of 4 checks passed
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.

3 participants