AWS Compute Optimizer now supports 99 additional Amazon Elastic Compute Cloud (Amazon EC2) instance types. These enhancements help you identify additional savings opportunities across your EC2 instances without specialized knowledge or manual analysis. Compute Optimizer has expanded support to include the latest generation Compute Optimized (C8gn, C8gd), General Purpose (M8i, M8i-flex, M8gd), Memory Optimized (R8i, R8i-flex, R8gd), and Storage Optimized (I8ge) instance types. This expansion enables Compute Optimizer to help you take advantage of the price-to-performance improvements offered by the newest instance types. This new feature is available in all AWS Regions where Compute Optimizer is available except the AWS GovCloud (US) and the China Regions. For more information about Compute Optimizer, visit our product page and documentation. You can start using Compute Optimizer through the AWS Management Console, AWS CLI, or AWS SDK.

Today, we are introducing automation rules, a new feature in AWS Compute Optimizer that enables you to optimize Amazon Elastic Block Store (EBS) volumes at scale. With automation rules, you can streamline the process of cleaning up unattached EBS volumes and upgrading volumes to the latest-generation volume types, saving cost and improving performance across your cloud infrastructure. Automation rules let you automatically apply optimization recommendations on a recurring schedule when they match your criteria. You can set criteria like AWS Region to target specific geographies and Resource Tags to distinguish between production and development workloads. Configure rules to run daily, weekly, or monthly, and AWS Compute Optimizer will continuously evaluate new recommendations against your criteria. A new dashboard allows you to summarize automation events over time, examine detailed step history, and estimate savings achieved. If you need to reverse an action, you can do so directly from the same dashboard. AWS Compute Optimizer automation rules are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). To get started, navigate to the new Automation section in the AWS Compute Optimizer console, visit the AWS Compute Optimizer user guide documentation, or read the announcement blog to learn more.

AWS Compute Optimizer now supports 99 additional Amazon Elastic Compute Cloud (Amazon EC2) instance types. These enhancements help you identify additional savings opportunities across your EC2 instances without specialized knowledge or manual analysis. Compute Optimizer has expanded support to include the latest generation Compute Optimized (C8gn, C8gd), General Purpose (M8i, M8i-flex, M8gd), Memory Optimized (R8i, R8i-flex, R8gd), and Storage Optimized (I8ge) instance types. This expansion enables Compute Optimizer to help you take advantage of the price-to-performance improvements offered by the newest instance types. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where Compute Optimizer is available except the AWS GovCloud (US) and the China Regions. For more information about Compute Optimizer, visit our https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ec2-recommendations.html. You can start using Compute Optimizer through the AWS Management Console, AWS CLI, or AWS SDK.

Today, we are introducing automation rules, a new feature in AWS Compute Optimizer that enables you to optimize Amazon Elastic Block Store (EBS) volumes at scale. With automation rules, you can streamline the process of cleaning up unattached EBS volumes and upgrading volumes to the latest-generation volume types, saving cost and improving performance across your cloud infrastructure. Automation rules let you automatically apply optimization recommendations on a recurring schedule when they match your criteria. You can set criteria like AWS Region to target specific geographies and Resource Tags to distinguish between production and development workloads. Configure rules to run daily, weekly, or monthly, and AWS Compute Optimizer will continuously evaluate new recommendations against your criteria. A new dashboard allows you to summarize automation events over time, examine detailed step history, and estimate savings achieved. If you need to reverse an action, you can do so directly from the same dashboard. AWS Compute Optimizer automation rules are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). To get started, navigate to the new Automation section in the AWS Compute Optimizer console, visit the AWS Compute Optimizer https://docs.aws.amazon.com/compute-optimizer/latest/ug/automation.html, or read the https://aws.amazon.com/blogs/aws-cloud-financial-management/introducing-automated-amazon-ebs-volume-optimization-in-aws-compute-optimizer/ to learn more.

AWS Compute Optimizer now includes improved visibility into IOPS and throughput spikes when deliverings Amazon EBS volume rightsizing recommendations. Compute Optimizer analyzes two additional Amazon CloudWatch metrics, VolumeIOPSExceededCheck and VolumeThroughputExceededCheck, which report whether your workload consistently attempted to drive IOPS or throughput beyond your volume's provisioned performance in any given minute. By factoring in these signals, Compute Optimizer helps you make rightsizing decisions to balance cost with performance for workloads that experience bursts of high IOPS or throughput. This enhancement is available in all AWS Regions where AWS Compute Optimizer is available, except the AWS GovCloud (US) Regions, and the China Regions. The underlying CloudWatch metrics are available at no additional charge for all EBS volumes attached to Nitro-based EC2 instances, excluding standard and Multi-Attach enabled volumes. To get started, go to AWS Compute Optimizer in the AWS Management Console. To learn more, visit the AWS Compute Optimizer User Guide.

Today, AWS announces that AWS Compute Optimizer now supports idle resource recommendations for NAT Gateways. With this new recommendation type, you will be able to identify NAT Gateways that are unused, resulting in cost savings. With the new unused NAT Gateway recommendation, you will be able to identify NAT Gateways that show no traffic activity over a 32-day analysis period. Compute Optimizer analyzes CloudWatch metrics including active connection count, incoming packets from source, and incoming packets from destination to validate if NAT Gateways are truly unused. To avoid recommending critical backup resources, Compute Optimizer also examines if the NAT Gateway resource is associated in any AWS Route Tables. You can view the total savings potential of these unused NAT Gateways and access detailed utilization metrics to verify unused conditions before taking action. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Compute Optimizer is available except the AWS GovCloud (US) and the China Regions. To learn more about the new feature updates, please visit Compute Optimizer’s https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html.

AWS Compute Optimizer now detects idle EC2 Auto Scaling groups using G and P instance types, enabling you to identify additional savings opportunities in your AWS spend. As AI development accelerates, organizations are creating more Auto Scaling groups with G and P instance types for training and inference workloads. Once you https://alpha.www.docs.aws.a2z.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-NVIDIA-GPU.html Compute Optimizer analyzes utilization data and identifies groups that have completed jobs and remained idle during your specified lookback period, making it easier to identify and prevent waste on these high-cost instance types. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Compute Optimizer is available except for the AWS GovCloud (US) and the China Regions. The new recommendations will also be available in https://aws.amazon.com/aws-cost-management/cost-optimization-hub/. For more information about Compute Optimizer, visit our https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ec2-recommendations.html. You can start using AWS Compute Optimizer through the AWS Management Console, AWS Services CLI, or AWS SDK.  

Today, AWS announces that AWS Compute Optimizer now supports idle resource recommendations for NAT Gateways. With this new recommendation type, you will be able to identify NAT Gateways that are unused, resulting in cost savings. With the new unused NAT Gateway recommendation, you will be able to identify NAT Gateways that show no traffic activity over a 32-day analysis period. Compute Optimizer analyzes CloudWatch metrics including active connection count, incoming packets from source, and incoming packets from destination to validate if NAT Gateways are truly unused. To avoid recommending critical backup resources, Compute Optimizer also examines if the NAT Gateway resource is associated in any AWS Route Tables. You can view the total savings potential of these unused NAT Gateways and access detailed utilization metrics to verify unused conditions before taking action. This new feature is available in all AWS Regions where AWS Compute Optimizer is available except the AWS GovCloud (US) and the China Regions. To learn more about the new feature updates, please visit Compute Optimizer’s product page and user guide.

AWS Compute Optimizer now provides recommendations for Amazon Aurora DB instances. These recommendations help you identify idle database instances and choose the optimal DB instance class, so you can reduce costs for unused resources and increase the performance of under-provisioned workloads. AWS Compute Optimizer automatically analyzes Amazon CloudWatch metrics such as CPU utilization, network throughput, and database connections to generate recommendations for your DB instances running Amazon Aurora MySQL-Compatible Edition and Aurora PostgreSQL-Compatible Edition engines. If you enable https://aws.amazon.com/rds/performance-insights/ on your DB instances, Compute Optimizer will analyze additional metrics such as DBLoad and out-of-memory counters to give you more insights to choose the optimal DB instance configuration. With this launch, AWS Compute Optimizer now supports recommendations for Amazon RDS for MySQL, Amazon RDS for PostgreSQL, and Amazon Aurora database engines. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Compute Optimizer is available except the AWS GovCloud (US) and the China Regions. To learn more about the new feature updates, please visit Compute Optimizer’s https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html.

AWS Compute Optimizer now detects idle EC2 Auto Scaling groups using G and P instance types, enabling you to identify additional savings opportunities in your AWS spend. As AI development accelerates, organizations are creating more Auto Scaling groups with G and P instance types for training and inference workloads. Once you enable the NVIDIA CloudWatch agent, Compute Optimizer analyzes utilization data and identifies groups that have completed jobs and remained idle during your specified lookback period, making it easier to identify and prevent waste on these high-cost instance types. This new feature is available in all AWS Regions where AWS Compute Optimizer is available except for the AWS GovCloud (US) and the China Regions. The new recommendations will also be available in Cost Optimization Hub. For more information about Compute Optimizer, visit our product page and documentation. You can start using AWS Compute Optimizer through the AWS Management Console, AWS Services CLI, or AWS SDK.

Today, AWS announces that AWS Compute Optimizer now supports recommendations to help you identify idle AWS resources. With this new recommendation type, you will be able to identify resources that are un-used and may be candidates for turning off or deleting, resulting in cost savings. With the new idle resource recommendation, you will be able to identify idle EC2 instances, EC2 Auto Scaling groups, EBS volumes, ECS services running on Fargate, and RDS instances. You can view the total savings potential of stopping or deleting these idle resources. Compute Optimizer analyzes 14 consecutive days of utilization history to validate if resources are idle to provide trustworthy savings opportunities. You can also view idle resource recommendation across all AWS accounts in your organization through the Cost Optimization Hub, with de-duplicated estimated savings with other recommendations on the same resources. For more information about the AWS Regions where Compute Optimizer is available, see https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ table. For more information about Compute Optimizer, visit our https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ec2-recommendations.html. You can start using AWS Compute Optimizer through the AWS Management Console, AWS CLI, and AWS SDK.

みなさんこんにちは杉金ですAWSComputeOptimizerでECインスタンス向けに推奨事項のカスタマイズを行うRightsizingrecommendationpreferencesが追加されま

このブログ記事はMicrosoftSQLServerのライセンスに関する推奨を生成するAWSCom

こんにちはkazです最近電気圧力鍋でモツ煮込み作るのハマってますはじめに以前にComputeOptimizerの組織設定を行い組織アカウントを一元化しましたAWSComputeOptimi

AWS Compute Optimizer now identifies idle resources for Amazon DynamoDB provisioned tables, Amazon ElastiCache (Redis and Valkey), Amazon MemoryDB, Amazon DocumentDB (provisioned and serverless), Amazon WorkSpaces, and Amazon SageMaker endpoints. This expansion enables you to detect unused resources across more of your AWS environment and identify potential cost savings. Compute Optimizer analyzes utilization metrics to determine whether a resource is idle. Customers can set this lookback period based on the nature of their workloads. For each resource type, Compute Optimizer evaluates service-specific signals such as consumed capacity, cache hits, active connections, and CPU utilization. When Compute Optimizer identifies potential idle resources, it surfaces these recommendations, along with detailed utilization metrics and estimated savings in the console, enabling you to evaluate recommendations before acting. You can also view idle resource recommendations across all AWS accounts in your organization through the Cost Optimization Hub, with de-duplicated estimated savings with other recommendations on the same resources. For more information about the AWS Regions where Compute Optimizer is available, see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. For more information about AWS Compute Optimizer, visit our https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ec2-recommendations.html. You can start using AWS Compute Optimizer through the AWS Management Console, AWS CLI, and AWS SDK.

AWS Compute Optimizer now includes improved visibility into IOPS and throughput spikes when deliverings Amazon EBS volume rightsizing recommendations. Compute Optimizer analyzes two additional Amazon CloudWatch metrics, VolumeIOPSExceededCheck and VolumeThroughputExceededCheck, which report whether your workload consistently attempted to drive IOPS or throughput beyond your volume's provisioned performance in any given minute. By factoring in these signals, Compute Optimizer helps you make rightsizing decisions to balance cost with performance for workloads that experience bursts of high IOPS or throughput. This enhancement is available in all AWS Regions where AWS Compute Optimizer is available, except the AWS GovCloud (US) Regions, and the China Regions. The underlying CloudWatch metrics are available at no additional charge for all EBS volumes attached to Nitro-based EC2 instances, excluding standard and Multi-Attach enabled volumes. To get started, go to AWS Compute Optimizer in the AWS Management Console. To learn more, visit the AWS Compute Optimizer https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ebs-recommendations.html.

AWS Compute Optimizer now lets you extend the lookback period of your Amazon EBS volume and Amazon ECS rightsizing recommendations from the default 14 days to 32 days, at no additional cost. A longer lookback period allows Compute Optimizer to account for monthly utilization patterns, such as month-end processing, when generating rightsizing recommendations. This can help you make better optimization decisions for your workload, leading to better cost and performance outcomes. AWS Compute Optimizer supports 32-day lookback periods for five types of recommendations: EC2 instance, EC2 Auto Scaling group, RDS database, EBS volume, and ECS service. You can set the lookback period at the organization, account, or resource level through the console, AWS SDK, or AWS CLI. This feature is available in all AWS Regions where AWS Compute Optimizer is available, except the AWS GovCloud (US) Regions and the China Regions. To learn more, see the AWS Compute Optimizer https://docs.aws.amazon.com/compute-optimizer/latest/ug/rightsizing-preferences.html#rightsizing-preferences-lookback.

AWS Compute Optimizer makes it easier to identify snapshots that are created when snapshotting and deleting unattached Amazon Elastic Block Store (EBS) volumes by automatically applying an AWS-generated tag during creation. This enhancement improves visibility and tracking of EBS snapshots created through Compute Optimizer Automation. When Compute Optimizer creates a snapshot before deleting an unattached EBS volume—whether initiated through manual actions or automation rules—the snapshot now receives the tag aws:compute-optimizer:automation-event-id with a tag value that links the snapshot to the unique identifier of the automation event that created it. This allows you to easily identify, track, and manage snapshots created through the automated optimization process, helping you maintain better governance over your backup resources and understand the source of snapshots in your environment. This is available in all AWS Regions where AWS Compute Optimizer Automation is available. To get started with automated optimization, go to the AWS Compute Optimizer console or visit the https://docs.aws.amazon.com/compute-optimizer/latest/ug/automation.html documentation.

Today, AWS announced the release of a model context protocol (MCP) server for Billing and Cost Management, now available in the https://github.com/awslabs/mcp/tree/main/src/billing-cost-management-mcp-server. The Billing and Cost Management MCP server allows customers to analyze their historical spending, find cost optimization opportunities, and estimate the costs of new workloads using the AI agent or assistant of their choice. Artificial intelligence is transforming the way that customers manage FinOps practices. While customers can access AI-powered cost analysis and optimization capabilities in Amazon Q Developer in the console, the Billing and Cost Management MCP server brings these capabilities to any MCP-compatible AI assistant or agent that customers may be using, such as https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/qdev-mcp.html, the https://kiro.dev/docs/mcp/ IDE, https://code.visualstudio.com/docs/copilot/chat/mcp-servers, or https://support.anthropic.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop. This MCP server gives these clients rich capabilities to analyze historical and forecasted cost and usage data, identify cost optimization opportunities, understand AWS service pricing, find cost anomalies, and more. The MCP server not only provides access to AWS service APIs; it also provides a dedicated SQL-based calculation engine allowing AI assistants to perform reliable, reproducible calculations — ranging from period-over-period changes to unit cost metrics — and easily handle large volumes of cost and usage data. You can download and integrate the open-source server with your preferred MCP-compatible AI assistant. The server connects securely to the AWS Billing and Cost Management services using standard AWS credentials with minimal configuration required. To get started, visit thehttps://github.com/awslabs/mcp/tree/main/src/aws-pricing-mcp-server.

AWS Compute Optimizer now supports 57 additional Amazon Elastic Compute Cloud (Amazon EC2) instance types. The newly supported instance types include the latest generation accelerated computing instances (P5e, P5en, G6e), storage optimized instances (I7ie, I8g), and compute optimized instances (M8g), as well as high memory instances (U7i) and new instance sizes for C7i-flex and M7i-flex. With these newly supported instance types, AWS Compute Optimizer delivers recommendations to help you identify cost and performance optimization opportunities across a wider range of EC2 instance types, helping you improve performance and cost savings for your workloads. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Compute Optimizer is available, except the AWS GovCloud (US) and the China Regions. For more information about Compute Optimizer, visit our https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/view-ec2-recommendations.html. You can start using AWS Compute Optimizer through the AWS Management Console, AWS Services CLI, or AWS SDK.

AWS Compute Optimizer now expands idle and rightsizing recommendations to Amazon EC2 Auto Scaling groups with scaling policies and multiple instance types. With the new recommendations, you can take actions to optimize cost and performance of these groups without requiring specialized knowledge or engineering resources to analyze them. Compute Optimizer analyzes EC2 Auto Scaling groups' scaling policies, instance configurations, and utilization metrics to understand their usage patterns and identify opportunities for cost and performance optimization. For EC2 Auto Scaling groups using multiple instance types, Compute Optimizer helps identify the most cost-efficient instance types, enabling you to prioritize them in your groups. When EC2 Auto Scaling groups use scaling policies to scale based on CPU utilization, Compute Optimizer recommends optimizing the CPU-to-memory ratio by considering only instance types with identical vCPU counts. Compute Optimizer also identifies and flags EC2 Auto Scaling groups that demonstrate consistently low CPU and network usage throughout the lookback period as idle, recommending that you scale them down to save costs. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Compute Optimizer is available, except the AWS GovCloud (US) and AWS China Regions. To learn more about the new feature updates, please visit Compute Optimizer’s https://aws.amazon.com/compute-optimizer/ and https://docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html.

AWS Compute Optimizer now identifies idle resources for Amazon DynamoDB provisioned tables, Amazon ElastiCache (Redis and Valkey), Amazon MemoryDB, Amazon DocumentDB (provisioned and serverless), Amazon WorkSpaces, and Amazon SageMaker endpoints. This expansion enables you to detect unused resources across more of your AWS environment and identify potential cost savings. Compute Optimizer analyzes utilization metrics to determine whether a resource is idle. Customers can set this lookback period based on the nature of their workloads. For each resource type, Compute Optimizer evaluates service-specific signals such as consumed capacity, cache hits, active connections, and CPU utilization. When Compute Optimizer identifies potential idle resources, it surfaces these recommendations, along with detailed utilization metrics and estimated savings in the console, enabling you to evaluate recommendations before acting. You can also view idle resource recommendations across all AWS accounts in your organization through the Cost Optimization Hub, with de-duplicated estimated savings with other recommendations on the same resources. For more information about the AWS Regions where Compute Optimizer is available, see the AWS Region table. For more information about AWS Compute Optimizer, visit our product page and documentation. You can start using AWS Compute Optimizer through the AWS Management Console, AWS CLI, and AWS SDK.

AWS Compute Optimizer now lets you extend the lookback period of your Amazon EBS volume and Amazon ECS rightsizing recommendations from the default 14 days to 32 days, at no additional cost. A longer lookback period allows Compute Optimizer to account for monthly utilization patterns, such as month-end processing, when generating rightsizing recommendations. This can help you make better optimization decisions for your workload, leading to better cost and performance outcomes. AWS Compute Optimizer supports 32-day lookback periods for five types of recommendations: EC2 instance, EC2 Auto Scaling group, RDS database, EBS volume, and ECS service. You can set the lookback period at the organization, account, or resource level through the console, AWS SDK, or AWS CLI. This feature is available in all AWS Regions where AWS Compute Optimizer is available, except the AWS GovCloud (US) Regions and the China Regions. To learn more, see the AWS Compute Optimizer User Guide.

AWS Compute Optimizer makes it easier to identify snapshots that are created when snapshotting and deleting unattached Amazon Elastic Block Store (EBS) volumes by automatically applying an AWS-generated tag during creation. This enhancement improves visibility and tracking of EBS snapshots created through Compute Optimizer Automation. When Compute Optimizer creates a snapshot before deleting an unattached EBS volume—whether initiated through manual actions or automation rules—the snapshot now receives the tag aws:compute-optimizer:automation-event-id with a tag value that links the snapshot to the unique identifier of the automation event that created it. This allows you to easily identify, track, and manage snapshots created through the automated optimization process, helping you maintain better governance over your backup resources and understand the source of snapshots in your environment. This is available in all AWS Regions where AWS Compute Optimizer Automation is available. To get started with automated optimization, go to the AWS Compute Optimizer console or visit the user guide documentation.