Skip to content
MCP-Bridge
Cloud InfrastructureNo Auth RequiredAuto OpenAPIQuality Score: 40/99

AWS EC2 Instance Connect MCP Server Integration Guide

Section A: Quick Answer & Architectural Summary

The AWS EC2 Instance Connect Model Context Protocol (MCP) integration bridges AI coding assistants to the AWS EC2 Instance Connect cloud infrastructure API. It exposes 2 validated endpoint operations as callable tools for Claude Desktop, Cursor, and VS Code. Configuration is managed via hosted registry at /config/amazonaws-com-ec2-instance-connect.json or local stdio bridge execution. Operates with zero authentication credentials out of the box. Contains 2 mutating operations (POST/PUT/DELETE); user confirmation is recommended before triggering write operations.

Core Functionality:AWS EC2 Instance Connect exposes 2 OpenAPI operations as callable MCP tools for AI assistants.
Quick Install:Add hosted configuration URL "/config/amazonaws-com-ec2-instance-connect.json" to your MCP client or use the configuration generator.
Authentication:No authentication required.
Operational Caveat:Contains 2 mutating operations (POST/PUT/DELETE); user confirmation is recommended before triggering write operations.
Section B: Editorial Evaluation

MCPBridge Editorial Verdict: AWS EC2 Instance Connect

8 Standardized Dimensions
1. Best For

AI coding workflows requiring programmatic access to AWS EC2 Instance Connect (Cloud Infrastructure) endpoints

2. Experience LevelBeginner
3. Setup Difficulty

Low (1-2 mins)

4. Authentication

Zero Authentication Required

5. Maintenance Status

Automated Spec Tracking

6. Compatibility

Claude Desktop, Cursor IDE, VS Code (Cline), Zed Editor

7. Security Profile

Read & Mutating endpoints; client confirmation and least-privilege token recommended

8. MCPBridge Verdict Summary

MCPBridge rates AWS EC2 Instance Connect as a standardized OpenAPI-to-MCP bridge providing structured tool definitions across 2 endpoints.

Technical Overview & Protocol Integration

Amazon EC2 Instance Connect, provided by Amazon Web Services (AWS), is a managed service designed to simplify and secure SSH and serial console access to Amazon Elastic Compute Cloud (EC2) instances. Its core capability revolves around the secure, one-time use of SSH public keys. Instead of users managing persistent SSH keys and manually distributing them across instances, system administrators can use this API to publish ephemeral, short-lived public keys to the instance metadata. This establishes a secure, just-in-time access model where credentials are valid only for the duration required for a connection session, typically 60 seconds. The primary enterprise use cases include providing secure, auditable access for developers and DevOps engineers to troubleshoot instances, enabling automated systems and CI/CD pipelines to perform secure deployment or management tasks without long-lived credentials, and facilitating compliance with security standards by minimizing the attack surface associated with persistent SSH keys on instances.

When this API is exposed as a set of tools to an AI coding assistant through the Model Context Protocol (MCP), it unlocks significant value for automating and securing infrastructure workflows. An AI agent, operating within a developer's IDE or a chat interface, gains the ability to directly orchestrate secure instance access as part of higher-level tasks. For example, instead of the developer manually generating a temporary key pair and calling the AWS CLI, they can instruct the AI to "securely connect to the production web server instance i-1234567890abcdef0 to check the application logs." The AI, via the MCP server, can then execute the workflow: generate a fresh, one-time SSH key pair locally, use the SendSSHPublicKey tool to push the public key to the specified instance, and provide the temporary private key or connection command back to the user or an integrated SSH client. This integration transforms instance access from a manual, error-prone step into a secure, tool-driven operation embedded within natural language instructions.

Practical workflow examples demonstrate the dynamic tasks an AI agent can perform. A developer could instruct: "Help me deploy a configuration change to all instances tagged with 'Environment: staging'." The AI agent could, in sequence, query AWS to list the target instances, then use the EC2 Instance Connect API to establish a secure, temporary connection to each instance one by one, execute the necessary configuration management commands (like applying a new config file via SCP or running a script), and report back on the success or failure for each instance. Another example is automated diagnostics: "The monitoring system is alerting on high CPU on instance i-... . Connect to it and gather a snapshot of running processes and network connections." The AI would initiate a temporary connection, run diagnostic commands like top -bn1 and ss -tuln, and return the structured output for analysis, all without the developer needing to handle or store any sensitive credentials on their local machine.

Crucially, while the API itself does not require direct authentication at the endpoint level (as the SendSSHPublicKey action is authenticated via the caller's IAM permissions), a robust security posture is mandatory. The IAM entity (user, role, or assumed role) invoking the API must have explicit permissions for the ec2-instance-connect:SendSSHPublicKey action, scoped to the specific instance IDs or tags using resource constraints, adhering to the principle of least privilege. Developers must ensure the EC2 instances are configured with the required IAM role (EC2InstanceConnect) or have the EC2 Instance Connect agent installed and configured. Best practices include enforcing tag-based policies for access control, logging all API calls via AWS CloudTrail for audit purposes, and integrating this tool-based access with broader identity governance systems. The temporary nature of the keys is a primary security feature, but it must be complemented by proper network controls (like Security Groups) and instance-level hardening to ensure a comprehensive defense-in-depth strategy.

By translating the OpenAPI 3.0 specification for AWS EC2 Instance Connect into native Model Context Protocol (MCP) tool definitions, developers and AI agents gain programmatic access to endpoints over stdio or HTTP transports. Every endpoint is translated into a discrete tool payload complete with input argument validation, parameter descriptions, and return type definitions.

2. Technical Specifications Matrix

System Specifications

API NameAWS EC2 Instance Connect
Slug Identifieramazonaws-com-ec2-instance-connect
CategoryCloud Infrastructure
Auth MethodNone Required
Endpoint Count2 tools mapped
Spec VersionOpenAPI v2018-04-02
Transport TypeSTDIO
Publisher Sourceauto

Developer Resources

Hosted Config JSON Registry URL→Claude Desktop Config Guide→Upstream API Docs

3. Multi-Client Installation Matrix

Copy and paste these pre-formatted JSON snippets into your MCP client configuration files.

Claude Desktop

Add to claude_desktop_config.json

{
  "mcpServers": {
    "amazonaws-com-ec2-instance-connect": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-openapi",
        "https://api.apis.guru/v2/specs/amazonaws.com/ec2-instance-connect/2018-04-02/openapi.json"
      ],
      "env": {
        "AWS_EC2_INSTANCE_CONNECT_API_KEY": "your_aws_ec2_instance_connect_api_key"
      }
    }
  }
}
Deep link

Cursor IDE

Settings → MCP Servers → Add Hosted Config

{
  "mcpServers": {
    "amazonaws-com-ec2-instance-connect": {
      "url": "https://mcpbridge.org/config/amazonaws-com-ec2-instance-connect.json"
    }
  }
}

Saves as .cursor/mcp.json in the download. Move it to your project root.

Deep link install →

VS Code / Cline

Use with MCP extension config

{
  "mcpServers": {
    "amazonaws-com-ec2-instance-connect": {
      "url": "https://mcpbridge.org/config/amazonaws-com-ec2-instance-connect.json"
    }
  }
}

4. Security Architecture & Credentials Reference

Key parameters and credential variable mappings for AWS EC2 Instance Connect.

Section G: Security Architecture

Security Considerations & Sandbox Guidance: AWS EC2 Instance Connect

Authorization credential isolation, least privilege boundaries, and container sandboxing options.

Credentials Handling

None Required

Permission Scope

Read & Mutating Operations

Execution Boundary

Local MCP bridge process making outbound HTTPS requests to upstream API

🔒

Isolation & Principle of Least Privilege

Ensure outbound network access to the API endpoint is permitted. Use restricted API tokens with minimal read/write scopes.

Actionable Operational Guidelines

  • Verify network firewall rules allow outbound traffic to upstream API endpoints.
  • Review arguments for mutating endpoints (/#X-Amz-Target=AWSEC2InstanceConnectService.SendSSHPublicKey, /#X-Amz-Target=AWSEC2InstanceConnectService.SendSerialConsoleSSHPublicKey) before execution.
  • Apply token rate limits and monitor usage in your provider dashboard to prevent unexpected quota consumption.
Variable NameRequiredExample Value
AWS_EC2_INSTANCE_CONNECT_API_KEYREQUIREDyour_aws_ec2_instance_connect_api_key

5. Endpoints & Tool Schemas Matrix

Search and inspect the 2 tool signatures mapped from OpenAPI.

Executable Code Integration Examples

Call AWS EC2 Instance Connect endpoints via cURL, TypeScript, or Python REST SDKs.

curl -X POST "https://api.apis.guru/v2/specs/amazonaws.com/ec2-instance-connect/2018-04-02/#X-Amz-Target=AWSEC2InstanceConnectService.SendSSHPublicKey" \
  -H "Content-Type: application/json" \
  # No auth required
Section C: Developer Workflows

Concrete Real-World Use Cases for AWS EC2 Instance Connect

Practical multi-step agentic workflows and prompt directives demonstrating concrete developer outcomes.

WorkflowWorkflow 01

Automated Contextual Workflow Integration

Practical workflow examples demonstrate the dynamic tasks an AI agent can perform. A developer could instruct: "Help me deploy a configuration change to all instances tagged with 'Environment: staging'." The AI agent could, in sequence, query AWS to list the target instances, then use the EC2 Instance Connect API to establish a secure, temporary connection to each instance one by one, execute the necessary configuration management commands (like applying a new config file via SCP or running a script), and report back on the success or failure for each instance. Another example is automated diagnostics: "The monitoring system is alerting on high CPU on instance i-... . Connect to it and gather a snapshot of running processes and network connections." The AI would initiate a temporary connection, run diagnostic commands like `top -bn1` and `ss -tuln`, and return the structured output for analysis, all without the developer needing to handle or store any sensitive credentials on their local machine.

Execution Steps:
  1. AI assistant inspects prompt context and selects relevant tool
  2. Validates parameter payload against OpenAPI JSON Schema
  3. Executes tool call and formats structured API response
"Query AWS EC2 Instance Connect for resources matching current task parameters and summarize findings."
State MutationWorkflow 02

Automated Mutation & Resource Creation

Execute state changes and create records through POST operations like "/#X-Amz-Target=AWSEC2InstanceConnectService.SendSSHPublicKey" with parameter validation.

Execution Steps:
  1. Agent constructs validated request body matching schema
  2. Prompts user for execution confirmation
  3. Executes tool and confirms response status
"Prepare a POST request for /#X-Amz-Target=AWSEC2InstanceConnectService.SendSSHPublicKey on AWS EC2 Instance Connect and display the payload for confirmation."
Section D: Project Suitability

Good Fit vs. Poor Fit Criteria for AWS EC2 Instance Connect

Architectural guidelines to determine when to adopt this integration and when to explore alternatives.

✓

When to Choose / Good Fit

  • AI coding assistants in Claude Desktop or Cursor requiring structured tool access to AWS EC2 Instance Connect.
  • Developers who want standardized OpenAPI-to-MCP translation without building custom server code.
  • Workflows that benefit from automated parameter validation against official OpenAPI 3.0 schemas.
  • Teams seeking zero-maintenance hosted JSON configurations for easy distribution.
✕

When to Avoid / Poor Fit

  • Ultra-high frequency data ingestion exceeding typical LLM context windows and token rate limits.
  • Unattended autonomous agent loops with write access where human approval of mutations is mandatory.
  • Environments lacking outbound internet access to upstream AWS EC2 Instance Connect API servers.
Section E: Trust Architecture

Verification & Evidence Audit: AWS EC2 Instance Connect

Tier: Automated Metadata CheckReview Protocol →

OpenAPI 3.0 specification parsed and validated via automated build pipeline.

Last Verified:
Verification Source: OpenAPI 3.0 Specification

Independent Evidence Checks

OpenAPI 3.0 Schema Validationverified

Valid specification version 2018-04-02 with 2 endpoints indexed.

Authentication Modelchecked

No authentication required.

Tool Call Argument Validationverified

JSON Schemas mapped to MCP tools/call standard format.

Runtime Execution Statuschecked

Automated schema validation only; live upstream API calls require developer credentials.

Section F: Health & Maintenance

Project Health & Maintenance Audit: AWS EC2 Instance Connect

lightningActive
Quality Score Index
90
★ Tier-One Quality Grade

Activity & Cadence

Commit VelocityTracked against upstream OpenAPI schema
Release CadenceOpenAPI Version: 2018-04-02
Project LicenseProprietary API / OpenAPI Spec

Transparent Quality Score Breakdown

✓Automated specification tracking (+12 pts)
✓Documentation URL available (+12 pts)
✓OpenAPI 3.0 specification available (+8 pts)
✓2 endpoint schemas (+8 pts)
Score Validation Criteria
✓Auto-generated specification (+12 pts)
✓Documentation URL available (+12 pts)
✓OpenAPI 3.0 specification available (+8 pts)
✓2 endpoint schemas (+8 pts)
Section H: Peer Comparison

Alternatives & Comparison Table (Cloud Infrastructure)

Comparative trade-offs between AWS EC2 Instance Connect and similar ecosystem tools in the Cloud Infrastructure category.

OptionBest ForMain Difference vs. AWS EC2 Instance ConnectSetup / RuntimeExplore
Access AnalyzerDevelopers needing Cloud Infrastructure operations with 10 tools10 endpoints vs 2 endpointsauto / v2019-11-01View →
ADHybridHealthServiceDevelopers needing Cloud Infrastructure operations with 10 tools10 endpoints vs 2 endpointsauto / v2014-01-01View →
AdvisorManagementClientDevelopers needing Cloud Infrastructure operations with 9 tools9 endpoints vs 2 endpointsauto / v2016-07-12-previewView →

9. Error Resolution & Troubleshooting Guide

Contextual diagnostics for HTTP status codes and JSON-RPC tool bridge operations.

-32600 (Invalid Request)

Root Cause: Malformed JSON-RPC payload sent to local MCP bridge process.

Resolution Action: Verify MCP client payload adheres to JSON-RPC 2.0 specification.

-32601 (Method Not Found)

Root Cause: Requested operation does not exist in mapped AWS EC2 Instance Connect OpenAPI endpoint schemas.

Resolution Action: Inspect Section 5 endpoints table to confirm valid method names and paths.

-32602 (Invalid Params)

Root Cause: Missing or invalid parameters for target tool operation.

Resolution Action: Check parameter data types against OpenAPI JSON Schema specification.

429 Rate Limit Exceeded

Root Cause: Upstream AWS EC2 Instance Connect API request rate limit quota reached.

Resolution Action: Implement exponential backoff in tool execution loop or verify provider plan quotas.

OPENAPI_GATEWAY_TIMEOUT

Root Cause: Upstream AWS EC2 Instance Connect endpoint response latency exceeded timeout threshold.

Resolution Action: Verify network connectivity and check provider system status dashboard.

Section I: Authority & References

Official Verified Sources for AWS EC2 Instance Connect

Authoritative upstream repositories, specifications, package registries, and configuration endpoints.

📖

Official Upstream Documentation

Official developer documentation and API reference for AWS EC2 Instance Connect.

https://docs.aws.amazon.com/ec2-instance-connect/
📐

OpenAPI 3.0 Specification

Machine-readable OpenAPI schema source used for MCP tool mapping.

https://api.apis.guru/v2/specs/amazonaws.com/ec2-instance-connect/2018-04-02/openapi.json
⚙️

Hosted MCPBridge Configuration

Pre-generated Model Context Protocol JSON configuration hosted on MCPBridge.

https://mcpbridge.org/config/amazonaws-com-ec2-instance-connect.json
⚙️

OpenAPI-to-MCP Converter Tool

Client-side browser converter to customize or filter endpoint tools.

https://mcpbridge.org/convert/
🛡️

Claim & Maintainer Verification

Submit a claim to verify API publisher ownership and update metadata.

https://github.com/stormlive-ai/mcp-bridge-docs/issues/new?title=Claim+Listing%3A+AWS+EC2+Instance+Connect+%28api%3A+amazonaws-com-ec2-instance-connect%29&labels=claim-listing&body=%23%23+Claim+Listing+Request%0A%0AI+would+like+to+claim+this+listing%3A%0A%0A-+**Type%3A**+api%0A-+**ID%3A**+amazonaws-com-ec2-instance-connect%0A-+**Name%3A**+AWS+EC2+Instance+Connect%0A%0A%23%23%23+Your+Information%0A%0A**GitHub+Handle%3A**+%3C%21--+your+GitHub+username+--%3E%0A%0A**Email%3A**+%3C%21--+optional%2C+for+verification+--%3E%0A%0A**Relationship+to+this+API%3A**%0A-+%5B+%5D+I+am+the+API+provider+%2F+maintainer%0A-+%5B+%5D+I+am+an+authorized+representative%0A-+%5B+%5D+Other%3A%0A%0A%23%23%23+Verification+Method%0A-+%5B+%5D+I+will+add+a+CNAME%2FTXT+record+to+verify+domain+ownership%0A-+%5B+%5D+I+can+confirm+from+an+email+address+at+the+provider+domain%0A-+%5B+%5D+I+maintain+the+GitHub+repository%0A%0A%23%23%23+Updates+I%27d+Like+to+Make+%28optional%29%0A%3C%21--+What+would+you+like+to+update%3F+Description%2C+links%2C+category%2C+etc.+--%3E%0A%0A---%0A*Submitted+via+MCP-Bridge+claim+form*
Section J: Technical FAQ

Frequently Asked Technical Questions: AWS EC2 Instance Connect

Targeted developer questions regarding installation, client configuration, credentials, and error resolution.

The AWS EC2 Instance Connect MCP server connects AI coding assistants (Claude Desktop, Cursor, VS Code, Zed) to the AWS EC2 Instance Connect API using the Model Context Protocol. It converts 2 OpenAPI operations into native MCP tools callable during chat sessions.

← Back to Directory

Related MCP Server Integrations

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →

ADHybridHealthService MCP Setup

The ADHybridHealthService REST API suite, provided by Microsoft as part of the Azure resource provider ecosystem, is the fundamental programmatic interface for managing and querying Azure AD Connect Health. It serves as the command plane for monitoring the health, performance, and configuration of hybrid identity environments that rely on Azure AD Connect to synchronize on-premises Active Directory with Azure Active Directory (now Microsoft Entra ID). Its core capabilities encompass the entire lifecycle of monitoring for these hybrid services. Developers and administrators can use these endpoints to programmatically list, register, and configure health monitoring for their Active Directory Domain Services (AD DS) deployments; retrieve comprehensive health metrics including service status, domain membership, and replication data; access real-time and historical alert data for proactive issue detection; and inspect service configurations to ensure alignment with best practices. Typical enterprise use cases include automating the provisioning and decommissioning of health monitors for large-scale AD DS environments, integrating health telemetry into centralized operational dashboards, triggering automated remediation workflows based on alert data, and conducting detailed audits of hybrid identity infrastructure health and configuration compliance.

Cloud InfrastructureConfigure →

AdvisorManagementClient MCP Setup

The AdvisorManagementClient API, provided by Microsoft Azure, serves as a comprehensive programmatic interface to the Azure Advisor service. This service is a personalized cloud consultant that continuously analyzes your resource configurations and usage patterns to provide actionable recommendations for optimizing your Azure deployments. The core capabilities of this API extend beyond simple querying; it allows enterprises to programmatically generate new recommendation snapshots on-demand, retrieve detailed advice across critical pillars—such as Reliability, Security, Performance, Cost, and Operational Excellence—and manage the lifecycle of recommendation suppressions. Typical use cases include cloud platform teams automating the retrieval of performance bottleneck alerts for high-priority applications, security operations centers programmatically acknowledging and suppressing known, risk-accepted findings to reduce alert fatigue, and finance departments automating the collection of cost optimization recommendations to feed into reporting dashboards. It is an essential tool for any organization practicing Infrastructure as Code (IaC) or FinOps, enabling them to integrate Azure's native optimization insights directly into their management pipelines.

Cloud InfrastructureConfigure →

Amazon API Gateway MCP Setup

Amazon API Gateway is a fully managed service provided by Amazon Web Services (AWS) that enables developers to create, publish, maintain, monitor, and secure APIs at any scale. At its core, the service acts as a front-door for applications to access backend data, business logic, or functionality from your back-end services, such as workloads running on Amazon EC2, code running on AWS Lambda, or any web application. The API facilitates the creation of RESTful APIs and HTTP APIs, offering features like traffic management, authorization and access control, monitoring, and API version management. Enterprise use cases typically involve building scalable microservices architectures, creating unified APIs for diverse mobile and web clients, securely exposing internal business capabilities to partners or public consumers, and implementing intricate request routing and transformation logic. For instance, a company might use API Gateway to orchestrate a single endpoint that interacts with multiple downstream services—a Lambda function for user authentication, a DynamoDB table for data storage, and an EC2-hosted legacy system—to serve a modern mobile application, all while handling throttling, caching, and API key management centrally.

Cloud InfrastructureConfigure →

Amazon AppConfig MCP Setup

Amazon AppConfig, a capability of AWS Systems Manager, provides a fully managed service that enables developers to create, manage, and safely deploy application configurations. Its core purpose is to decouple configuration data from code, allowing for dynamic changes without requiring redeployment of application binaries. The API facilitates the definition of application configurations, environments (such as "dev," "staging," and "prod"), and deployment strategies that control the rollout pace and error thresholds. Key enterprise use cases include feature flagging to enable or disable features for specific user segments, operational tuning (like adjusting concurrency limits or timeouts), A/B testing by directing traffic to different configuration variants, and rapid, safe rollback of configuration changes in response to incidents. The service's built-in validation checks and monitoring ensure configuration integrity and observability across the deployment lifecycle.

Cloud InfrastructureConfigure →
← Back to Cloud Infrastructure Directory