> coreweave-migration-deep-dive
Migrate ML workloads from AWS/GCP/Azure to CoreWeave GPU cloud. Use when moving inference services from hyperscaler GPU instances, migrating training pipelines, or evaluating CoreWeave vs cloud GPU costs. Trigger with phrases like "migrate to coreweave", "coreweave migration", "move from aws to coreweave", "coreweave vs aws gpu".
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/coreweave-migration-deep-dive?format=md"CoreWeave Migration Deep Dive
Cost Comparison
| Instance | AWS | CoreWeave | Savings |
|---|---|---|---|
| 1x A100 80GB | ~$3.60/hr (p4d) | ~$2.21/hr | ~39% |
| 8x A100 80GB | ~$32/hr (p4d.24xl) | ~$17.70/hr | ~45% |
| 1x H100 80GB | ~$6.50/hr (p5) | ~$4.76/hr | ~27% |
Migration Steps
Phase 1: Containerize
# If running on bare EC2/GCE, containerize first
docker build -t inference-server:v1 .
docker push ghcr.io/myorg/inference-server:v1
Phase 2: Adapt YAML for CoreWeave
Key changes from AWS EKS / GKE:
- Node affinity: Use
gpu.nvidia.com/classinstead ofnvidia.com/gpu.product - Storage: Use CoreWeave storage classes (
shared-ssd-ord1) - Networking: CoreWeave provides flat networking within VPC
Phase 3: Parallel Deploy
Run both old and new infrastructure simultaneously, gradually shift traffic.
Phase 4: Cut Over
Decommission old GPU instances after validation period.
Common Gotchas
| Issue | Solution |
|---|---|
| Different CUDA drivers | Match container CUDA to CoreWeave node drivers |
| Storage migration | Use rclone or rsync to move data to CoreWeave PVC |
| DNS changes | Update ingress/load balancer DNS |
| IAM differences | CoreWeave uses kubeconfig, not IAM roles |
Resources
Next Steps
This completes the CoreWeave skill pack. Start with coreweave-install-auth for new deployments.
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".