Amazon Elastic Compute Cloud

Name: Amazon Elastic Compute Cloud API
Brand: Amazon Elastic Compute Cloud
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputehmac1182 EndpointsREST

For Agents

Provision and manage EC2 instances, EBS volumes, AMIs, VPC networking, security groups, and the broad surface of AWS compute and network resources.

Quickstart

Get started with Amazon Elastic Compute Cloud in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"launch an EC2 instance"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Elastic Compute Cloud API.

Launch and terminate EC2 instances with RunInstances and TerminateInstances at the requested instance type and AMI

Manage EBS volumes via CreateVolume, AttachVolume, DetachVolume, and DeleteVolume tied to instances

Define VPC networking with CreateVpc, CreateSubnet, CreateRouteTable, and CreateInternetGateway

Control inbound and outbound traffic through CreateSecurityGroup, AuthorizeSecurityGroupIngress, and RevokeSecurityGroupEgress

GET STARTED

Start building with Amazon Elastic Compute Cloud API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon Elastic Compute Cloud, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Elastic Compute Cloud, keeping it validated and agent-ready. Amazon EC2 provides resizable compute capacity in AWS, and its API is the foundational control plane for EC2 instances, EBS volumes, VPC networking, security groups, and a broad set of related compute primitives. With more than a thousand operations, the API spans instance lifecycle, AMIs, key pairs, networking (VPC, subnets, route tables, NAT, VPN), elastic IP addresses, transit gateways, and capacity reservations. Use it when an agent needs to provision compute, manage networking, or automate any AWS infrastructure-as-API workflow.

Use Cases

Patterns agents use Amazon Elastic Compute Cloud API for, with concrete tasks.

★ Provision a Fleet of Compute Instances

Use RunInstances to launch one or more EC2 instances of a chosen type from an AMI, attach them to a security group, and place them in a target subnet. The same call sets tags, IAM instance profiles, and user data, giving an agent everything needed to bring up workers, application servers, or batch hosts in one structured call.

Call RunInstances with ImageId, InstanceType t3.medium, MinCount 1, MaxCount 1, the chosen SubnetId, and a SecurityGroupIds list, then poll DescribeInstances until State.Name is running.

Stand Up a Production VPC

Compose a production-ready network by chaining CreateVpc, CreateSubnet for each AZ, CreateInternetGateway, CreateRouteTable, CreateNatGateway, and the route association calls. The result is a fully tagged VPC with predictable CIDR layout that workloads can be deployed into without console clicks.

Call CreateVpc with the requested CidrBlock, CreateSubnet for each AZ, CreateInternetGateway, AttachInternetGateway, then CreateRouteTable and CreateRoute to wire up egress.

Lock Down Inbound Access with Security Groups

Tighten access to a workload by replacing broad CIDR allow rules with narrow ones. AuthorizeSecurityGroupIngress adds the permitted port and source CIDR, RevokeSecurityGroupIngress removes outdated rules, and DescribeSecurityGroups gives an audit-friendly view of effective rules per group.

Call AuthorizeSecurityGroupIngress with the GroupId, IpProtocol tcp, FromPort 443, ToPort 443, and the approved CIDR ranges, then DescribeSecurityGroups to verify.

Agent-Driven Infrastructure as API

An AI agent connected via Jentic can interpret a runbook, locate the right EC2 operations, and provision compute and networking changes — launch instances, rotate AMIs, scale Auto Scaling-friendly groups, or rebuild VPC routes — without leaving the conversation. Jentic returns the matching EC2 operation and schema across the 1000+ operation surface so the agent can pick the right call.

Search Jentic for 'launch an EC2 instance', load RunInstances, execute it with the requested InstanceType, ImageId, SubnetId, and SecurityGroupIds, then DescribeInstances until running.

Key Endpoints

1182 endpoints — jentic publishes the only available openapi specification for amazon elastic compute cloud, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#Action=RunInstances

Launch one or more EC2 instances

POST

/#Action=TerminateInstances

Terminate one or more instances

POST

/#Action=DescribeInstances

Describe instances and their state

POST

/#Action=CreateVpc

Create a VPC with a CIDR block

POST

/#Action=CreateSubnet

Create a subnet in a VPC

POST

/#Action=AuthorizeSecurityGroupIngress

Add an inbound rule to a security group

POST

/#Action=AllocateAddress

Allocate an Elastic IP address

POST

/#Action=CreateNatGateway

Create a NAT gateway in a public subnet

POST

/#Action=RunInstances

Launch one or more EC2 instances

POST

/#Action=TerminateInstances

Terminate one or more instances

POST

/#Action=DescribeInstances

Describe instances and their state

POST

/#Action=CreateVpc

Create a VPC with a CIDR block

POST

/#Action=CreateSubnet

Create a subnet in a VPC

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for EC2 are stored encrypted in the Jentic vault. Jentic signs each EC2 request with SigV4 at execution time and the agent only sees scoped, short-lived access — raw access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'launch an EC2 instance' or 'create a security group rule') and Jentic returns the matching EC2 operation from the 1000+ operation surface with its input schema, so the agent can call the right endpoint without browsing AWS documentation.

Time to first call

Direct EC2 integration: 3-7 days for SigV4 signing, query/form encoding, pagination, and selecting the right operation from a very large surface. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon Elastic Block Store

Block-level snapshot APIs for the volumes EC2 attaches.

Choose EBS direct APIs when the agent needs to read or write snapshot blocks rather than manage volumes through EC2.

Complementary

AWS Auto Scaling

Auto Scaling Groups that orchestrate EC2 instance fleets.

Choose Auto Scaling when the agent needs to manage scaling policies and groups rather than launch instances directly.

Alternative

AWS Lambda

Run code without managing instances or VPCs.

Choose Lambda when the workload is short-lived and event-driven, and EC2's instance lifecycle is unnecessary.

FAQs

Specific to using Amazon Elastic Compute Cloud API through Jentic.

Why is there no official OpenAPI spec for Amazon Elastic Compute Cloud?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Elastic Compute Cloud via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon EC2 API use?

EC2 uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in the Jentic vault and are injected into signed requests at execution time, so the agent never sees the raw secret access key.

Can I launch and tag instances in one call?

Yes. RunInstances accepts a TagSpecifications parameter that applies tags to the instance and any volumes created by the launch. There is no need to call CreateTags separately for instances launched this way.

What are the rate limits for the Amazon EC2 API?

EC2 enforces per-account, per-region request limits that vary by operation; describe operations have higher limits than write operations such as RunInstances. Specific numbers are not in the spec; the AWS user guide documents them, and ThrottlingException responses should trigger exponential backoff.

How do I launch an instance through Jentic?

Search Jentic for 'launch an EC2 instance', load RunInstances, then execute it with ImageId, InstanceType, MinCount, MaxCount, SubnetId, and SecurityGroupIds. Run pip install jentic and use the async search and execute pattern.

Does this API include Auto Scaling and Elastic Load Balancing?

No. EC2 covers instances, volumes, AMIs, and VPC networking. Auto Scaling Groups and Elastic Load Balancers live in their own AWS APIs (autoscaling and elasticloadbalancingv2) and require separate operations to manage.