Today, AWS announces the general availability of a new capability of AWS Service Quotas called automatic quota management. AWS Service Quotas helps you view and manage your quotas from a central location. This new feature monitors quota usage, and notifies customers before they run out of their allocated quotas supported on AWS Service Quotas. This helps customers with better visibility and proactive awareness about their quota usage, enabling them to scale their applications without interruptions. AWS customers can get notified of their quota usage with automatic quota management. Customers can configure their preferred notifications channels, such as email, SMS, or Slack, through Service Quotas console or API. Notifications are also available in AWS Health, and customers can subscribe to related AWS Cloudtrail events for automation workflows. This new capability is now available at no additional cost in all AWS commercial regions. To explore this feature and for details, please visit and AWS Service Quotas documentation.

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for cross-account ingestion. Starting today, you can agentlessly scrape metrics from Amazon Elastic Kubernetes Service clusters in different accounts than your Amazon Managed Service for Prometheus workspace. While it was previously possible to apply AWS multi-account best practices for centralized observability with Amazon Managed Service for Prometheus workspaces, you had to use self-managed collection. This meant that you had to run, scale, and patch telemetry agents yourself to scrape metrics from Amazon Elastic Kubernetes Service clusters in various accounts in order to ingest them into a central Amazon Managed Service for Prometheus workspaces in a different account. With this launch, you can now use the Amazon Managed Service for Prometheus collector to get rid of this heavy lifting and ingest metrics in a cross-account setup without having to self-run a collector. In addition, you can now also use the Amazon Managed Service for Prometheus collector to scrape metrics from for Amazon Elastic Kubernetes Service clusters to ingest them into Amazon Managed Service for Prometheus workspaces created with customer managed keys. Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is available. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

Amazon Managed Service for Prometheus is now available in the AWS GovCloud (US) Regions. Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found in the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html. Customers can send up to 1 billion active metrics to a single workspace and can create multiple workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus, visit the https://aws.amazon.com/prometheus.

Amazon Managed Service for Prometheus is now available in Africa (Cape Town), Asia Pacific (Thailand), Asia Pacific (Hong Kong), Asia Pacific (Malaysia), Europe (Milan), Europe (Zurich), and Middle East (UAE). Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found on the user guide. Customers can send up to 1 billion active metrics to a single workspace and can create many workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

Today, AWS announces the general availability of a new capability of AWS Service Quotas called automatic quota management. AWS Service Quotas helps you view and manage your quotas from a central location. This new feature monitors quota usage, and notifies customers before they run out of their allocated quotas supported on AWS Service Quotas. This helps customers with better visibility and proactive awareness about their quota usage, enabling them to scale their applications without interruptions. AWS customers can get notified of their quota usage with automatic quota management. Customers can configure their preferred notifications channels, such as email, SMS, or Slack, through Service Quotas console or API. Notifications are also available in AWS Health, and customers can subscribe to related AWS Cloudtrail events for automation workflows. This new capability is now available at no additional cost in all AWS commercial regions. To explore this feature and for details, please visit Service Quotas console and AWS Service Quotas documentation.

Developers can now use their existing AWS Management Console sign-in credentials for programmatic access to AWS services. After a quick browser-based authentication flow, AWS automatically generates temporary credentials that work across local development tools like the AWS CLI, AWS Tools for PowerShell and AWS SDKs. To get started, simply install or upgrade to the latest version of the AWS CLI and run aws login in your terminal. This login for AWS local development feature makes it easier to start building with AWS services within minutes of account sign-up, eliminating the need to create and manage separate identities and access keys for programmatic access. The aws login CLI command generates short-lived credentials that are automatically rotated, reducing the risks associated with long-term access keys and enhancing your security posture. This feature is available in all commercial AWS regions. To get started, install or upgrade to AWS CLI version 2.32.0 and the latest versions of all AWS SDKs. For more information, please read our blog or visit the AWS CLI User Guide.

Today, we’re excited to announce the general availability of new capability of automatic quota management feature in AWS Service Quotas. Today, automatic quota management supports customers to receive notifications when their quota usage approaches their allocated quotas and configure their preferred notifications channel, such as email, SMS, or Slack, through Service Quotas console or API. Now, this feature adjusts values of AWS services’ quotas automatically and safely based on customer’s usage, which reduces operational burden from customers to constantly monitor their quota usage, and request quota increases across multiple AWS services in different AWS accounts and Regions. Customers can now confidently scale their applications on AWS to meet their growing customer demand without the risk of unexpected service interruptions due to quota exhaustion. This new capability is now available at no additional cost in all AWS commercial regions. To explore this feature and for details, please visit and https://docs.aws.amazon.com/servicequotas/latest/userguide/automatic-management.html.

Today, we’re excited to announce the general availability of new capability of automatic quota management feature in AWS Service Quotas. Today, automatic quota management supports customers to receive notifications when their quota usage approaches their allocated quotas and configure their preferred notifications channel, such as email, SMS, or Slack, through Service Quotas console or API. Now, this feature adjusts values of AWS services’ quotas automatically and safely based on customer’s usage, which reduces operational burden from customers to constantly monitor their quota usage, and request quota increases across multiple AWS services in different AWS accounts and Regions. Customers can now confidently scale their applications on AWS to meet their growing customer demand without the risk of unexpected service interruptions due to quota exhaustion. This new capability is now available at no additional cost in all AWS commercial regions. To explore this feature and for details, please visit Service Quotas console and AWS Service Quotas documentation.

Amazon Managed Service for Prometheus is now available in Africa (Cape Town), Asia Pacific (Thailand), Asia Pacific (Hong Kong), Asia Pacific (Malaysia), Europe (Milan), Europe (Zurich), and Middle East (UAE). Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found on the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html. Customers can send up to 1 billion active metrics to a single workspace and can create many workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html or https://aws.amazon.com/prometheus.  

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, now offers customers the option to collect metrics from an Amazon Elastic Kubernetes Service clusters using Internet Protocol version 6 (IPv6) in a https://docs.aws.amazon.com/eks/latest/best-practices/subnets.html setup. The continued growth of the internet is exhausting available Internet Protocol version 4 (IPv4) addresses. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their VPCs. Customers can now use the managed service to collect IPv6 Prometheus metrics endpoints in Amazon Elastic Kubernetes Service clusters. To learn more on best practices for configuring IPv6 in your environment, visit the white paper on https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html. Support for IPv6 on Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is GA. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html or https://aws.amazon.com/prometheus.  

Amazon Managed Service for Prometheus now supports queries with time ranges up to 95 days, an increase from the previous 32-day limit. With this feature, customers can query any 95-day window, including historical data, allowing them to perform month-over-month comparisons, analyze long-term system trends and review historical incidents. This feature is now available across all Amazon Managed Service for Prometheus workspaces in all regions where the service is available. To get started, check out the product page and quotas page for more information about limits.

Developers can now use their existing AWS Management Console sign-in credentials for programmatic access to AWS services. After a quick browser-based authentication flow, AWS automatically generates temporary credentials that work across local development tools like the AWS CLI, AWS Tools for PowerShell and AWS SDKs. To get started, simply install or upgrade to the latest version of the AWS CLI and run aws login in your terminal. This login for AWS local development feature makes it easier to start building with AWS services within minutes of account sign-up, eliminating the need to create and manage separate identities and access keys for programmatic access. The aws login CLI command generates short-lived credentials that are automatically rotated, reducing the risks associated with long-term access keys and enhancing your security posture. This feature is available in all commercial AWS regions. To get started, install or upgrade to AWS CLI version 2.32.0 and the latest versions of all AWS SDKs. For more information, please read our https://aws.amazon.com/blogs/security/simplified-developer-access-to-aws-with-aws-login/ or visit the https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sign-in.html

Amazon Managed Service for Prometheus now supports queries with time ranges up to 95 days, an increase from the previous 32-day limit. With this feature, customers can query any 95-day window, including historical data, allowing them to perform month-over-month comparisons, analyze long-term system trends and review historical incidents. This feature is now available across all Amazon Managed Service for Prometheus workspaces in all regions where the service is available. To get started, check out the https://aws.amazon.com/prometheus/ and https://docs.aws.amazon.com/prometheus/latest/userguide/AMP_quotas.html for more information about limits.  

Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service, now provides the capability to identify expensive PromQL queries, and limit their execution. This enables customers to monitor and control the types of queries being issued against their Amazon Managed Service for Prometheus workspaces. Customers have highlighted the need for tighter governance controls for queries, specifically around high cost queries. You can now monitor queries above a certain Query Samples Processed (QSP) threshold, and log those queries to Amazon CloudWatch. The information in the vended logs allows you to identify expensive queries. The vended logs contain the PromQL query and metadata about where it originated from, such as from Grafana dashboard IDs or alerting rules. In addition, you can now set warning or error thresholds for query execution. To control query cost, you can pre-empt the execution of expensive queries by providing an error threshold in the HTTP headers to the https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-APIReference-QueryMetrics.html. Alternatively, by setting a warning threshold, we return the query results, charge you for the QSP, and return a warning to the end-user that the query is more expensive than the limit set by your workspace administrator. This feature is now available in all regions where Amazon Managed Service for Prometheus is https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html or https://aws.amazon.com/prometheus.  

Amazon Managed Service for Prometheus is now available in the AWS Canada (Central) region. Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found on the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html. Customers can send up to 1 billion active metrics to a single workspace and can create many workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html or https://aws.amazon.com/prometheus.  

Today, AWS announced managed support for Energy Data Insights (EDI) on AWS - delivered through AWS Managed Service (AMS), which enables energy customers to easily deploy, manage, and operate their subsurface data management platform on AWS, in compliance with the (OSDU®) standard. Now, you can automatically deploy EDI on AWS and accelerate your data ingestion from weeks to hours, and intelligently process and organize your subsurface data with minimal manual effort. AWS extends your team with operational capabilities, allowing you to focus on innovation and accelerating time to value with your subsurface data. With AWS-provided managed support, EDI on AWS removes the undifferentiated heavy-lifting and the complexities of deploying, operating, and maintaining an OSDU Data Platform on AWS, optimizing your EDI operations and security while ensuring round-the-clock availability and protection of the service. AWS handles critical operations on your behalf such as incident management, and backup and restore, significantly improving the resilience of your OSDU Data Platform on AWS. You also receive timely support for application upgrades and patches, allowing you to stay current with the latest features and improvements. EDI on AWS is available with pay-as-you-go pricing in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (Paris), and South America (São Paulo). To learn more about EDI, visit the https://aws.amazon.com/energy-utilities/osdu-data-platform/.

https://aws.amazon.com/prometheus/ now supports label-based active series limits within your workspace. This feature helps you manage active series volume across different producers such as applications, services or teams that share a workspace. You can now allocate specific active series limits to different metric producers in your workspace, enabling you to protect your critical metrics. If a sub-set of metrics experience an unexpected surge, only the metrics sharing the same label-based active series limits are throttled. For example, you can set different limits for metrics from different applications using label sets like {app="payment-service", environment="prod"}. If the payment-service application produced an unexpected surge in metrics, only ingested metrics originating from the payment-service application are throttled. This experience is enabled by the new Workspace Configuration APIs. Using these APIs, you can also manage the data retention period of your workspace. You can specify the number of days to retain metrics data within your workspace, before permanent deletion. To get started, visit AMP console's workspace configuration tab or use AWS CLI, SDK, or APIs. Check out the https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-workspace-configuration.html for detailed documentation. This feature is now available in all AWS regions where Amazon Managed Service for Prometheus is https://docs.aws.amazon.com/prometheus/latest/userguide/what-is-Amazon-Managed-Service-Prometheus.html#AMP-supported-Regions.

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for cross-account ingestion. Starting today, you can agentlessly scrape metrics from Amazon Elastic Kubernetes Service clusters in different accounts than your Amazon Managed Service for Prometheus workspace. While it was previously possible to apply AWS https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html#multi-account-strategy-best-practices-and-recommendations for centralized observability with Amazon Managed Service for Prometheus workspaces, you had to use self-managed collection. This meant that you had to run, scale, and patch telemetry agents yourself to scrape metrics from Amazon Elastic Kubernetes Service clusters in various accounts in order to ingest them into a central Amazon Managed Service for Prometheus workspaces in a different account. With this launch, you can now use the Amazon Managed Service for Prometheus collector to get rid of this heavy lifting and ingest metrics in a cross-account setup without having to self-run a collector. In addition, you can now also use the Amazon Managed Service for Prometheus collector to scrape metrics from for Amazon Elastic Kubernetes Service clusters to ingest them into Amazon Managed Service for Prometheus workspaces created with https://docs.aws.amazon.com/prometheus/latest/userguide/encryption-at-rest-Amazon-Service-Prometheus.html. Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is available. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html or https://aws.amazon.com/prometheus.  

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, now offers customers the option to collect metrics from an Amazon Elastic Kubernetes Service clusters using Internet Protocol version 6 (IPv6) in a https://docs.aws.amazon.com/eks/latest/best-practices/subnets.html setup. The continued growth of the internet is exhausting available Internet Protocol version 4 (IPv4) addresses. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their VPCs. Customers can now use the managed service to collect IPv6 Prometheus metrics endpoints in Amazon Elastic Kubernetes Service clusters. To learn more on best practices for configuring IPv6 in your environment, visit the white paper on https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/internet-protocol-version-6.html. Support for IPv6 on Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is GA. To learn more about Amazon Managed Service for Prometheus collector, visit the https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html or https://aws.amazon.com/prometheus.  

Observability solutions help you get up-and-running faster with infrastructure and application monitoring at AWS. They are intended for developers who need opinionated guidance about the best options for observing AWS services, custom applications, and third-party workloads. Observability solutions include working examples of instrumentation, telemetry collection, custom dashboards, and metric alarms. Using observability solutions, you can select from a catalog of available solutions that deliver focused observability guidance for AWS services and common workloads such as Java Virtual Machine (JVM), Apache Kafka, Apache Tomcat, or NGINX. Solutions cover monitoring tasks including installing and configuring Amazon CloudWatch agent, deploying pre-defined custom dashboards and setting metric alarms. Observability solutions also include guidance about observability features such as Detailed Monitoring metrics for infrastructure, Container Insights for container monitoring, and Application Signals for monitoring applications. Solutions are available for Amazon CloudWatch and Amazon Managed Service for Prometheus. Observability solutions can be deployed as-is or customized to suit specific use cases, with options for enabling features or configuring deployments based on workload needs. Observability solutions are available in all commercial regions. To get started with observability solutions, navigate to the https://console.aws.amazon.com/cloudwatch/home?#settings:/observability-solutions in the CloudWatch console.

Amazon Managed Service for Prometheus is now available in the AWS GovCloud (US) Regions. Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found in the user guide. Customers can send up to 1 billion active metrics to a single workspace and can create multiple workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus, visit the product page.

Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service, now provides the capability to identify expensive PromQL queries, and limit their execution. This enables customers to monitor and control the types of queries being issued against their Amazon Managed Service for Prometheus workspaces. Customers have highlighted the need for tighter governance controls for queries, specifically around high cost queries. You can now monitor queries above a certain Query Samples Processed (QSP) threshold, and log those queries to Amazon CloudWatch. The information in the vended logs allows you to identify expensive queries. The vended logs contain the PromQL query and metadata about where it originated from, such as from Grafana dashboard IDs or alerting rules. In addition, you can now set warning or error thresholds for query execution. To control query cost, you can pre-empt the execution of expensive queries by providing an error threshold in the HTTP headers to the QueryMetrics API. Alternatively, by setting a warning threshold, we return the query results, charge you for the QSP, and return a warning to the end-user that the query is more expensive than the limit set by your workspace administrator. This feature is now available in all regions where Amazon Managed Service for Prometheus is generally available. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

Amazon Managed Service for Prometheus is now available in the AWS Canada (Central) region. Amazon Managed Service for Prometheus is a fully managed Prometheus-compatible monitoring service that makes it easy to monitor and alarm on operational metrics at scale. The list of all supported regions where Amazon Managed Service for Prometheus is generally available can be found on the user guide. Customers can send up to 1 billion active metrics to a single workspace and can create many workspaces per account, where a workspace is a logical space dedicated to the storage and querying of Prometheus metrics. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

Today, AWS announced managed support for Energy Data Insights (EDI) on AWS - delivered through AWS Managed Service (AMS), which enables energy customers to easily deploy, manage, and operate their subsurface data management platform on AWS, in compliance with the (OSDU®) standard. Now, you can automatically deploy EDI on AWS and accelerate your data ingestion from weeks to hours, and intelligently process and organize your subsurface data with minimal manual effort. AWS extends your team with operational capabilities, allowing you to focus on innovation and accelerating time to value with your subsurface data. With AWS-provided managed support, EDI on AWS removes the undifferentiated heavy-lifting and the complexities of deploying, operating, and maintaining an OSDU Data Platform on AWS, optimizing your EDI operations and security while ensuring round-the-clock availability and protection of the service. AWS handles critical operations on your behalf such as incident management, and backup and restore, significantly improving the resilience of your OSDU Data Platform on AWS. You also receive timely support for application upgrades and patches, allowing you to stay current with the latest features and improvements. EDI on AWS is available with pay-as-you-go pricing in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (Paris), and South America (São Paulo). To learn more about EDI, visit the Product Detail page.