Trending

#CloudFinancialManagement

Latest posts tagged with #CloudFinancialManagement on Bluesky

Latest Top
Trending

Posts tagged #CloudFinancialManagement

Enhanced Transactions view now available in AWS Billing Console AWS announces significant improvements to the Transactions view in the AWS Billing and Cost Management Console’s Payments page, delivering faster performance, simplified payment reconciliation, and improved data accuracy. The enhanced view provides customers with a unified interface to manage all their financial transactions, improving visibility and reducing the time spent on payment tracking. The enhanced view delivers improved performance, with pages loading in mili seconds instead of minutes. Even customers with tens of thousands of transactions can now access their complete transaction history without timeouts. The enhanced view introduces new capabilities including comprehensive balance tracking, clear transaction status indicators, and advanced filtering options. Key improvements include consolidated visibility into invoice statuses, clear +/- indicators for amounts owed versus funds available, and the ability to view records in a single view without performance impact. For organizations using https://aws.amazon.com/blogs/aws/new-aws-billing-transfer-for-centrally-managing-aws-billing-and-costs-across-multiple-organizations/, the new "Usage Consolidation Account" column makes it easier to track transactions across multiple accounts. This feature was made available to all customers on January 12, 2026, in all AWS commercial regions. To learn more about managing your transactions, visit the https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/view-payment-info.html For additional information about managing your AWS payments and billing, see the https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-what-is.html.

Enhanced Transactions view now available in AWS Billing Console

AWS announces significant improvements to the Transactions view in the AWS Billing and Cost Management Console’s Payments page, delivering faster performance, simplified payment reconciliation, an...

#AWS #CloudFinancialManagement

0 0 0 0
Preview
Enhanced Transactions view now available in AWS Billing Console AWS announces significant improvements to the Transactions view in the AWS Billing and Cost Management Console’s Payments page, delivering faster performance, simplified payment reconciliation, and improved data accuracy. The enhanced view provides customers with a unified interface to manage all their financial transactions, improving visibility and reducing the time spent on payment tracking. The enhanced view delivers improved performance, with pages loading in mili seconds instead of minutes. Even customers with tens of thousands of transactions can now access their complete transaction history without timeouts. The enhanced view introduces new capabilities including comprehensive balance tracking, clear transaction status indicators, and advanced filtering options. Key improvements include consolidated visibility into invoice statuses, clear +/- indicators for amounts owed versus funds available, and the ability to view records in a single view without performance impact. For organizations using Billing Transfer, the new "Usage Consolidation Account" column makes it easier to track transactions across multiple accounts. This feature was made available to all customers on January 12, 2026, in all AWS commercial regions. To learn more about managing your transactions, visit the AWS Billing and Cost Management documentation. For additional information about managing your AWS payments and billing, see the AWS Billing Console User Guide.

🆕 AWS enhances Billing Console's Transactions view with faster performance, simplified reconciliation, and improved accuracy. Available Jan 12, 2026, it offers unified financial management, faster load times, and advanced filtering. For more, see AWS documentation.

#AWS #CloudFinancialManagement

0 0 0 0
AWS announces enhanced custom line item controls for AWS Billing Conductor Starting today, AWS Billing Conductor customers gain greater flexibility when using custom line items. Customers can now create service-specific custom line items scoped at either one AWS service or to a set of selected AWS service and can choose how these line items are presented in the pro forma billing artifacts, such as Bills Page, Cost Explorer and Cost and Usage Records. These enhancements enable customers to create more precise and tailored charge-back and re-billing strategies that better reflect their pricing structures and improve the traceability experience for pro forma users. Customers can use this functionality to apply percentage discounts on Saving Plans fees or allocate shared flat support charges under AWS Support service. Service specific custom line items are available for standard billing group regardless of the type of pricing plan selected, and for billing-transfer billing groups exclusively when customer-managed pricing plans are selected. To start, use AWS Billing Conductor console or APIs, create a custom line item and specify the cost reference value (one or multiple AWS services) and the display setting options (itemized or consolidated under your service of choice). To learn more about custom line items visit https://docs.aws.amazon.com/billingconductor/latest/userguide/what-is-billingconductor.html. This feature is available now in all AWS commercial Regions, excluding AWS China (Beijing) Region, operated by Sinnet, and AWS China (Ningxia) Region, operated by NWCD.

AWS announces enhanced custom line item controls for AWS Billing Conductor

Starting today, AWS Billing Conductor customers gain greater flexibility when using custom line items.

Customers can now create service-specific custom line items sc...

#AWS #CloudFinancialManagement #AwsCostExplorer

0 0 0 0
Preview
AWS announces enhanced custom line item controls for AWS Billing Conductor Starting today, AWS Billing Conductor customers gain greater flexibility when using custom line items. Customers can now create service-specific custom line items scoped at either one AWS service or to a set of selected AWS service and can choose how these line items are presented in the pro forma billing artifacts, such as Bills Page, Cost Explorer and Cost and Usage Records. These enhancements enable customers to create more precise and tailored charge-back and re-billing strategies that better reflect their pricing structures and improve the traceability experience for pro forma users. Customers can use this functionality to apply percentage discounts on Saving Plans fees or allocate shared flat support charges under AWS Support service. Service specific custom line items are available for standard billing group regardless of the type of pricing plan selected, and for billing-transfer billing groups exclusively when customer-managed pricing plans are selected. To start, use AWS Billing Conductor console or APIs, create a custom line item and specify the cost reference value (one or multiple AWS services) and the display setting options (itemized or consolidated under your service of choice). To learn more about custom line items visit AWS Billing Conductor documentation. This feature is available now in all AWS commercial Regions, excluding AWS China (Beijing) Region, operated by Sinnet, and AWS China (Ningxia) Region, operated by NWCD.

🆕 AWS Billing Conductor now lets you create custom line items for precise charge-backs, applying discounts and support charges. Available globally except AWS China, it enhances traceability. Use the console or APIs to manage these items.

#AWS #CloudFinancialManagement #AwsCostExplorer

0 0 0 0
AWS reduces publishing time for Carbon Footprint Data to 21 days or Less AWS is now publishing your carbon footprint data in 21 days or less. Previously, the carbon footprint data was published with up to a three month data lag. Now, you have access to your carbon footprint data with estimates published between the 15th and the 21st of the month following your usage. With carbon footprint data available sooner, you have the insights needed to make more timely decisions about how and where your applications are running and identify opportunities to reduce emissions and costs through improved resource efficiency. Also, the CCFT dashboard maintains 38 months of data so you can view your carbon usage trends over time. To view your carbon footprint data, navigate to your carbon emissions data through the https://us-east-1.console.aws.amazon.com/costmanagement/home?region=us-east-1#/customer-carbon-footprint-tool. For more information about CCFT visit the https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/ccft-overview.html page, review the https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/what-is-ccft.html, and learn more by visiting the https://aws.amazon.com/sustainability/tools/aws-customer-carbon-footprint-tool/.

AWS reduces publishing time for Carbon Footprint Data to 21 days or Less

AWS is now publishing your carbon footprint data in 21 days or less. Previously, the carbon footprint data was published with up to a three month data lag. Now, you have access to your carb...

#AWS #CloudFinancialManagement

0 0 0 0
Preview
AWS reduces publishing time for Carbon Footprint Data to 21 days or Less AWS is now publishing your carbon footprint data in 21 days or less. Previously, the carbon footprint data was published with up to a three month data lag. Now, you have access to your carbon footprint data with estimates published between the 15th and the 21st of the month following your usage. With carbon footprint data available sooner, you have the insights needed to make more timely decisions about how and where your applications are running and identify opportunities to reduce emissions and costs through improved resource efficiency. Also, the CCFT dashboard maintains 38 months of data so you can view your carbon usage trends over time. To view your carbon footprint data, navigate to your carbon emissions data through the AWS Billing and Cost Management console. For more information about CCFT visit the CCFT capabilities and features page, review the CCFT user guides, and learn more by visiting the CCFT webpage.

🆕 AWS now publishes carbon footprint data in 21 days or less, down from a three-month lag, offering timely insights to reduce emissions and costs via the AWS Billing and Cost Management console.

#AWS #CloudFinancialManagement

1 0 0 0
AWS Billing and Cost Management now supports PDF export and CSV data download for Dashboards Today, AWS announces PDF export and CSV data download capabilities for AWS Billing and Cost Management Dashboards. These new features enable you to export your customized dashboards as PDF files for offline analysis and sharing, and download individual widget data in CSV format for detailed examination in spreadsheet applications. With these capabilities, you now have more ways to distribute AWS cost insights across your organization, in addition to https://docs.aws.amazon.com/cost-management/latest/userguide/share-dashboards.htmlwith can-view or can-edit access. Billing and Cost Management Dashboards allows you to export entire dashboards or individual widgets as PDF files directly from the console, eliminating the need for screenshots or manual formatting. The PDF export feature provides formatted reports that maintain consistent appearance and preserve dashboard layouts, making them ideal for sharing with stakeholders during board meetings, reviews, or strategic planning sessions. For detailed data analysis needs, you can export individual widget data in CSV format, enabling analysts to perform granular examination of specific cost metrics in their preferred spreadsheet tools. AWS Billing and Cost Management Dashboards PDF and CSV export features are available at no additional cost in all AWS commercial Regions, excluding AWS China Regions. To get started, visit the AWS Billing and Cost Management console and select "Dashboards" from the left navigation menu. For more information, see the AWS Billing and Cost Management Dashboards export https://docs.aws.amazon.com/cost-management/latest/userguide/export-dashboards.html.

AWS Billing and Cost Management now supports PDF export and CSV data download for Dashboards

Today, AWS announces PDF export and CSV data download capabilities for AWS Billing and Cost Management Dashboards. These new features enable you to export your customize...

#AWS #CloudFinancialManagement

0 0 0 0
Amazon EKS introduces enhanced network security policies Today, we’re announcing enhanced network policy capabilities in https://aws.amazon.com/eks/, allowing customers to improve the network security posture for their Kubernetes workloads and their integrations with cluster-external destinations. This enhancement builds on network segmentation features previously supported in EKS. Now you can centrally enforce network access filters across the entire cluster, as well as leverage Domain Name System (DNS) based policies to secure egress traffic from your cluster’s environment. As customers continue to scale their application environments using EKS, network traffic isolation is increasingly fundamental for preventing unauthorized access to resources inside and outside the cluster. To address this, EKS introduced support for https://kubernetes.io/docs/concepts/services-networking/network-policies/ in the https://github.com/aws/amazon-vpc-cni-k8s, allowing you to segment pod-to-pod communication at a namespace level. Now you can further strengthen the defensive posture for your Kubernetes network environment by centrally managing network filters for the whole cluster. Also, cluster admins now have a more stable and predictable approach for preventing unauthorized access to cluster-external resources in the cloud or on-prem using egress rules that filter traffic to external endpoints based on their Fully Qualified Domain Name (FQDN). These new network security features are available in all commercial AWS Regions for new EKS clusters running Kubernetes version 1.29 or later, with support for existing clusters to follow in the coming weeks. ClusterNetworkPolicy is available in all EKS cluster launch modes using VPC CNI v1.21.0 or later. DNS-based policies are only supported in https://docs.aws.amazon.com/eks/latest/userguide/automode.html. To learn more, visit the https://docs.aws.amazon.com/eks/latest/userguide/auto-net-pol.html or read the https://aws.amazon.com/blogs/containers/amazon-eks-introduces-enhanced-network-policy-capabilities.

Amazon EKS introduces enhanced network security policies

Today, we’re announcing enhanced network policy capabilities in https://aws.amazon.com/eks/ allowing customers to improve the network security posture for their Kubernetes workloads and their integratio...

#AWS #CloudFinancialManagement

0 0 0 0
Announcing cost allocation using users’ attributes AWS announces a new cost allocation feature that uses existing workforce user attributes like cost center, division, organization, and department to track and analyze AWS application usage and cost. This new capability enables customers to allocate per-user monthly subscription and on-demand fees of AWS applications, such as Amazon Q Business, Amazon Q Developer, and Amazon QuickSight, to respective internal business units. Customers should import their workforce users’ attributes to IAM Identity Center, the recommended service for managing workforce access to AWS applications. After importing the attributes, customers can enable one or more of these attributes as cost allocation tags from the AWS Billing and Cost Management console. When users access AWS applications, their usage and cost are automatically recorded with selected attributes. Cloud Financial Operations (FinOps) professionals can view and analyze costs in AWS Cost Explorer and AWS CUR 2.0, gaining visibility into how different teams drive AWS usage and costs. Support for cost allocation using user attributes is generally available in all AWS Regions, excluding GovCloud (US) Regions and China (Beijing) and China (Ningxia) Regions. To learn more, see https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html.

Announcing cost allocation using users’ attributes

AWS announces a new cost allocation feature that uses existing workforce user attributes like cost center, division, organization, and department to track and analyze AWS application usage and cost. This new c...

#AWS #CloudFinancialManagement

0 0 0 0
Preview
AWS Billing and Cost Management now supports PDF export and CSV data download for Dashboards Today, AWS announces PDF export and CSV data download capabilities for AWS Billing and Cost Management Dashboards. These new features enable you to export your customized dashboards as PDF files for offline analysis and sharing, and download individual widget data in CSV format for detailed examination in spreadsheet applications. With these capabilities, you now have more ways to distribute AWS cost insights across your organization, in addition to sharing dashboards with can-view or can-edit access. Billing and Cost Management Dashboards allows you to export entire dashboards or individual widgets as PDF files directly from the console, eliminating the need for screenshots or manual formatting. The PDF export feature provides formatted reports that maintain consistent appearance and preserve dashboard layouts, making them ideal for sharing with stakeholders during board meetings, reviews, or strategic planning sessions. For detailed data analysis needs, you can export individual widget data in CSV format, enabling analysts to perform granular examination of specific cost metrics in their preferred spreadsheet tools. AWS Billing and Cost Management Dashboards PDF and CSV export features are available at no additional cost in all AWS commercial Regions, excluding AWS China Regions. To get started, visit the AWS Billing and Cost Management console and select "Dashboards" from the left navigation menu. For more information, see the AWS Billing and Cost Management Dashboards export user guide.

🆕 AWS Billing and Cost Management now supports PDF and CSV exports for Dashboards, enabling offline analysis and detailed data examination in spreadsheets, available at no extra cost in all regions except AWS China.

#AWS #CloudFinancialManagement

0 0 0 0
Preview
Announcing cost allocation using users’ attributes AWS announces a new cost allocation feature that uses existing workforce user attributes like cost center, division, organization, and department to track and analyze AWS application usage and cost. This new capability enables customers to allocate per-user monthly subscription and on-demand fees of AWS applications, such as Amazon Q Business, Amazon Q Developer, and Amazon QuickSight, to respective internal business units. Customers should import their workforce users’ attributes to IAM Identity Center, the recommended service for managing workforce access to AWS applications. After importing the attributes, customers can enable one or more of these attributes as cost allocation tags from the AWS Billing and Cost Management console. When users access AWS applications, their usage and cost are automatically recorded with selected attributes. Cloud Financial Operations (FinOps) professionals can view and analyze costs in AWS Cost Explorer and AWS CUR 2.0, gaining visibility into how different teams drive AWS usage and costs. Support for cost allocation using user attributes is generally available in all AWS Regions, excluding GovCloud (US) Regions and China (Beijing) and China (Ningxia) Regions. To learn more, see organizing and tracking cost using AWS cost allocation tags.

🆕 AWS now lets you track and analyze costs by user attributes like cost center or division. Import these to IAM Identity Center, enable tags in Billing, and view in Cost Explorer. Available everywhere except GovCloud and China.

#AWS #CloudFinancialManagement

0 0 0 0
Preview
Amazon EKS introduces enhanced network security policies Today, we’re announcing enhanced network policy capabilities in Amazon Elastic Kubernetes Service (EKS), allowing customers to improve the network security posture for their Kubernetes workloads and their integrations with cluster-external destinations. This enhancement builds on network segmentation features previously supported in EKS. Now you can centrally enforce network access filters across the entire cluster, as well as leverage Domain Name System (DNS) based policies to secure egress traffic from your cluster’s environment. As customers continue to scale their application environments using EKS, network traffic isolation is increasingly fundamental for preventing unauthorized access to resources inside and outside the cluster. To address this, EKS introduced support for Kubernetes NetworkPolicies in the Amazon VPC Container Network Interface (VPC CNI) plugin, allowing you to segment pod-to-pod communication at a namespace level. Now you can further strengthen the defensive posture for your Kubernetes network environment by centrally managing network filters for the whole cluster. Also, cluster admins now have a more stable and predictable approach for preventing unauthorized access to cluster-external resources in the cloud or on-prem using egress rules that filter traffic to external endpoints based on their Fully Qualified Domain Name (FQDN). These new network security features are available in all commercial AWS Regions for new EKS clusters running Kubernetes version 1.29 or later, with support for existing clusters to follow in the coming weeks. ClusterNetworkPolicy is available in all EKS cluster launch modes using VPC CNI v1.21.0 or later. DNS-based policies are only supported in EKS Auto Mode-launched EC2 instances. To learn more, visit the Amazon EKS documentation or read the launch blog post here.

🆕 Amazon EKS now provides improved network security with Kubernetes NetworkPolicies and DNS-based egress rules to isolate pod traffic and secure external connections, available in all commercial AWS Regions for Kubernetes 1.29+. For details, see the Amazon EKS docum…

#AWS #CloudFinancialManagement

0 0 0 0
Announcing Database Savings Plans with up to 35% savings Today, AWS announces Database Savings Plans, a new flexible pricing model that helps you save up to 35% in exchange for a commitment to a consistent amount of usage (measured in $/hour) over a one-year term with no upfront payment. Database Savings Plans automatically apply to eligible serverless and provisioned instance usage regardless of supported engine, instance family, size, deployment option, or AWS Region. For example, with Database Savings Plans, you can change between Aurora db.r7g and db.r8g instances, shift a workload from EU (Ireland) to US (Ohio), modernize from Amazon RDS for Oracle to Amazon Aurora PostgreSQL or from RDS to Amazon DynamoDB and still benefit from discounted pricing offered by Database Savings Plans. Database Savings Plans will be available starting today in all AWS Regions, except China Regions, with support for Amazon Aurora, Amazon RDS, Amazon DynamoDB, Amazon ElastiCache, Amazon DocumentDB (with MongoDB compatibility), Amazon Neptune, Amazon Keyspaces (for Apache Cassandra), Amazon Timestream, and AWS Database Migration Service (DMS). You can get started with Database Savings Plans from the AWS Billing and Cost Management Console or by using the AWS CLI. To realize the largest savings, you can make a commitment to Savings Plans by using purchase recommendations provided in the console. For a more customized analysis, you can use the Savings Plans Purchase Analyzer to estimate potential cost savings for custom purchase scenarios. For more information, visit the Database Savings Plans pricing page and the AWS Savings Plans FAQs.

Announcing Database Savings Plans with up to 35% savings

Today, AWS announces Database Savings Plans, a new flexible pricing model that helps you save up to 35% in exchange for a commitment to a consistent amount of usage (measured in $/hour) over a one-year ter...

#AWS #CloudFinancialManagement

0 0 0 0
AWS Compute Optimizer now supports unused NAT Gateway recommendations 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 supports unused NAT Gateway recommendations

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 identif...

#AWS #AwsComputeOptimizer #CloudFinancialManagement

1 0 0 0
Preview
AWS Compute Optimizer now supports unused NAT Gateway recommendations 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 recommends unused NAT Gateways, helping you identify idle resources for cost savings. Available in most regions, it analyzes traffic metrics and route tables to ensure recommendations are safe.

#AWS #AwsComputeOptimizer #CloudFinancialManagement

1 0 0 0
Announcing AWS Compute Optimizer automation rules 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.

Announcing AWS Compute Optimizer automation rules

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. Wit...

#AWS #CloudFinancialManagement #AmazonElasticBlockStore #AwsComputeOptimizer

1 0 0 0
Preview
Announcing AWS Compute Optimizer automation rules 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 adds automation rules for EBS volume optimization, saving costs and boosting performance. Automate cleanup and upgrades with criteria-based scheduling. Available in multiple regions; manage via a …

#AWS #CloudFinancialManagement #AmazonElasticBlockStore #AwsComputeOptimizer

1 0 0 0
AWS Cost Anomaly Detection accelerates anomaly identification AWS Cost Anomaly Detection now features an improved detection algorithm that enables faster identification of unusual spending patterns. The enhanced algorithm analyzes your AWS spend using rolling 24-hour windows, comparing current costs against equivalent time periods from previous days each time AWS receives updated cost and usage data. The enhanced algorithm addresses two common challenges in cost pattern analysis. First, it removes the delay in anomaly detection caused by comparing incomplete calendar-day costs against historical daily totals. The rolling window always compares full 24-hour periods, enabling faster identification of unusual patterns. Second, it provides more accurate comparisons by evaluating costs against similar times of day, accounting for workloads that have different morning and evening usage patterns. These improvements help reduce false positives while enabling faster, more accurate anomaly detection. This enhancement to AWS Cost Anomaly Detection is available in all AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To learn more about this new feature, AWS Cost Anomaly Detection, and how to reduce your risk of spend surprises, visit the AWS Cost Anomaly Detection https://aws.amazon.com/aws-cost-management/aws-cost-anomaly-detection/ and https://docs.aws.amazon.com/cost-management/latest/userguide/billing-getting-started.html.

AWS Cost Anomaly Detection accelerates anomaly identification

AWS Cost Anomaly Detection now features an improved detection algorithm that enables faster identification of unusual spending patterns. The enhanced algorithm analyzes your AWS spend using rolling 24...

#AWS #CloudFinancialManagement

1 0 0 0
Preview
AWS Cost Anomaly Detection accelerates anomaly identification AWS Cost Anomaly Detection now features an improved detection algorithm that enables faster identification of unusual spending patterns. The enhanced algorithm analyzes your AWS spend using rolling 24-hour windows, comparing current costs against equivalent time periods from previous days each time AWS receives updated cost and usage data. The enhanced algorithm addresses two common challenges in cost pattern analysis. First, it removes the delay in anomaly detection caused by comparing incomplete calendar-day costs against historical daily totals. The rolling window always compares full 24-hour periods, enabling faster identification of unusual patterns. Second, it provides more accurate comparisons by evaluating costs against similar times of day, accounting for workloads that have different morning and evening usage patterns. These improvements help reduce false positives while enabling faster, more accurate anomaly detection. This enhancement to AWS Cost Anomaly Detection is available in all AWS Regions, except the AWS GovCloud (US) Regions and the China Regions. To learn more about this new feature, AWS Cost Anomaly Detection, and how to reduce your risk of spend surprises, visit the AWS Cost Anomaly Detection product page and getting started guide.

🆕 AWS Cost Anomaly Detection now uses a faster algorithm for quicker anomaly detection, comparing 24-hour periods to reduce delays and false positives, available in all regions except AWS GovCloud (US) and China.

#AWS #CloudFinancialManagement

0 0 0 0
Announcing enhanced cost management capabilities in Amazon Q Developer Amazon Q Developer now offers enhanced cost management capabilities, enabling customers to analyze costs across a wider range of Cloud Financial Management domains with more advanced analytical capabilities. Customers can now ask complex, open-ended questions about historical and forecasted costs and usage, optimization recommendations, commitment coverage and utilization, cost anomalies, budgets, free tier usage, product attributes, and cost estimation. Q can explore data, form hypotheses, and perform calculations to provide deeper insights with less time and expertise required. With these capabilities, FinOps practitioners, engineers, and Finance professionals can increase productivity by delegating more cost analysis and estimation tasks to Q. For example, customers can ask "Why did costs for this application increase last week?". Q will explore the data by retrieving costs and usage quantities by service, account, or resource, form hypotheses, gather data from multiple sources, and perform calculations ranging from simple period-over-period cost changes to unit economic metrics like effective cost per instance-hour. Q provides transparency on each API call it makes to retrieve data, including specific parameters used, and provides matching console links where customers can verify the data or dive deeper. To get started, open the Amazon Q chat panel from anywhere in the AWS Management Console and ask a question about your costs. To learn more, see https://docs.aws.amazon.com/cost-management/latest/userguide/ce-cost-analysis-q.html in the AWS Cost Management user guide.

Announcing enhanced cost management capabilities in Amazon Q Developer

Amazon Q Developer now offers enhanced cost management capabilities, enabling customers to analyze costs across a wider range of Cloud Financial Management domains with more advanced analytic...

#AWS #CloudFinancialManagement

1 0 0 0
AWS Cost Optimization Hub introduces Cost Efficiency metric to measure and track cloud cost efficiency AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track cloud cost efficiency over time across your organization. This metric automatically calculates the percentage of your cloud spend that can be optimized by considering rightsizing, idle, and commitment recommendations, allowing you to establish consistent cost savings benchmarks, set performance goals, and track progress to maximize your return on cloud investments. AWS Cost Optimization Hub provides you with a measure of your cost efficiency by dividing aggregated estimated monthly savings of your cost optimization opportunities by your optimizable spend. You can track this metric over time across your organization to understand and benchmark your cost efficiency. With daily refreshes, the metric provides daily insights into optimization progress, showing score improvements when you implement cost-saving recommendations and score decreases when inefficient resources are provisioned. Cost efficiency is now available in AWS https://aws.amazon.com/aws-cost-management/cost-optimization-hub/ across all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ where AWS Cost Optimization Hub is supported. To get started with cost efficiency metric, please visit the https://docs.aws.amazon.com/cost-management/latest/userguide/cost-optimization-hub.html and https://aws.amazon.com/blogs/aws-cloud-financial-management/measuring-cloud-cost-efficiency-with-the-new-cost-efficiency-metric-by-aws/. 

AWS Cost Optimization Hub introduces Cost Efficiency metric to measure and track cloud cost efficiency

AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track clo...

#AWS #CloudFinancialManagement

1 0 0 0
Savings Plans and Reserved Instances Group Sharing is now generally available AWS today announced the general availability of Reserved Instances and Savings Plans (RISP) Group Sharing, a new Billing and Cost Management feature that gives customers granular control over how AWS commitments are shared across their organization. This capability allows customers to define how Reserved Instances and Savings Plans benefits are distributed among specific groups of accounts within their AWS organization, ensuring cost savings align with their business structure and accountability requirements. RISP Group Sharing addresses a common challenge faced by enterprise customers managing AWS costs across multiple business units: for example, Reserved Instances and Savings Plans don't always benefit the teams that purchased them. With this feature, customers can create groups using AWS Cost Categories that reflect their organizational hierarchy—whether by business units, projects, geographical regions, or funding sources. The feature offers two sharing options: the Prioritized Group Sharing applies commitments to defined groups first, then shares unused capacity organization-wide, while the Restricted Group Sharing keeps commitments exclusively within defined groups for complete isolation when strict boundaries are required. RISP Group Sharing is available now in all AWS Regions, except AWS GovCloud (US) Regions and the China Regions. To get started with RISP Group Sharing, visit the Billing preferences from the http://console.aws.amazon.com/billing/home and follow the guided setup to create your first Cost Category and configure sharing preferences. For detailed implementation guidance, see the http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/ri-sp-group-sharing.html. and https://aws.amazon.com/blogs/aws-cloud-financial-management/control-your-aws-commitments-with-risp-group-sharing/.  

Savings Plans and Reserved Instances Group Sharing is now generally available

AWS today announced the general availability of Reserved Instances and Savings Plans (RISP) Group Sharing, a new Billing and Cost Management feature that gives customers granular contr...

#AWS #CloudFinancialManagement

0 0 0 0
Split Cost Allocation Data for Amazon EKS supports Kubernetes labels Starting today, Split Cost Allocation Data for Amazon EKS now allows you to import up to 50 Kubernetes custom labels per pod as cost allocation tags. You can attribute costs of your Amazon EKS cluster at the pod level using custom attributes, such as cost center, application, business unit, and environment in AWS Cost and Usage Report (CUR). With this new https://docs.aws.amazon.com/cur/latest/userguide/split-cost-allocation-data-kubernetes-labels.html, you can better align your cost allocation with specific business requirements and organizational structure driven by your cloud financial management needs. This enables granular cost visibility of your EKS clusters running multiple application containers using shared EC2 instances, allowing you to allocate the shared costs of your EKS cluster. For new split cost allocation data customers, you can enable this feature in the AWS Billing and Cost Management console. For existing customers, EKS will automatically import the labels, but you must activate them as cost allocation tags. After activation, Kubernetes custom labels are available in your CUR within 24 hours. You can use the https://docs.aws.amazon.com/guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard.html to visualize the costs in Amazon QuickSight and the https://catalog.workshops.aws/cur-query-library/en-US/queries/container to query the costs using Amazon Athena. This feature is available in all AWS Regions where Split Cost Allocation Data for Amazon EKS is available. To get started, visit https://docs.aws.amazon.com/cur/latest/userguide/split-cost-allocation-data.html.

Split Cost Allocation Data for Amazon EKS supports Kubernetes labels

Starting today, Split Cost Allocation Data for Amazon EKS now allows you to import up to 50 Kubernetes custom labels per pod as cost allocation tags. You can attribute costs of your Amazon EKS ...

#AWS #CloudFinancialManagement

2 0 0 0
Preview
Split Cost Allocation Data for Amazon EKS supports Kubernetes labels Starting today, Split Cost Allocation Data for Amazon EKS now allows you to import up to 50 Kubernetes custom labels per pod as cost allocation tags. You can attribute costs of your Amazon EKS cluster at the pod level using custom attributes, such as cost center, application, business unit, and environment in AWS Cost and Usage Report (CUR). With this new capability, you can better align your cost allocation with specific business requirements and organizational structure driven by your cloud financial management needs. This enables granular cost visibility of your EKS clusters running multiple application containers using shared EC2 instances, allowing you to allocate the shared costs of your EKS cluster. For new split cost allocation data customers, you can enable this feature in the AWS Billing and Cost Management console. For existing customers, EKS will automatically import the labels, but you must activate them as cost allocation tags. After activation, Kubernetes custom labels are available in your CUR within 24 hours. You can use the Containers Cost Allocation dashboard to visualize the costs in Amazon QuickSight and the CUR query library to query the costs using Amazon Athena. This feature is available in all AWS Regions where Split Cost Allocation Data for Amazon EKS is available. To get started, visit Understanding Split Cost Allocation Data.

🆕 AWS EKS now supports up to 50 Kubernetes labels for cost allocation, enabling granular cost visibility and alignment with business needs. Activate custom labels in AWS CUR to visualize costs in QuickSight. Available in all regions with EKS Split Cost Allocation.

#AWS #CloudFinancialManagement

1 0 0 0
AWS’ Customer Carbon Footprint Tool now includes Scope 3 emissions data Today, AWS’ Customer Carbon Footprint Tool (CCFT) has been updated to include Scope 3 emissions data and Scope 1 natural gas and refrigerants, providing AWS customers more complete visibility into their cloud carbon footprint. This update expands the CCFT to cover all three industry-standard emission scopes as defined by the Greenhouse Gas Protocol. The CCFT Scope 3 update gives AWS customers full visibility into the lifecycle carbon impact of their AWS usage, including emissions from manufacturing the servers that run their workloads, powering AWS facilities, and transporting equipment to data centers. Historical data is available back to January 2022, allowing organizations to track their progress over time and make informed decisions about their cloud strategy to meet their sustainability goals. This data is available through the CCFT dashboard and AWS Billing and Cost Management Data Exports, enabling customers to easily incorporate carbon insights into their operational workflows, sustainability planning, and reporting processes. To learn more about the enhanced Customer Carbon Footprint Tool, visit the https://aws.amazon.com/sustainability/tools/aws-customer-carbon-footprint-tool/, https://us-east-1.console.aws.amazon.com/costmanagement/home?region=us-east-1#/customer-carbon-footprint-tool or read the https://sustainability.aboutamazon.com/aws-customer-carbon-footprint-tool-methodology.pdf and https://docs.aws.amazon.com/ccft/latest/releasenotes/what-is-ccftrn.html.

AWS’ Customer Carbon Footprint Tool now includes Scope 3 emissions data

Today, AWS’ Customer Carbon Footprint Tool (CCFT) has been updated to include Scope 3 emissions data and Scope 1 natural gas and refrigerants, providing AWS customers more complete visib...

#AWS #CloudFinancialManagement

0 0 0 0
Preview
AWS’ Customer Carbon Footprint Tool now includes Scope 3 emissions data Today, AWS’ Customer Carbon Footprint Tool (CCFT) has been updated to include Scope 3 emissions data and Scope 1 natural gas and refrigerants, providing AWS customers more complete visibility into their cloud carbon footprint. This update expands the CCFT to cover all three industry-standard emission scopes as defined by the Greenhouse Gas Protocol. The CCFT Scope 3 update gives AWS customers full visibility into the lifecycle carbon impact of their AWS usage, including emissions from manufacturing the servers that run their workloads, powering AWS facilities, and transporting equipment to data centers. Historical data is available back to January 2022, allowing organizations to track their progress over time and make informed decisions about their cloud strategy to meet their sustainability goals. This data is available through the CCFT dashboard and AWS Billing and Cost Management Data Exports, enabling customers to easily incorporate carbon insights into their operational workflows, sustainability planning, and reporting processes. To learn more about the enhanced Customer Carbon Footprint Tool, visit the CCFT Website, AWS Billing and Cost Management console or read the updated methodology documentation and release notes.

🆕 AWS’ Customer Carbon Footprint Tool now includes Scope 3 emissions, offering full visibility into lifecycle carbon impact, from server manufacturing to data center transport. Historical data back to Jan 2022 available.

#AWS #CloudFinancialManagement

1 0 0 0
Amazon Q Developer now help customers understand service prices and estimate workload costs Today, AWS announces a new pricing and cost estimation capability in Amazon Q Developer. Amazon Q Developer is the most capable generative AI-powered assistant for software development. With this launch, customers can now use Amazon Q Developer to get information about AWS product and service pricing, availability, and attributes, helping them select the right resources and estimate workload costs using natural language. When architecting new workloads on AWS, customers need to estimate costs so they can evaluate cost/performance tradeoffs, set budgets, and plan future spending. Customers can now use Amazon Q Developer to retrieve detailed product attribute and pricing information using natural language, making it easier to estimate the cost of new workloads without having to review multiple pricing pages or specify detailed API request parameters. Customers can now ask questions about service pricing (e.g., “How much does RDS extended support cost?”), the cost of a planned workload (e.g., “I need to send 1 million notifications per month to email, and 1 million to HTTP/S endpoints. Estimate the monthly cost using SNS.”), or the relative costs of different resources (e.g., “What is the cost difference between an Application Load Balancer and a Network Load Balancer?”). To answer these questions, Amazon Q Developer retrieves information from the AWS Price List APIs. To learn more, see https://docs.aws.amazon.com/cost-management/latest/userguide/ce-cost-analysis-q.html. To get started, open the Amazon Q chat panel in the AWS Management Console and ask a question about pricing.

Amazon Q Developer now help customers understand service prices and estimate workload costs

Today, AWS announces a new pricing and cost estimation capability in Amazon Q Developer. Amazon Q Developer is the most capable generative AI-powered assistant for softwa...

#AWS #CloudFinancialManagement

1 0 0 0
Preview
Amazon Q Developer now help customers understand service prices and estimate workload costs Today, AWS announces a new pricing and cost estimation capability in Amazon Q Developer. Amazon Q Developer is the most capable generative AI-powered assistant for software development. With this launch, customers can now use Amazon Q Developer to get information about AWS product and service pricing, availability, and attributes, helping them select the right resources and estimate workload costs using natural language. When architecting new workloads on AWS, customers need to estimate costs so they can evaluate cost/performance tradeoffs, set budgets, and plan future spending. Customers can now use Amazon Q Developer to retrieve detailed product attribute and pricing information using natural language, making it easier to estimate the cost of new workloads without having to review multiple pricing pages or specify detailed API request parameters. Customers can now ask questions about service pricing (e.g., “How much does RDS extended support cost?”), the cost of a planned workload (e.g., “I need to send 1 million notifications per month to email, and 1 million to HTTP/S endpoints. Estimate the monthly cost using SNS.”), or the relative costs of different resources (e.g., “What is the cost difference between an Application Load Balancer and a Network Load Balancer?”). To answer these questions, Amazon Q Developer retrieves information from the AWS Price List APIs. To learn more, see Managing your costs using generative AI with Amazon Q Developer. To get started, open the Amazon Q chat panel in the AWS Management Console and ask a question about pricing.

🆕 AWS introduces a new pricing feature in Amazon Q Developer, enabling users to understand service prices and estimate workload costs via natural language queries, simplifying cost management for new workloads.

#AWS #CloudFinancialManagement

1 0 0 0
AWS Introduces self-service invoice correction feature Today, AWS announces the general availability of a self-service Invoice correction feature to update AWS invoices. This launch enables all AWS customers to correct key invoice attributes—including purchase order numbers, business legal name, and addresses — on their AWS invoices and get corrected invoices instantaneously. AWS customers can now access the new self-service Invoice correction feature directly from the AWS Billing and Cost Management console. This feature offers AWS customers a guided self-service workflow to update invoice attributes in their account settings and on select invoices. This feature gives AWS customers direct control over invoice corrections while reducing wait times and improving efficiency in managing their AWS accounts. AWS self-service Invoice Correction feature is generally available in all AWS Regions, excluding GovCloud (US) Regions and China (Beijing) and China (Ningxia) Regions. To get started with AWS self-service invoice correction feature, please visit the https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/getting-viewing-bill.html#view-invoices. 

AWS Introduces self-service invoice correction feature

Today, AWS announces the general availability of a self-service Invoice correction feature to update AWS invoices. This launch enables all AWS customers to correct key invoice attributes—including purchase...

#AWS #CloudFinancialManagement

1 0 0 0
Preview
AWS Introduces self-service invoice correction feature Today, AWS announces the general availability of a self-service Invoice correction feature to update AWS invoices. This launch enables all AWS customers to correct key invoice attributes—including purchase order numbers, business legal name, and addresses — on their AWS invoices and get corrected invoices instantaneously. AWS customers can now access the new self-service Invoice correction feature directly from the AWS Billing and Cost Management console. This feature offers AWS customers a guided self-service workflow to update invoice attributes in their account settings and on select invoices. This feature gives AWS customers direct control over invoice corrections while reducing wait times and improving efficiency in managing their AWS accounts. AWS self-service Invoice Correction feature is generally available in all AWS Regions, excluding GovCloud (US) Regions and China (Beijing) and China (Ningxia) Regions. To get started with AWS self-service invoice correction feature, please visit the product details page.

🆕 AWS now offers a self-service Invoice Correction feature for updating purchase order numbers, names, and addresses on invoices instantly. Available globally except GovCloud and China regions, it's accessible via the Billing and Cost Management console.

#AWS #CloudFinancialManagement

1 0 0 0