AWS Compute Optimizer

Name: AWS Compute Optimizer API
Brand: AWS Compute Optimizer
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeAWS Signature v4 (HMAC)21 EndpointsREST

For Agents

Fetch right-sizing and idle-resource recommendations across EC2, Auto Scaling, EBS, Lambda, ECS-Fargate, and RDS, and export them to S3.

Quickstart

Get started with AWS Compute Optimizer 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:
"find oversized EC2 instances and Lambda functions"

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

Capabilities

What an agent can do with AWS Compute Optimizer API.

Get right-sizing recommendations for EC2 instances and Auto Scaling groups

Surface oversized or underutilized EBS volumes and Lambda functions

Export recommendation sets to S3 for finance and reporting workflows

Detect idle resources across the account with GetIdleRecommendations

GET STARTED

Start building with AWS Compute Optimizer API

Explore with Jentic

View OpenAPI Document

Use for: I need to find oversized EC2 instances I can downsize, I want to export Lambda right-sizing recommendations to S3, Get the recommendations for a specific Auto Scaling group, List all idle EBS volumes in this account

Not supported: Does not handle automatic right-sizing actions, billing analysis, or general performance monitoring - use only to fetch right-sizing recommendations and export them.

Jentic publishes the only available OpenAPI document for AWS Compute Optimizer, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Compute Optimizer, keeping it validated and agent-ready. AWS Compute Optimizer analyzes utilization metrics from CloudWatch to recommend right-sized configurations for EC2 instances, EC2 Auto Scaling groups, EBS volumes, Lambda functions, ECS services on Fargate, RDS, and idle resources. It quantifies the savings and performance risk of each recommendation and can export full recommendation sets to S3 for downstream analysis. Recommendations are refreshed daily based on at least 14 days of metric history.

Use Cases

Patterns agents use AWS Compute Optimizer API for, with concrete tasks.

★ EC2 Right-Sizing for Cost Reduction

FinOps and platform teams need to identify EC2 instances that are over-provisioned. AWS Compute Optimizer's GetEC2InstanceRecommendations returns recommended instance types ranked by estimated monthly savings and performance risk, based on at least 14 days of CloudWatch metrics. Acting on the top recommendations typically yields 20-40% compute cost reduction.

Call GetEC2InstanceRecommendations for the current account and return the top 10 instances by estimated monthly savings.

Lambda Memory Tuning

Lambda billing scales with allocated memory and duration. AWS Compute Optimizer's GetLambdaFunctionRecommendations recommends a memory size that minimizes cost while keeping latency within risk bounds. Applying the recommendation is a single UpdateFunctionConfiguration call per function.

Call GetLambdaFunctionRecommendations and return the recommended memory size and projected savings for a given function ARN.

Idle Resource Cleanup

Engineering organizations accumulate idle EC2 instances, EBS volumes, and Auto Scaling groups that incur cost without delivering value. AWS Compute Optimizer's GetIdleRecommendations surfaces these resources with confidence-rated idle classifications so they can be stopped, deleted, or scheduled.

Call GetIdleRecommendations and return all resources classified as Idle along with their estimated monthly savings.

Agent-Driven FinOps Reports

An AI agent supporting a FinOps team can pull recommendations across EC2, Auto Scaling, EBS, Lambda, ECS, and RDS in one pass and generate a prioritized savings plan. Through Jentic, each operation is one structured call - no boto3 setup or pagination boilerplate.

Call GetRecommendationSummaries, then GetEC2InstanceRecommendations and GetLambdaFunctionRecommendations, and return the top 20 savings opportunities ranked by estimated monthly impact.

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for aws compute optimizer, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=ComputeOptimizerService.GetEC2InstanceRecommendations

Get right-sizing recommendations for EC2 instances

POST

/#X-Amz-Target=ComputeOptimizerService.GetAutoScalingGroupRecommendations

Get recommendations for Auto Scaling groups

POST

/#X-Amz-Target=ComputeOptimizerService.GetLambdaFunctionRecommendations

Get memory-size recommendations for Lambda

POST

/#X-Amz-Target=ComputeOptimizerService.GetEBSVolumeRecommendations

Get recommendations for EBS volumes

POST

/#X-Amz-Target=ComputeOptimizerService.GetIdleRecommendations

List idle resource recommendations

POST

/#X-Amz-Target=ComputeOptimizerService.ExportEC2InstanceRecommendations

Export EC2 recommendations to S3

POST

/#X-Amz-Target=ComputeOptimizerService.GetRecommendationSummaries

Summarize recommendations across resource types

POST

/#X-Amz-Target=ComputeOptimizerService.GetEC2InstanceRecommendations

Get right-sizing recommendations for EC2 instances

POST

/#X-Amz-Target=ComputeOptimizerService.GetAutoScalingGroupRecommendations

Get recommendations for Auto Scaling groups

POST

/#X-Amz-Target=ComputeOptimizerService.GetLambdaFunctionRecommendations

Get memory-size recommendations for Lambda

POST

/#X-Amz-Target=ComputeOptimizerService.GetEBSVolumeRecommendations

Get recommendations for EBS volumes

POST

/#X-Amz-Target=ComputeOptimizerService.GetIdleRecommendations

List idle resource recommendations

Why though Jentic?

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

Credential isolation

AWS SigV4 (HMAC) credentials for the AWS Compute Optimizer are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access via Jentic's MAXsystem rather than holding the raw AWS access key ID and secret access key in their context.

Intent-based discovery

Agents search Jentic with intents like 'find oversized EC2 instances and Lambda functions' and Jentic returns the matching AWS Compute Optimizer operation with its input schema, so the agent can call the correct endpoint without browsing the AWS service reference.

Time to first call

Direct integration: 2-4 days for SigV4 request signing, IAM policy setup, and error handling across AWS Compute Optimizer operations. Through Jentic: under 1 hour - search by intent, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Cost Explorer

Cost and usage analytics that pair with Compute Optimizer's resource-level recommendations.

Use Cost Explorer for spend trends and forecasts; use Compute Optimizer for resource-level right-sizing actions.

Alternative

AWS Cost Explorer

Cost and usage analytics with built-in dashboards.

Choose Cost Explorer for cost trends and forecasts to complement Compute Optimizer's right-sizing actions.

Complementary

AWS Cost and Usage Report

Detailed billing line items that ground recommendations in actual spend.

Pair CUR with Compute Optimizer to validate the realized savings from acting on recommendations.

FAQs

Specific to using AWS Compute Optimizer API through Jentic.

Why is there no official OpenAPI spec for AWS Compute Optimizer?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Compute Optimizer 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 AWS Compute Optimizer API use?

AWS Signature v4 (HMAC) with IAM permissions on compute-optimizer:Get* and compute-optimizer:Export* actions. Jentic isolates the AWS credentials and signs each request from its vault.

Can I get Lambda memory recommendations with the AWS Compute Optimizer API?

Yes. GetLambdaFunctionRecommendations returns one or more memory-size options per function, with estimated cost savings and a performance risk rating. Recommendations require at least 14 days of CloudWatch invocation metrics.

What are the rate limits for the AWS Compute Optimizer API?

Per-account, per-region TPS limits apply to all Get* operations. Use ExportEC2InstanceRecommendations and similar export operations to fetch large recommendation sets without paginating thousands of Get calls.

How do I export right-sizing recommendations through Jentic?

Search Jentic for 'export EC2 right-sizing recommendations to S3', load the ExportEC2InstanceRecommendations schema, and execute it with the destination S3 bucket and object key. Compute Optimizer writes the CSV file and returns the job ID.

Is the AWS Compute Optimizer API free?

The basic recommendations are free. Enhanced infrastructure metrics for EC2 require an opt-in and incur a small per-resource monthly charge. Export operations are free aside from S3 storage of the output.