Skip to content
ツール・製品

AWS Details AI Product Tagging System Built With SageMaker Serverless Model Customization

AWSは、SageMakerのサーバーレスモデルカスタマイズ機能を使い、小売業の商品カタログにタグを付けるためにQwen3-8Bをカスタマイズした手順を公開した。

DigitalNeuron Desk約2分

ひとことで言うと

What did AWS announce about its SageMaker serverless model customization for product tagging?

AWSは、Qwen3-8Bオープンウェイトモデルをカスタマイズして商品タグ付けシステムを構築する技術解説を公開した。SageMakerのサーバーレスモデルカスタマイズ機能を用い、教師ありファインチューニングと検証可能な報酬による強化学習を組み合わせて調整したうえで、その成果をSageMaker非同期推論にデプロイし、カタログ情報の拡充に活用するという内容だ。

要点

  • AWSは、Amazon SageMakerのサーバーレスモデルカスタマイズを活用したAI搭載型商品タグ付けシステムの構築手順を公開した。
  • The walkthrough customizes the open-weight Qwen3-8B model, first with supervised fine-tuning (SFT), then with reinforcement learning with verifiable rewards (RLVR) using Group Relative Policy Optimization (GRPO).
  • AWSによると、SageMakerのサーバーレスモデルカスタマイズはトレーニング用の計算能力を自動的に管理し、コンピュート構成が指定されない場合、Amazon SageMakerがカスタマイズジョブ用の容量を自ら選択し、解放するという。
  • The optimized model is deployed separately to Amazon SageMaker Asynchronous Inference for batch-oriented catalog enrichment.
  • AWSによると、今回のウォークスルーは、顧客が選択したGPUインスタンスとカスタムトレーニングイメージを用いてAmazon SageMaker Training Jobsを利用した従来のQwen3-8Bの例とは異なり、Amazon SageMaker Python SDK v3のサーバーレスカスタマイズトレーナー(SFTTrainerおよびRLVRTrainer)を使用しているという。

AWS published a technical walkthrough describing how to build an AI-powered product tagging system using Amazon SageMaker serverless model customization, according to a blog post from AWS authors Linpo Guo, Ray Wang, Josh Chiu, and Kanwaljit Khurmi.

The problem AWS describes

AWS says retail catalogs rarely arrive with clean, structured attributes. Product names, descriptions, and category paths come from many sources and change continuously, the company says, and while search, recommendations, and catalog navigation depend on consistent tags, manually applying those tags across thousands of stock keeping units (SKUs) is slow and hard to keep consistent.

AWS says a general-purpose frontier model can generate tags through prompt engineering, but argues that when a tagging workflow has a narrower, stable objective — returning the right attributes in a fixed schema — customizing a smaller open-weight model can be a better fit. According to AWS, this approach lets a team teach the model the schema directly, optimize the trade-off between missing tags and unnecessary tags, and avoid paying for broad model capabilities the workflow doesn't need on every request.

What AWS built

In the walkthrough, AWS says it customizes the Qwen3-8B open-weight model in two stages: first with supervised fine-tuning (SFT), then with reinforcement learning with verifiable rewards (RLVR) using an approach called Group Relative Policy Optimization (GRPO).

AWS states that Amazon SageMaker serverless model customization manages the training capacity for this process. When no compute configuration is supplied, the company says, Amazon SageMaker selects and releases the training capacity for the customization job itself. The optimized model is then deployed separately, AWS says, to Amazon SageMaker Asynchronous Inference for batch-oriented catalog enrichment.

AWS distinguishes this approach from an earlier Qwen3-8B example in its amazon-sagemaker-examples repository, which it says used Amazon SageMaker Training Jobs (SMTJ) with customer-selected GPU instances and custom training images. This new walkthrough instead uses the Amazon SageMaker Python SDK v3 serverless customization trainers, which AWS names as SFTTrainer and RLVRTrainer.

Prerequisites AWS lists

AWS lists several resources and permissions needed before following the walkthrough:

  • Amazon SageMaker AI permissions to manage serverless customization jobs, AI Registry datasets and evaluators, model package groups, models, endpoints, and asynchronous inference, plus iam:PassRole where required
  • Amazon S3 access to read and write the source catalog, transformed training data, model artifacts, and asynchronous inference requests and outputs
  • Amazon ECR access, which AWS says is required only if a custom vLLM inference image is built and hosted, noting that serverless SFT and RLVR do not require a custom training image
  • Confirmation that the chosen AWS Region and model/technique combination supports Qwen3-8B SFT and RLVR
  • Sufficient hosting quota for ml.g6.2xlarge instances and the endpoint count used for the asynchronous endpoint

For data, AWS says the walkthrough uses the public Amazon Sales Dataset, or alternatively a private catalog transformed into the same prompt/target structure.

Source: AWS Machine Learning Blog, "Build an AI-powered product tagging system with Amazon SageMaker serverless model customization," published September 15, 2026.

よくある質問

What model does AWS use in this walkthrough?
AWSは、オープンウェイトモデルのQwen3-8Bをカスタマイズし、教師ありファインチューニングを施した後、Group Relative Policy Optimizationによる検証可能な報酬を用いた強化学習を実施している。
What AWS service manages the training capacity?
AWSによると、Amazon SageMakerのサーバーレスモデルカスタマイズはトレーニング用のコンピューティング容量を管理し、コンピューティング構成が指定されない場合、SageMakerがそのジョブ向けの容量を自動的に選択・解放するという。
How is the finished model deployed?
AWSによると、最適化されたモデルはバッチ処理によるカタログ拡充のため、Amazon SageMaker Asynchronous Inferenceに導入されているという。
What data does the walkthrough use?
AWSによると、このウォークスルーでは一般公開されているAmazon Sales Datasetを使用するか、あるいは同じプロンプト/ターゲット構造に変換した独自のカタログを利用するという。

出典

  1. Build an AI-powered product tagging system with Amazon SageMaker serverless model customization | Artificial IntelligenceAmazon Web Services (AWS)
タグawsamazon-sagemakermodel-customizationqwen3product-taggingfine-tuningreinforcement-learning

あわせて読みたい

{"duration_api_ms":2142,"stop_reason":"end_turn","session_id":"cb5bd98a-ef61-429a-92ff-94d414f9baab","total_cost_usd":0.0020774,"usage":{"input_tokens":2,"cache_creation_input_tokens":0,"cache_read_input_tokens":2647,"output_tokens":38,"output_tokens_details":{"thinking_tokens":0},"server_tool_use":{"web_search_requests":0,"web_fetch_requests":0},"service_tier":"standard","cache_creation":{"ephemeral_1h_input_tokens":0,"ephemeral_5m_input_tokens":0},"inference_geo":"not_available","iterations":[{"input_tokens":2,"output_tokens":38,"cache_read_input_tokens":2647,"cache_creation_input_tokens":0,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":0},"type":"message"}],"speed":"standard"},"modelUsage":{"claude-haiku-4-5-20251001":{"inputTokens":1074,"outputTokens":18,"cacheReadInputTokens":0,"cacheCreationInputTokens":0,"webSearchRequests":0,"costUSD":0.001164,"contextWindow":200000,"maxOutputTokens":32000,"thinkingTokens":0,"canonicalModel":"claude-haiku-4-5","provider":"firstParty","costBasis":"list"},"claude-sonnet-5":{"inputTokens":2,"outputTokens":38,"cacheReadInputTokens":2647,"cacheCreationInputTokens":0,"webSearchRequests":0,"costUSD":0.0009134000000000001,"contextWindow":1000000,"maxOutputTokens":64000,"thinkingTokens":0,"canonicalModel":"claude-sonnet-5","provider":"firstParty","costBasis":"list"}},"permission_denials":[],"terminal_reason":"completed","fast_mode_state":"off","fast_mode_disabled_reason":"sdk_opt_in_required","subagent_stats":{"spawned":0,"requested":{"background":0,"foreground":0,"unset":0},"started_in_background":0,"max_depth":0,"spawned_by_subagents":0,"completed":0,"failed":0,"killed":{"parent":0,"user":0,"system":0},"refused":{"depth_limit":0,"concurrency_limit":0,"budget":0},"by_type":{}},"is_error":false,"num_turns":1,"subtype":"success","api_error_status":null,"result":"AWS、Bedrock上のOpenAIモデルを比較するオープンソースベンチマークを公開","ttft_ms":1607,"type":"result","duration_ms":1639,"uuid":"3df90be3-9290-4b39-a22b-e9812c0f651f","ttft_stream_ms":1035,"time_to_request_ms":402,"queued_turn_count":0} Client.listTools() called but server does not advertise tools capability - returning empty list

AWSはブログ記事を公開し、ベンチマーク用ハーネス「openai-on-aws/benchmarks-openai」をオープンソースとして公開した。これはAmazon Bedrock上で提供される3種類のOpenAIモデルを、OpenAI API版の2種類のベースラインモデルと比較するもので、トークン単価だけでなく、正答あたりのコスト、マルチターンエージェントの運用コスト、ルーブリックによって採点された実務レベルの成果物の質を評価軸としている。

約3分