canonical: https://jentic.com/apis/amazonaws.com/aws-compute-optimizer # AWS Compute Optimizer 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. ## For AI agents Fetch right-sizing and idle-resource recommendations across EC2, Auto Scaling, EBS, Lambda, ECS-Fargate, and RDS, and export them to S3. ## Scope Does not handle automatic right-sizing actions, billing analysis, or general performance monitoring - use only to fetch right-sizing recommendations and export them. ## Capabilities - 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 - Retrieve effective recommendation preferences for an enrollment status - Update recommendation preferences such as enhanced infrastructure metrics ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Call GetRecommendationSummaries, then GetEC2InstanceRecommendations and GetLambdaFunctionRecommendations, and return the top 20 savings opportunities ranked by estimated monthly impact. ## Key endpoints | 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 | ## Key resources - **EC2InstanceRecommendation** — Retrieve right-sizing recommendations for individual EC2 instances and export them to S3. - **AutoScalingGroupRecommendation** — Recommendations for Auto Scaling group instance types and configurations. - **EBSVolumeRecommendation** — Recommendations for EBS volume type, size, and IOPS configuration. - **LambdaFunctionRecommendation** — Memory-size recommendations for Lambda functions. - **ECSServiceRecommendation** — Right-sizing recommendations for ECS services running on Fargate. - **IdleRecommendation** — Identifies idle resources across supported types via GetIdleRecommendations. - **RecommendationPreferences** — Account- and resource-level preferences such as enhanced infrastructure metrics and savings estimation mode. ## Why Jentic - **Setup:** Wiring AWS Compute Optimizer by hand means signing every request with AWS Signature v4 HMAC, targeting the right regional host like compute-optimizer.{region}.amazonaws.com, and dispatching each operation through the X-Amz-Target header instead of a REST path. Through Jentic you install once, import AWS Compute Optimizer from the API Directory, store the AWS access key and secret once, and your agent calls it. - **Permission scoping:** Compute Optimizer routes operations through the X-Amz-Target header and carries resource ARNs and account filters in the request body, not the URL path, so scoping is by operation. You limit the agent to the operations it needs, such as GetEC2InstanceRecommendations or GetRecommendationSummaries, so export operations like ExportEC2InstanceRecommendations are not included unless you add them. - **Credential handling:** Your AWS access key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find oversized EC2 instances and Lambda functions' or 'list idle resource recommendations', and Jentic returns the matching Compute Optimizer operation with its input schema, so the agent calls the correct endpoint without browsing the AWS service reference. ## Related APIs - **AWS Cost Explorer** — Cost and usage analytics that pair with Compute Optimizer's resource-level recommendations. - **AWS Cost Explorer** — Cost and usage analytics with built-in dashboards. - **AWS Cost and Usage Report** — Detailed billing line items that ground recommendations in actual spend. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the AWS Compute Optimizer API? Yes. Because you run Jentic One yourself, your own rules decide which Compute Optimizer operations and credentials the agent may use, and scoping here is by operation since the API selects each action through the X-Amz-Target header rather than a URL path. You can restrict the agent to read-only calls like GetEC2InstanceRecommendations, GetLambdaFunctionRecommendations, or GetRecommendationSummaries, so write and export actions such as ExportEC2InstanceRecommendations are not available unless you explicitly add them. The AWS access key and secret stay stored on your instance and are injected only when a permitted request is signed.