Skip to content

fix(examples): use valid instance_count for Nova serverful SMTJ SFT notebook#6046

Merged
lucasjia-aws merged 1 commit into
aws:masterfrom
Hannah14295:fix/sft-serverful-instance-count
Jul 17, 2026
Merged

fix(examples): use valid instance_count for Nova serverful SMTJ SFT notebook#6046
lucasjia-aws merged 1 commit into
aws:masterfrom
Hannah14295:fix/sft-serverful-instance-count

Conversation

@Hannah14295

Copy link
Copy Markdown
Contributor

SFTTrainer for amazon.nova-2-lite-v1 serverful SMTJ fine-tuning requires instance_count in {4, 8, 16, 32}; the notebook used instance_count=2, which the SDK rejects client-side at train() with "Node/Instance count '2' is not supported. Allowed values: [4, 8, 16, 32]". Set both SFTTrainer compute blocks to 4 (the minimum valid value).

Description of changes:
The sft_finetuning_serverful_smtj example fails at train() because it
constructs SFTTrainer with instance_count=2. For amazon.nova-2-lite-v1
serverful SMTJ fine-tuning, the SDK requires instance_count in
{4, 8, 16, 32} and rejects 2 client-side:

ValueError: Node/Instance count '2' is not supported.
Allowed values: [4, 8, 16, 32].

This sets both SFTTrainer compute blocks to instance_count=4 (the minimum
valid value). The ModelTrainer.from_recipe block (instance_count=1) is
unaffected.

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

SFTTrainer for amazon.nova-2-lite-v1 serverful SMTJ fine-tuning requires
instance_count in {4, 8, 16, 32}; the notebook used instance_count=2, which
the SDK rejects client-side at train() with "Node/Instance count '2' is not
supported. Allowed values: [4, 8, 16, 32]". Set both SFTTrainer compute
blocks to 4 (the minimum valid value).
@lucasjia-aws
lucasjia-aws merged commit 6659b11 into aws:master Jul 17, 2026
6 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