explainx.ai350K+ learn from us
TrendingAI News TodayExplainx for Business
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • FFT versus LoRA in plain language
  • The November 18 experiment design
  • Evaluation trio AWS ships serverlessly
  • Hyperparameters AWS sweeps
  • When AWS says to stay on LoRA
  • How this compares to other serverless trainers
  • Builder checklist for this week
  • Spectral view: why AWS says rank limits LoRA
  • Rapid experimentation story
  • PRIMECODE versus LLM-as-Judge
  • Operational details builders ask in search
  • Failure modes to log in your runbook
  • Enterprise procurement angle
  • Step-by-step first FFT job
  • Documentation pointers
  • Cost realism
  • Related reading
← Back to blog

explainx / blog

AWS SageMaker FFT: Full Fine-Tuning on Serverless Model Customization

Amazon Web Services, Fine-Tuning, SageMaker, LoRA, Guides

Part of AI Research

Amazon added Full Fine-Tuning to SageMaker AI Serverless Model Customization Nov 18, 2026. AWS shows FFT beating LoRA at 100K examples on code tasks with MMLU guardrails.

Nov 19, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
AWS SageMaker FFT: Full Fine-Tuning on Serverless Model Customization

Amazon SageMaker AI Serverless Model Customization now supports Full Fine-Tuning (FFT), not only parameter-efficient LoRA adapters. AWS published the workflow on November 18, 2026, arguing FFT can close quality gaps on large, complex corpora when LoRA plateaus.

For builders on Bedrock AgentCore or custom model routes, the headline is operational: one serverless job type now spans cheap adapters and full-rank updates without a separate training stack.

Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

FFT versus LoRA in plain language

LoRA freezes base weights and trains small low-rank matrices. It saves GPU memory and trains fast. AWS warns that low-rank updates can cap representation power as tasks grow—extra rank does not always catch up to full fine-tuning.

FFT updates all parameters together. AWS says that preserves layer alignment better on complex domain shifts, especially when datasets exceed tens of thousands of high-quality examples.

table · 4 cols
MethodMemoryBest whenRisk AWS highlights
LoRALowerSmaller shifts, budget fine-tunesRank plateaus on hard tasks
FFTHigherLarge curated corpora, code style absorptionCatastrophic forgetting at aggressive LR

This is not an either-or religion. AWS's own charts show LoRA winning one LLM-as-Judge comparison while FFT wins aggregate PRIMECODE and large-scale judge scores.

The November 18 experiment design

AWS ran supervised fine-tuning on Qwen3-4B using Magicoder-Evol-Instruct-110K—110,000 coding instruction pairs spanning algorithms, debugging, and systems topics. Split:

  • 99,000 train
  • 5,500 validation
  • 5,500 held-out test

Jobs ran on SageMaker AI Serverless Model Customization with identical prompts and evaluation code for LoRA and FFT branches.

Code entry point

AWS sample code constructs SFTTrainer with TrainingType.FULL:

python
from sagemaker.train.sft_trainer import SFTTrainer
from sagemaker.train.common import TrainingType

trainer = SFTTrainer(
    model=base_model_id,
    training_type=TrainingType.FULL,
    model_package_group=model_package_group_name,
    training_dataset=training_dataset,
    validation_dataset=val_dataset,
    s3_output_path=output_path,
    sagemaker_session=sess,
    role=role,
)

trainer.hyperparameters.learning_rate = 2e-5
trainer.hyperparameters.global_batch_size = 8
trainer.hyperparameters.max_epochs = 2
trainer.hyperparameters.lr_warmup_steps_ratio = 0.1

trainer.train(wait=False)

Switching to LoRA is TrainingType.LORA only—everything else unchanged per AWS.

Fine-tuned artifacts register as versioned Model Packages in the SageMaker Model Registry when jobs complete.

Evaluation trio AWS ships serverlessly

LLM-as-Judge semantic correctness FFT versus LoRA at 100K examplesLLM-as-Judge semantic correctness FFT versus LoRA at 100K examples Image: Amazon Web Services

AWS evaluates inside the same serverless product:

  1. LLM-as-Judge — Amazon Nova Pro judges whether generated code is logically correct versus the prompt.
  2. PRIMECODE — Deterministic BLEU, ROUGE, and F1 against reference solutions for reproducible code-style metrics.
  3. MMLU — Forgetting detector across 57 academic subjects; tracks whether code fine-tuning erases general knowledge.

At 100K+ scale AWS charts ~90% LLM-as-Judge semantic correctness for FFT on the coding task setup they describe. Radar charts show FFT extending farther than LoRA across multiple quality axes in the same post.

Caveat: Those figures are AWS-run benchmarks on a single public dataset. Replicate on your validation set before production routing.

Hyperparameters AWS sweeps

Learning rate dataset size risk map for SageMaker full fine-tuningLearning rate dataset size risk map for SageMaker full fine-tuning Image: Amazon Web Services

Learning rate

FFT touches every weight. AWS maps learning rate × dataset size risk: 2e-5 at 100K+ examples landed in their safe zone. ≥5e-5 wrecked MATH exact match and drove MMLU toward ~3.6% in aggressive configs—classic catastrophic forgetting.

Epochs

AWS treats max epochs as a forgetting knob, not a loss-curve game. ~3 epochs raised judge scores toward 90%, but beyond 3 degraded variants they tried—even when validation loss still looked fine on in-distribution code.

Batch size

Smaller batches add noise akin to higher LR; larger batches smooth updates but reduce steps. AWS includes batch-size trade-off charts in the post.

Warmup

A configuration with 5% warmup, batch size 8, and LR 2e-5 best preserved MMLU in their forgetting study.

When AWS says to stay on LoRA

The post is explicit FFT is not universal:

  • Both FFT and LoRA trailed the base model on MATH exact match in some runs.
  • LoRA at 81.5% beat FFT at 79.5% on one LLM-as-Judge setup AWS lists.
  • Aggressive FFT schedules destroyed general benchmarks.

Pick FFT when you have large, clean in-domain data and monitoring for MMLU-style drift. Stay on LoRA when budgets, iteration speed, or subjective judge alignment matter more.

How this compares to other serverless trainers

table · 3 cols
PlatformFull-weight SFT serverlessNotes
SageMaker (this launch)Yes, TrainingType.FULLBundled judge + PRIMECODE + MMLU
Baseten LoopsSFT and RL per tokenDifferent billing model
Snowflake Cortex TrainingPreview SFT and RLWarehouse-adjacent

SageMaker's angle is enterprise registry + evaluation batteries in one managed lane—valuable if you already standardize on AgentCore identity.

Builder checklist for this week

  1. Inventory data size. Below ~10K curated examples, start LoRA; plan FFT trials when growth toward 100K is realistic.
  2. Pin evaluation. Export baseline MMLU and domain-held-out sets before first FFT job.
  3. Cap LR at AWS's 2e-5 starting point unless your regression suite proves otherwise.
  4. Stop at epoch 3 until you see forgetting curves flatten safely.
  5. Register packages in Model Registry for rollback when coding model scores rise but merge rates fall.

Spectral view: why AWS says rank limits LoRA

The AWS post dives into weight matrix spectra: LoRA applies a low-rank delta that cannot express every direction full fine-tuning can move. As datasets scale, the missing directions show up as plateaus in judge scores even when you increase LoRA rank.

FFT modifies matrices uniformly, which AWS ties to better activation alignment across layers. You do not need to accept the theory wholesale to use the practical signal: when validation loss stalls while train loss falls on LoRA, FFT is the next serverless knob—if your MMLU guardrail passes.

Rapid experimentation story

AWS emphasizes tens of jobs in a short window because serverless removes cluster babysitting. They swept:

  • Training type (FFT vs LoRA)
  • Learning rate, batch, warmup, epochs
  • Base models: Qwen3-4B, DeepSeek-R1-1.5B, Nemotron-30B, Gemma-4-26B

Each job registered outputs in Model Registry, so promotion to endpoints stays auditable—important when audit agents ask for lineage.

PRIMECODE versus LLM-as-Judge

PRIMECODE rewards n-gram overlap with reference solutions—great for detecting formatting conventions and API usage patterns in code corpora. LLM-as-Judge rewards logical correctness from Nova Pro's reading of the prompt plus code.

AWS uses both because neither alone is sufficient: a solution can look like the reference yet be wrong, or be correct yet novel. If you only track loss, you miss the split.

Operational details builders ask in search

Do I provision GPUs? AWS says no—serverless customization allocates compute for the job.

Where do checkpoints live? S3 output paths you provide; registered packages surface in Model Registry.

Can I A/B in production? Use packages as versions; pair with higher merge-rate experiments before routing traffic.

What about RL after SFT? This post covers SFT only; combine with your RL stack separately—compare MIT agent self-improvement loops if you chain RL after FFT.

Failure modes to log in your runbook

  1. MMLU cliff after epoch 3 — roll back package, reduce LR, or shorten epochs.
  2. Judge regression vs base on subjective tasks — LoRA may be the better tool per AWS's own tie cases.
  3. MATH exact match collapse — treat as forgetting alarm, not noise.
  4. Cost spikes — FFT uses more compute than LoRA; watch job duration against TSMC credit stories only if you finance GPU-hours centrally.

Enterprise procurement angle

Teams already buying SageMaker for compliance get FFT without a separate vendor. That matters when Snowflake and Baseten compete on per-token economics but your IAM boundary is AWS-only.

Document Nova Pro judge costs in FFT evaluation—they are not free tokens even when training is serverless.

Step-by-step first FFT job

  1. Register Magicoder or your corpora in SageMaker dataset assets.
  2. Create a model package group for promotion discipline.
  3. Instantiate SFTTrainer with TrainingType.FULL and conservative LR 2e-5.
  4. Run MMLU baseline on the base package before training.
  5. Train with max_epochs=2 first; inspect PRIMECODE and judge on held-out code.
  6. Compare against a LoRA twin job on identical splits.
  7. Promote only if MMLU drop sits inside your risk tolerance.

Documentation pointers

AWS links hyperparameter docs for Serverless Model Customization on the SageMaker doc site—read those alongside this post for field names that change release to release. The blog date is November 18, 2026; if your account lacks TrainingType.FULL, your region may still be rolling out—open a support case rather than assuming the blog is wrong.

For dataset hygiene, Magicoder-Evol-Instruct is a public corpus tied to the Magicoder paper on OSS-Instruct and Evol-Instruct data; enterprise teams should mirror the 90/5/5 split discipline on proprietary logs with PII stripped, similar to how GitHub and Microsoft m-dash reports stress provenance before automation.

Cost realism

Serverless does not mean free. FFT updates more parameters per step than LoRA, so expect longer jobs and higher GPU-second bills even without cluster admin overhead. Model the inference savings only after you measure quality uplift on your held-out suite—do not assume FFT inference is cheaper; you may deploy a smaller specialized model that beats a frontier generalist on your task, which is the economic story AWS tells at the top of its post. Keep a LoRA checkpoint as rollback until FFT wins on your judge suite twice in a row.

Related reading

  • Baseten Loops serverless SFT
  • Snowflake Cortex training preview
  • AWS Bedrock AgentCore identity
  • Higher scoring models and merge rates
  • Qwen38 OpenCode adapter LoRA

Benchmarks and charts come from the AWS Machine Learning Blog post dated November 18, 2026; rerun on your data before production commits. Contact AWS support if TrainingType.FULL is missing in your account region.

Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Nov 12, 2026

Hugging Face 3D LoRA Guide: Fine-Tune TRELLIS.2 on Your Meshes

Hugging Face released scripts to fine-tune TRELLIS.2 on custom 3D assets via LoRA, targeting shape errors like incorrect shoe soles. The guide walks pipeline stages, what to freeze, and how to run on Hugging Face Jobs or local Docker.

Nov 13, 2026

OpenFold3 on SageMaker JumpStart: Async Protein Folding in AWS

On November 13, 2026 AWS published a SageMaker JumpStart guide for OpenFold3-preview — the OpenFold Consortium structure predictor — with asynchronous inference, optional private MSAs, multi-GPU parallelism, and scale-to-zero to cut idle GPU bills. explainx.ai walks through what changed and how it compares to BioNeMo paths we already cover.

Nov 11, 2026

AWS October 2026 ICYMI: Bedrock Models, AgentCore Gateway, and Strands Updates

Amazon machine learning blog ICYMI for October 2026 bundles Bedrock model launches, AgentCore availability features, structured JSON outputs, cost visibility, and Strands open-source agent tooling for builders shipping production agents.