hf-cloud-sagemaker-deployment-planner

Plans Amazon SageMaker model deployments by selecting inference pathways and instance types.

507|40|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/waybarrios/opencode-power-pack --skill hf-cloud-sagemaker-deployment-planner-waybarrios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hf-cloud-sagemaker-deployment-planner
Source: https://github.com/waybarrios/opencode-power-pack/tree/main/skills/hf-cloud-sagemaker-deployment-planner
Command: npx skills add https://github.com/waybarrios/opencode-power-pack --skill hf-cloud-sagemaker-deployment-planner-waybarrios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a model to Amazon SageMaker requires choosing between real-time, serverless, async, batch, and Bedrock pathways, each with different cost, latency, and quota constraints. This Skill guides that decision with minimal questions and hands off to specialized implementation skills. ## Core Features & Use Cases - Pathway Selection: Compares real-time endpoints, serverless inference, async inference, batch transform, and Bedrock Custom Model Import against traffic shape, latency tolerance, and model type. - Quota-Aware Instance Recommendation: Checks SageMaker service quotas per region before recommending GPU instance families like ml.g5, ml.g6, or ml.g6e to avoid ResourceLimitExceeded failures. - Workflow Orchestration: Coordinates handoffs to context discovery, IAM preflight, image selection, and production deployment skills. - Use Case: A user wants to deploy a fine-tuned LLM. The Skill asks only what model and how often it will be called, recommends a real-time endpoint on ml.g5.xlarge after verifying quota, then defers implementation to downstream skills. ## Quick Start Ask the assistant to plan a SageMaker deployment for your HuggingFace model, describing roughly how often it will be called.

Frequently Asked Questions about hf-cloud-sagemaker-deployment-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between SageMaker real-time and serverless inference?▼

Choose real-time endpoints for steady traffic with sub-second to few-second latency needs. Serverless fits spiky or intermittent traffic that tolerates cold starts around 10 seconds, but most LLMs above a few billion parameters exceed its memory limits.

When should I use SageMaker async inference for model deployment?▼

Use async inference for workloads exceeding 60 seconds per request, such as text-to-image or video generation, especially with bursty traffic. It queues requests via S3 and supports scale-to-zero between batches so you avoid paying for idle GPU.

Why does SageMaker endpoint creation fail with ResourceLimitExceeded?▼

Endpoint quotas are per instance type and region, and GPU quotas default to zero in many accounts. Check available quotas with the aws service-quotas list-service-quotas command before creating anything, and request an increase if your target instance type is missing.

Should embedding models on SageMaker use GPU or CPU instances?▼

CPU instances are usually the right choice for embedding models under 1 billion parameters with moderate traffic, since they are much cheaper and fast enough. Reserve GPU instances for larger models or high-throughput requirements.

What is the difference between ml.g5 and ml.g6 instances on SageMaker?▼

Both are 24 GB GPU tiers working with current vLLM images. ml.g6 (L4) is newer and slightly cheaper per hour, while ml.g5 (A10G) has roughly double the memory bandwidth, typically giving better LLM token throughput.