Migrate AWS Bedrock to Merge Gateway

Migrate boto3 Bedrock calls to Merge Gateway SDK equivalents.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-aws-bedrock-to-merge-gateway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Migrate AWS Bedrock to Merge Gateway
Source: https://github.com/merge-api/merge-gateway-skills/tree/main/skills/migrate-bedrock
Command: npx skills add https://github.com/merge-api/merge-gateway-skills --skill migrate-aws-bedrock-to-merge-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replace boto3 Bedrock calls with the Merge Gateway SDK to unify and modernize LLM routing, model discovery, and streaming.

Core Features & Use Cases

  • Migrate invoke_model and converse API patterns by translating Bedrock requests to Merge Gateway SDK calls.
  • Map Bedrock model IDs to Gateway provider/model format and migrate streaming of Bedrock events to Gateway streaming.
  • Remove AWS Bedrock-specific logic and environment variables, replacing with MERGE_GATEWAY_API_KEY-based authentication.

Quick Start

Run the migration workflow in your project by calling /migrate-bedrock to begin replacing Bedrock usage with the Merge Gateway SDK.

Frequently Asked Questions about Migrate AWS Bedrock to Merge Gateway

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

FAQPage Schema
How do I migrate AWS Bedrock boto3 calls to a gateway SDK?

You can migrate AWS Bedrock boto3 calls by replacing provider requests with Merge Gateway SDK equivalents, mapping Bedrock model IDs and translating invoke_model or converse API patterns to Gateway calls.

What is the best way to map Bedrock model IDs when switching to Merge Gateway?

Mapping Bedrock model IDs to Gateway provider/model format involves translating your existing Bedrock identifiers into the Merge Gateway SDK's expected provider and model naming structure during migration.

Can I migrate Bedrock streaming events to the Merge Gateway SDK?

Yes, you can migrate Bedrock streaming events to Gateway streaming by replacing AWS Bedrock-specific event handling logic with the Merge Gateway SDK's streaming patterns during the migration workflow.

Do I need a Merge Gateway API key to migrate from AWS Bedrock?

Yes, you need a Merge Gateway API key and an existing project that uses boto3 Bedrock. The migration removes AWS-specific environment variables, replacing them with MERGE_GATEWAY_API_KEY-based authentication.

Does the Merge Gateway SDK migration work with TypeScript and Python projects?

Yes, the migration applies to both Python and TypeScript projects using boto3 Bedrock, covering invoke_model, converse, and streaming patterns to replace request and response formats with Gateway SDK equivalents.