aws-sdk-v2-to-v3-migration

Migrate AWS SDK v2 imports and constructors to v3 clients and commands.

1|1|Updated May 3, 2026
One-click install
npx skills add https://github.com/matt-riley/agent-skills --skill aws-sdk-v2-to-v3-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-sdk-v2-to-v3-migration
Source: https://github.com/matt-riley/agent-skills/tree/main/skills/aws-sdk-v2-to-v3-migration
Command: npx skills add https://github.com/matt-riley/agent-skills --skill aws-sdk-v2-to-v3-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrate AWS SDK v2 usage to AWS SDK v3 without changing runtime behavior, enabling a modular, future-proof codebase.

Core Features & Use Cases

  • Inventory and map all v2 imports and constructors (e.g., new AWS.*) to the corresponding v3 clients and commands.
  • Update tests, mocks, and helpers to align with the v3 dispatch model (client.send(command)).
  • Plan and execute incremental migrations per service, preserving region, credentials, and configuration.

Quick Start

Start by inventorying all aws-sdk v2 imports and map them to their v3 equivalents before changing code.

Frequently Asked Questions about aws-sdk-v2-to-v3-migration

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

FAQPage Schema
How do I migrate AWS SDK v2 code to v3 without changing runtime behavior?

To migrate AWS SDK v2 code to v3 safely, inventory all v2 imports and map them to v3 clients and commands, then update tests and mocks to align with the v3 dispatch model using client.send(command).

What is the best way to handle AWS SDK v3 migration for DocumentClient and s3.upload?

Handling AWS SDK v3 migration for DocumentClient and s3.upload involves mapping them to their modular v3 client-command equivalents, enforcing explicit v3 patterns while preserving region, credentials, and configuration.

How does AWS SDK v3 migration affect my existing TypeScript tests and mocks?

AWS SDK v3 migration requires updating existing TypeScript tests and mocks to align with the v3 dispatch model, replacing v2 promise-based calls and constructor mocks with the new client.send(command) pattern.

Can I migrate AWS SDK v2 to v3 incrementally per service?

Yes, you can migrate AWS SDK v2 to v3 incrementally per service by planning and executing service-by-service migrations, which allows you to preserve runtime behavior and configuration while transitioning modularly.

Why do I need to replace AWS.config.update() when migrating to AWS SDK v3?

You need to replace AWS.config.update() when migrating to AWS SDK v3 because v3 enforces explicit client-command patterns, requiring per-service configuration instead of global updates to preserve behavior safely.