Trending

#AmazonOpensearchService

Latest posts tagged with #AmazonOpensearchService on Bluesky

Posts tagged #AmazonOpensearchService

Preview
Amazon OpenSearch Service now supports Graviton4 based i8ge instances Amazon OpenSearch Service now supports i8ge instances, which is the latest generation of storage optimized instances offering the best performance for storage-intensive workloads. Powered by AWS Graviton4 processors, I8ge instances deliver up to 60% better compute performance compared to previous generation Graviton2-based storage optimized Im4gn instances. I8ge instances use the latest third generation AWS Nitro SSDs, local NVMe storage that deliver up to 55% better real-time storage performance per TB while offering up to 60% lower storage I/O latency and up to 75% lower storage I/O latency variability compared to previous generation Im4gn instances. Built on the AWS Nitro System, these instances offload CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads. I8ge instances are available of sizes up to 18xlarge and 45 TB instance storage. At 112.5 Gbps, these instances have the highest networking bandwidth among storage optimized instances available in Amazon OpenSearch Service. I8ge instances support all OpenSearch versions & Elasticsearch (open source) versions 7.9 and 7.10. Amazon OpenSearch Service supports i8ge instances in following AWS Regions : US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), Europe (Ireland), Europe (Stockholm), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Singapore) and Asia Pacific (Sydney). For region specific availability & pricing, visit our pricing page. To learn more about Amazon OpenSearch Service and its capabilities, visit our product page.

🆕 Amazon OpenSearch Service now supports Graviton4-based i8ge instances, delivering up to 60% better compute and 55% better storage per TB, with lower latency and higher bandwidth. Available in multiple regions. For pricing, check AWS.

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service now supports Graviton4 based i8ge instances Amazon OpenSearch Service now supports i8ge instances, which is the latest generation of storage optimized instances offering the best performance for storage-intensive workloads. Powered by AWS Graviton4 processors, I8ge instances deliver up to 60% better compute performance compared to previous generation Graviton2-based storage optimized Im4gn instances. I8ge instances use the latest third generation AWS Nitro SSDs, local NVMe storage that deliver up to 55% better real-time storage performance per TB while offering up to 60% lower storage I/O latency and up to 75% lower storage I/O latency variability compared to previous generation Im4gn instances. Built on the https://aws.amazon.com/ec2/nitro/, these instances offload CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads. I8ge instances are available of sizes up to 18xlarge and 45 TB instance storage. At 112.5 Gbps, these instances have the highest networking bandwidth among storage optimized instances available in Amazon OpenSearch Service. I8ge instances support all OpenSearch versions & Elasticsearch (open source) versions 7.9 and 7.10. Amazon OpenSearch Service supports i8ge instances in following https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ : US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), Europe (Ireland), Europe (Stockholm), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Singapore) and Asia Pacific (Sydney). For region specific availability & pricing, visit our https://aws.amazon.com/opensearch-service/pricing/. To learn more about Amazon OpenSearch Service and its capabilities, visit our https://aws.amazon.com/opensearch-service/.

Amazon OpenSearch Service now supports Graviton4 based i8ge instances

Amazon OpenSearch Service now supports i8ge instances, which is the latest generation of storage optimized instances offering the best performance for storage-intensive workloads.

Powered ...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Service introduces agentic AI for log analytics Amazon OpenSearch Service now offers agentic AI capabilities that enable engineering and support teams to analyze log data through an agentic conversational interface. These agentic AI features help simplify log querying and accelerate incident investigations by allowing teams to interact with data using natural language, plan and initiate autonomous root cause analysis, and persist conversation as they navigate through their Observability workspace in OpenSearch UI. This launch introduces three key capabilities available at no additional cost (token-based usage limits apply). Agentic chat enables you to ask questions in natural language to analyze data, generate and iterate Piped Processing Language (PPL) queries in Discover, and analyze visualizations for insights. When deeper root cause analysis is needed, you can trigger the investigation agent to autonomously and iteratively plan for the investigation, execute queries, reflect on results, and then deliver structured root cause hypotheses ranked by likelihood with full transparency into its reasoning. With agent memory, you can seamlessly continue your conversation across different feature pages or in a new web session. You can use the agentic AI features in the following AWS Regions: Asia Pacific (Tokyo), Asia Pacific (Sydney), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Europe (Ireland), US East (N. Virginia), US East (Ohio), and US West (Oregon). To learn more, see Agentic AI in Amazon OpenSearch Service. For more information about Amazon OpenSearch Service, see the Amazon OpenSearch Service product page.

🆕 Amazon OpenSearch Service adds agentic AI for log analytics, enabling teams to query logs naturally, plan root cause analyses, and persist conversations. Available at no extra cost in select regions.

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service introduces agentic AI for log analytics Amazon OpenSearch Service now offers agentic AI capabilities that enable engineering and support teams to analyze log data through an agentic conversational interface. These agentic AI features help simplify log querying and accelerate incident investigations by allowing teams to interact with data using natural language, plan and initiate autonomous root cause analysis, and persist conversation as they navigate through their Observability workspace in OpenSearch UI. This launch introduces three key capabilities available at no additional cost (token-based usage limits apply). Agentic chat enables you to ask questions in natural language to analyze data, generate and iterate Piped Processing Language (PPL) queries in Discover, and analyze visualizations for insights. When deeper root cause analysis is needed, you can trigger the investigation agent to autonomously and iteratively plan for the investigation, execute queries, reflect on results, and then deliver structured root cause hypotheses ranked by likelihood with full transparency into its reasoning. With agent memory, you can seamlessly continue your conversation across different feature pages or in a new web session. You can use the agentic AI features in the following AWS Regions: Asia Pacific (Tokyo), Asia Pacific (Sydney), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Europe (Ireland), US East (N. Virginia), US East (Ohio), and US West (Oregon). To learn more, see https://docs.aws.amazon.com/opensearch-service/latest/developerguide/application-ai-assistant.html. For more information about Amazon OpenSearch Service, see the https://aws.amazon.com/opensearch-service/.

Amazon OpenSearch Service introduces agentic AI for log analytics

Amazon OpenSearch Service now offers agentic AI capabilities that enable engineering and support teams to analyze log data through an agentic conversational interface. These agentic AI features hel...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Access Cluster Insights through the Amazon OpenSearch Service Console and Amazon EventBridge events Amazon OpenSearch Service extends access to Cluster Insights through the AWS Management Console, in addition to the existing OpenSearch UI Dashboards. This launch makes it easier to review performance and resilience recommendations and make necessary configuration changes, all within the same Console. In addition, Cluster Insights now publishes insights as events to Amazon EventBridge. Cluster insights presents curated insights of a cluster’s operational health along with actionable recommendations to help prevent issues before they affect the stability or performance of the cluster. You can continue to use OpenSearch UI Dashboards for more detailed metrics, including index and shard-level data and top-N query analysis. In addition, with this release, you can monitor insights through Amazon EventBridge events. Cluster Insights is available at no additional cost for OpenSearch versions 2.17 or later in all Regions where OpenSearch Service is available. View the complete list of supported Regions here. To learn more about Cluster Insights, refer to our technical documentation.

🆕 Amazon OpenSearch Service now offers Cluster Insights via the Console and EventBridge events, simplifying performance reviews and resilience recommendations. Insights are free for OpenSearch 2.17+ in all supported regions. Use OpenSearch UI for detailed metrics.

#AWS #AmazonOpensearchService

0 0 0 0
Access Cluster Insights through the Amazon OpenSearch Service Console and Amazon EventBridge events Amazon OpenSearch Service extends access to Cluster Insights through the AWS Management Console, in addition to the existing OpenSearch UI Dashboards. This launch makes it easier to review performance and resilience recommendations and make necessary configuration changes, all within the same Console. In addition, Cluster Insights now publishes insights as events to Amazon EventBridge. Cluster insights presents curated insights of a cluster’s operational health along with actionable recommendations to help prevent issues before they affect the stability or performance of the cluster. You can continue to use OpenSearch UI Dashboards for more detailed metrics, including index and shard-level data and top-N query analysis. In addition, with this release, you can monitor insights through Amazon EventBridge events. Cluster Insights is available at no additional cost for OpenSearch versions 2.17 or later in all Regions where OpenSearch Service is available. View the complete list of supported Regions https://docs.aws.amazon.com/opensearch-service/latest/developerguide/opensearch-ui-endpoints-quotas.html. To learn more about Cluster Insights, refer to our https://docs.aws.amazon.com/opensearch-service/latest/developerguide/cluster-insights.html.

Access Cluster Insights through the Amazon OpenSearch Service Console and Amazon EventBridge events

Amazon OpenSearch Service extends access to Cluster Insights through the AWS Management Console, in addition to the existing OpenSearch UI Dashboards. This launch ...

#AWS #AmazonOpensearchService

0 0 0 0
AWS Weekly Roundup: Amazon EC2 M8azn instances, new open weights models in Amazon Bedrock, and more (February 16, 2026) I joined AWS in 2021, and since then I’ve watched the Amazon Elastic Compute Cloud (Amazon EC2) instance family grow at a pace that still surprises me. From AWS Graviton-powered instances to specialized accelerated computing options, it feels like every few months there’s a new instance type landing that pushes performance boundaries further. As of […]

AWS Weekly Roundup: Amazon EC2 M8azn instances, new open weights models in Amazon Bedrock, and more (February 16, 2026)

I joined AWS in 2021, and since then I’ve watched the Amazon Elastic ...

#AWS #AmazonBedrock #AmazonElasticKubernetesService #AmazonOpensearchService #AmazonRds #WeekInReview

0 0 0 0
Preview
Amazon OpenSearch Service now supports OpenSearch version 3.5 You can now run OpenSearch version 3.5 on Amazon OpenSearch Service. OpenSearch 3.5 introduces significant improvements in agentic AI capabilities, search relevance tooling, and observability features to help you build powerful agentic applications. With this launch, agentic conversation memory captures conversation context and tool reasoning in persistent storage, enabling your agents to provide coherent, accurate responses across multi-turn conversations. In addition to this, context management optimizes what you send to large language models (LLMs) through automatic truncation and summarization, reducing your token costs while maintaining response quality. Finally a redesigned no-code agent interface supports Model Context Protocol (MCP) integration, search templates, conversational memory, and single model configurations, allowing you to build sophisticated agents without writing code. You can now tune search quality faster with expanded search relevance workbench capabilities. LLM-powered evaluation automatically assesses search results with customizable prompts, letting you scale relevance testing beyond manual judgments and accelerate quality improvements. Scheduled experiments run tests nightly, weekly, or monthly, helping you track search quality trends over time and catch regressions early. Enhanced single query comparison displays agentic search queries alongside agent summaries, making it easier to validate and optimize agent-driven search experiences. For information on upgrading to OpenSearch 3.5, please see the documentation. OpenSearch 3.5 is now available in all AWS Regions where Amazon OpenSearch Service is available.

🆕 Amazon OpenSearch Service adds OpenSearch 3.5, boosting agentic AI, search relevance, and observability. New features include conversation memory, context management, and a revamped no-code agent interface. Enhanced search relevance workbench and LLM-powered evalua…

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service now supports OpenSearch version 3.5 You can now run OpenSearch version 3.5 on Amazon OpenSearch Service. OpenSearch 3.5 introduces significant improvements in agentic AI capabilities, search relevance tooling, and observability features to help you build powerful agentic applications. With this launch, https://docs.opensearch.org/latest/ml-commons-plugin/api/agent-apis/execute-agent/ captures conversation context and tool reasoning in persistent storage, enabling your agents to provide coherent, accurate responses across multi-turn conversations. In addition to this, https://docs.opensearch.org/latest/ml-commons-plugin/context-management optimizes what you send to large language models (LLMs) through automatic truncation and summarization, reducing your token costs while maintaining response quality. Finally a redesigned no-code agent interface supports Model Context Protocol (MCP) integration, search templates, conversational memory, and single model configurations, allowing you to build sophisticated agents without writing code. You can now tune search quality faster with expanded https://docs.opensearch.org/latest/search-plugins/search-relevance/using-search-relevance-workbench/ capabilities. LLM-powered evaluation automatically assesses search results with customizable prompts, letting you scale relevance testing beyond manual judgments and accelerate quality improvements. Scheduled experiments run tests nightly, weekly, or monthly, helping you track search quality trends over time and catch regressions early. Enhanced single query comparison displays agentic search queries alongside agent summaries, making it easier to validate and optimize agent-driven search experiences. For information on upgrading to OpenSearch 3.5, please see the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html. OpenSearch 3.5 is now available in all AWS Regions where Amazon OpenSearch Service is available.

Amazon OpenSearch Service now supports OpenSearch version 3.5

You can now run OpenSearch version 3.5 on Amazon OpenSearch Service. OpenSearch 3.5 introduces significant improvements in agentic AI capabilities, search relevance tooling, and observability features ...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
OpenSearch UI supports Cross Account Data Access to OpenSearch domains Amazon OpenSearch Service now supports cross-account data access, enabling users to access OpenSearch domains hosted in different AWS accounts from within a single OpenSearch UI application. With this feature, you can query or build dashboard with data from OpenSearch domains across different accounts in the same region - without switching to a new endpoint or replicating data. Cross-account data access is available for OpenSearch domains hosted in both public and Virtual Private Cloud (VPC) configurations. With cross-account data access, teams no longer need to consolidate data into a single account or maintain costly data pipelines to enable unified analysis across organizational boundaries. This makes it easier to build centralized observability, search, and security analytics workflows that span multiple AWS accounts while keeping data in place and maintaining each account's access controls. Cross-account data access supports both IAM (including SAML via IAM federation) and IAM Identity Center (IdC) for end user authentication. Cross-account data access to OpenSearch domains is available in all AWS Regions where OpenSearch UI is available. To learn more, see Cross-account data access to OpenSearch domains in the Amazon OpenSearch Service Developer Guide.

🆕 Amazon OpenSearch Service now supports cross-account data access, enabling unified analysis across accounts via OpenSearch UI without data replication or costly pipelines, available in all regions where OpenSearch UI is supported.

#AWS #AmazonOpensearchService

0 0 0 0
OpenSearch UI supports Cross Account Data Access to OpenSearch domains Amazon OpenSearch Service now supports cross-account data access, enabling users to access OpenSearch domains hosted in different AWS accounts from within a single OpenSearch UI application. With this feature, you can query or build dashboard with data from OpenSearch domains across different accounts in the same region - without switching to a new endpoint or replicating data. Cross-account data access is available for OpenSearch domains hosted in both public and Virtual Private Cloud (VPC) configurations. With cross-account data access, teams no longer need to consolidate data into a single account or maintain costly data pipelines to enable unified analysis across organizational boundaries. This makes it easier to build centralized observability, search, and security analytics workflows that span multiple AWS accounts while keeping data in place and maintaining each account's access controls. Cross-account data access supports both IAM (including SAML via IAM federation) and IAM Identity Center (IdC) for end user authentication. Cross-account data access to OpenSearch domains is available in all AWS Regions where OpenSearch UI is available. To learn more, see https://docs.aws.amazon.com/opensearch-service/latest/developerguide/application-cross-account-data-access-domains.html in the Amazon OpenSearch Service Developer Guide.

OpenSearch UI supports Cross Account Data Access to OpenSearch domains

Amazon OpenSearch Service now supports cross-account data access, enabling users to access OpenSearch domains hosted in different AWS accounts from within a single OpenSearch UI application. W...

#AWS #AmazonOpensearchService

0 1 0 0
Preview
Amazon OpenSearch Service now supports in-place volume increases for all volume sizes Amazon OpenSearch Service now extends in-place cluster volume size increases to volumes exceeding 3 TiB. With this enhancement, you can scale storage capacity across all volume sizes without requiring a blue/green deployment. Previously, you could perform volume increases up to 3 TiB on your clusters without a blue/green deployment. This release removes that limitation, making it easier for you to scale up quickly even beyond 3 TiB when required. Domains that already have a volume size above 3 TiB will require a blue/green deployment the first time a volume increase is made; subsequent volume increases will not require a blue/green deployment. Decreasing storage volume size, or making volume increases within short intervals, will still require a blue/green deployment. You can use the dry-run option to check whether your change requires a blue/green deployment. This feature is available in all AWS Commercial and AWS GovCloud (US) Regions where Amazon OpenSearch Service is available. See here for a full list of our Regions. To learn more about Amazon OpenSearch Service configurations, visit the documentation page.

🆕 Amazon OpenSearch Service lets you scale volumes over 3 TiB in-place, simplifying growth without blue/green deployments. For smaller volumes, a blue/green deployment is needed initially. Available in all regions where OpenSearch Service operates.

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service now supports in-place volume increases for all volume sizes https://aws.amazon.com/opensearch-service/ now extends in-place cluster volume size increases to volumes exceeding 3 TiB. With this enhancement, you can scale storage capacity across all volume sizes without requiring a blue/green deployment. Previously, you could perform volume increases up to 3 TiB on your clusters without a blue/green deployment. This release removes that limitation, making it easier for you to scale up quickly even beyond 3 TiB when required. Domains that already have a volume size above 3 TiB will require a blue/green deployment the first time a volume increase is made; subsequent volume increases will not require a blue/green deployment. Decreasing storage volume size, or making volume increases within short intervals, will still require a blue/green deployment. You can use the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-configuration-changes.html#dryrun option to check whether your change requires a blue/green deployment. This feature is available in all AWS Commercial and AWS GovCloud (US) Regions where Amazon OpenSearch Service is available. See https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ for a full list of our Regions. To learn more about Amazon OpenSearch Service configurations, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-configuration-changes.html.

Amazon OpenSearch Service now supports in-place volume increases for all volume sizes

https://aws.amazon.com/opensearch-service/ now extends in-place cluster volume size increases to volumes exceeding 3 TiB. With this enhancement, you can scale storage capacity a...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
OpenSearch OR2 and OM2 instances in AWS GovCloud (US-East, US-West) Regions Amazon OpenSearch Service, expands availability of OR2 and OM2, OpenSearch Optimized Instance family to 12 additional regions. The OR2 instance delivers up to 26% higher indexing throughput compared to previous OR1 instances and 70% over R7g instances. The OM2 instance delivers up to 15% higher indexing throughput compared to OR1 instances and 66% over M7g instances in internal benchmarks The OpenSearch Optimized instances, leveraging best-in-class cloud technologies like Amazon S3, to provide high durability, and improved price-performance for higher indexing throughput better for indexing heavy workload. Each OpenSearch Optimized instance is provisioned with compute, local instance storage for caching, and remote Amazon S3-based managed storage. OR2 and OM2 offers pay-as-you-go pricing and reserved instances, with a simple hourly rate for the instance, local instance storage, as well as the managed storage provisioned. OR2 instances come in sizes ‘medium’ through ‘16xlarge’, and offer compute, memory, and storage flexibility. OM2 instances come in sizes ‘large’ through ‘16xlarge’ Please refer to the Amazon OpenSearch Service pricing page for pricing details. OR2 and OM2 instance family is now available on Amazon OpenSearch Service across 2 additional regions: AWS GovCloud (US-East, US-West).

🆕 Amazon OpenSearch Service now offers OR2 and OM2 instances in AWS GovCloud (US-East, US-West), providing up to 26% higher indexing throughput than OR1 and 70% over R7g instances, with pay-as-you-go and reserved pricing.

#AWS #AmazonOpensearchService

0 0 0 0
OpenSearch OR2 and OM2 instances in AWS GovCloud (US-East, US-West) Regions Amazon OpenSearch Service, expands availability of OR2 and OM2, OpenSearch Optimized Instance family to 12 additional regions. The OR2 instance delivers up to 26% higher indexing throughput compared to previous OR1 instances and 70% over R7g instances. The OM2 instance delivers up to 15% higher indexing throughput compared to OR1 instances and 66% over M7g instances in internal benchmarks The OpenSearch Optimized instances, leveraging best-in-class cloud technologies like Amazon S3, to provide high durability, and improved price-performance for higher indexing throughput better for indexing heavy workload. Each OpenSearch Optimized instance is provisioned with compute, local instance storage for caching, and remote Amazon S3-based managed storage. OR2 and OM2 offers pay-as-you-go pricing and reserved instances, with a simple hourly rate for the instance, local instance storage, as well as the managed storage provisioned. OR2 instances come in sizes ‘medium’ through ‘16xlarge’, and offer compute, memory, and storage flexibility. OM2 instances come in sizes ‘large’ through ‘16xlarge’ Please refer to the Amazon OpenSearch Service https://aws.amazon.com/opensearch-service/pricing/ for pricing details. OR2 and OM2 instance family is now available on Amazon OpenSearch Service across 2 additional regions: AWS GovCloud (US-East, US-West).

OpenSearch OR2 and OM2 instances in AWS GovCloud (US-East, US-West) Regions

Amazon OpenSearch Service, expands availability of OR2 and OM2, OpenSearch Optimized Instance family to 12 additional regions. The OR2 instance delivers up to 26% higher indexing throughp...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Service introduces capacity optimized blue/green deployments Amazon OpenSearch Service now offers a Capacity Optimized option for blue/green deployments, ensuring domain updates can complete even when available instance capacity is less than required. Updates are performed in incremental batches, reducing the number of additional instances needed during the process. Amazon OpenSearch Service uses a blue/green deployment process when updating domains — creating an idle copy of the original environment, applying updates, and routing traffic to the new environment once complete. This minimizes downtime and preserves the original environment as a fallback. Until now, blue/green deployments required 100% instance capacity upfront. For example, for a cluster with 100 data nodes, another 100 nodes were needed to proceed. If sufficient capacity was unavailable, customers had to wait and retry later. Now, customers can choose between two deployment strategies. The default Full Swap option maintains current behavior, requiring full capacity upfront for the fastest deployment. The new Capacity Optimized option attempts a full capacity deployment first, but automatically falls back to batch deployment if capacity is insufficient. OpenSearch Service determines the appropriate batch size based on cluster size and available instances. Because updates are applied in batches, this option may take longer than a full-swap deployment. Customers can select their preferred option in the deployment configuration settings via the OpenSearch Service console or API. We recommend choosing the Capacity Optimized deployment option for clusters with 30 or more nodes. The Capacity Optimized option is available for all OpenSearch and Elasticsearch versions, across all AWS Commercial Regions where OpenSearch Service is available. See here for a full listing of our Regions. To learn more, visit the documentation page.

🆕 Amazon OpenSearch Service now supports Capacity Optimized blue/green deployments, allowing domain updates with insufficient capacity by applying changes in batches. This reduces extra instances and offers two strategies: Full Swap and Capacity Optimized.

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service introduces capacity optimized blue/green deployments https://aws.amazon.com/opensearch-service/ now offers a Capacity Optimized option for blue/green deployments, ensuring domain updates can complete even when available instance capacity is less than required. Updates are performed in incremental batches, reducing the number of additional instances needed during the process. Amazon OpenSearch Service uses a blue/green deployment process when updating domains — creating an idle copy of the original environment, applying updates, and routing traffic to the new environment once complete. This minimizes downtime and preserves the original environment as a fallback. Until now, blue/green deployments required 100% instance capacity upfront. For example, for a cluster with 100 data nodes, another 100 nodes were needed to proceed. If sufficient capacity was unavailable, customers had to wait and retry later. Now, customers can choose between two deployment strategies. The default Full Swap option maintains current behavior, requiring full capacity upfront for the fastest deployment. The new Capacity Optimized option attempts a full capacity deployment first, but automatically falls back to batch deployment if capacity is insufficient. OpenSearch Service determines the appropriate batch size based on cluster size and available instances. Because updates are applied in batches, this option may take longer than a full-swap deployment. Customers can select their preferred option in the deployment configuration settings via the OpenSearch Service console or API. We recommend choosing the Capacity Optimized deployment option for clusters with 30 or more nodes. The Capacity Optimized option is available for all OpenSearch and Elasticsearch versions, across all AWS Commercial Regions where OpenSearch Service is available. See https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ for a full listing of our Regions. To learn more, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-configuration-changes.html.

Amazon OpenSearch Service introduces capacity optimized blue/green deployments

https://aws.amazon.com/opensearch-service/ now offers a Capacity Optimized option for blue/green deployments, ensuring domain updates can complete even when available instance capacity...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Ingestion now supports unified ingestion endpoint for OpenTelemetry data Amazon OpenSearch Ingestion now supports a unified ingestion endpoint that can accept all three OpenTelemetry observability signals — logs, metrics, and traces — through a single pipeline. Previously, customers who wanted to ingest all three OpenTelemetry data types had to create and manage three separate pipelines, one for each signal type. With this launch, a single pipeline can now receive any combination of OpenTelemetry signals, simplifying pipeline architecture and reducing operational overhead. Customers can now build centralized observability pipelines that consolidate logs, metrics, and traces in one place, making it easier to correlate signals and gain a holistic view of application health. Teams operating at scale can reduce the number of pipelines they manage, lowering infrastructure costs and simplifying access control, monitoring, and lifecycle management. This also makes it easier to adopt OpenTelemetry incrementally as teams can begin with one signal type and add others over time without any pipeline reconfiguration. The unified ingestion endpoint for OpenTelemetry data is supported in all regions that Amazon OpenSearch Ingestion is currently available. Customers can get started by using the new unified OpenTelemetry source in their pipeline configuration via the AWS Management console or using the AWS CLI and point their OpenTelemetry clients to the new unified endpoint. To learn more and get started, visit the Amazon OpenSearch Ingestion documentation.

🆕 Amazon OpenSearch Ingestion offers a unified endpoint for OpenTelemetry logs, metrics, and traces, simplifying pipeline management and reducing costs. A single pipeline handles all signals, easing observability and incremental adoption. Available globally, it’s con…

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Ingestion now supports unified ingestion endpoint for OpenTelemetry data Amazon OpenSearch Ingestion now supports a unified ingestion endpoint that can accept all three OpenTelemetry observability signals — logs, metrics, and traces — through a single pipeline. Previously, customers who wanted to ingest all three OpenTelemetry data types had to create and manage three separate pipelines, one for each signal type. With this launch, a single pipeline can now receive any combination of OpenTelemetry signals, simplifying pipeline architecture and reducing operational overhead. Customers can now build centralized observability pipelines that consolidate logs, metrics, and traces in one place, making it easier to correlate signals and gain a holistic view of application health. Teams operating at scale can reduce the number of pipelines they manage, lowering infrastructure costs and simplifying access control, monitoring, and lifecycle management. This also makes it easier to adopt OpenTelemetry incrementally as teams can begin with one signal type and add others over time without any pipeline reconfiguration. The unified ingestion endpoint for OpenTelemetry data is supported in all regions that Amazon OpenSearch Ingestion is currently https://docs.aws.amazon.com/general/latest/gr/opensearch-service.html#opensearch-service-regions. Customers can get started by using the new unified OpenTelemetry source in their pipeline configuration via the AWS Management console or using the AWS CLI and point their OpenTelemetry clients to the new unified endpoint. To learn more and get started, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/configure-client-otel.html.

Amazon OpenSearch Ingestion now supports unified ingestion endpoint for OpenTelemetry data

Amazon OpenSearch Ingestion now supports a unified ingestion endpoint that can accept all three OpenTelemetry observability signals — logs, metrics, and traces — throug...

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus as a sink Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus  as a sink, making it possible to build fully managed, end-to-end metrics ingestion pipelines without any custom forwarding infrastructure. With this launch, customers can now manage their entire metrics ingestion workflow using the same pipeline infrastructure they already use for logs and traces. Customers can now choose the right destination for each observability signal — sending logs and traces to Amazon OpenSearch Service for powerful full-text search, log analytics, and trace correlation, while routing metrics to Amazon Managed Service for Prometheus for time-series storage and analysis. This flexibility allows teams to build purpose-fit observability pipelines that leverage the strengths of each service without compromising on data fidelity or analytical capability. Amazon OpenSearch Ingestion's built-in data transformation and enrichment capabilities allow customers to prepare and refine metrics before they land in Amazon Managed Service for Prometheus, improving data quality and consistency. Once metrics are in Amazon Managed Service for Prometheus, customers can query them using Prometheus Query Language to analyze trends, configure alerting rules to get notified when metrics cross defined thresholds, and visualize their data using Amazon Managed Grafana for rich, customizable views of infrastructure and application health. The feature is supported in all regions that Amazon OpenSearch Ingestion and  is currently https://docs.aws.amazon.com/general/latest/gr/opensearch-service.html#opensearch-service-regions. Customers can get started by using the new sink for Amazon Managed Service for Prometheus in their pipeline configuration via the AWS Management console or using the AWS CLI and start ingesting metrics into their Amazon Managed Service for Prometheus workspace. To learn more and get started, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/configure-client-prometheus.html.

Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus as a sink

Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus  as a sink, making it possible to build fully managed, end-to-end metrics ingestion pipelines ...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus as a sink Amazon OpenSearch Ingestion now supports Amazon Managed Service for Prometheus  as a sink, making it possible to build fully managed, end-to-end metrics ingestion pipelines without any custom forwarding infrastructure. With this launch, customers can now manage their entire metrics ingestion workflow using the same pipeline infrastructure they already use for logs and traces. Customers can now choose the right destination for each observability signal — sending logs and traces to Amazon OpenSearch Service for powerful full-text search, log analytics, and trace correlation, while routing metrics to Amazon Managed Service for Prometheus for time-series storage and analysis. This flexibility allows teams to build purpose-fit observability pipelines that leverage the strengths of each service without compromising on data fidelity or analytical capability. Amazon OpenSearch Ingestion's built-in data transformation and enrichment capabilities allow customers to prepare and refine metrics before they land in Amazon Managed Service for Prometheus, improving data quality and consistency. Once metrics are in Amazon Managed Service for Prometheus, customers can query them using Prometheus Query Language to analyze trends, configure alerting rules to get notified when metrics cross defined thresholds, and visualize their data using Amazon Managed Grafana for rich, customizable views of infrastructure and application health. The feature is supported in all regions that Amazon OpenSearch Ingestion and  is currently available. Customers can get started by using the new sink for Amazon Managed Service for Prometheus in their pipeline configuration via the AWS Management console or using the AWS CLI and start ingesting metrics into their Amazon Managed Service for Prometheus workspace. To learn more and get started, visit the Amazon OpenSearch Ingestion documentation.

🆕 Amazon OpenSearch Ingestion supports Amazon Managed Service for Prometheus as a sink, creating fully managed metrics pipelines without custom infrastructure. Route metrics and logs for enhanced observability, transformation, and analysis. Available globally. More d…

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Service adds new insights for improved cluster stability Amazon OpenSearch Service has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides instant visibility into shard imbalances that cause uneven workload distribution, while Cluster Overload surfaces elevated cluster resource utilization that can lead to request throttling or rejections. Both insights come with details of affected resources along with actionable mitigation recommendations. Previously, identifying resource constraints and shard imbalances required manually correlating multiple metrics and logs, making it difficult to detect issues early. With these new insights, you can proactively monitor cluster health and take timely action. Suboptimal Sharding Strategy detects shard imbalances caused by indices with too few shards relative to the number of data nodes, or by shards carrying disproportionately large amounts of data compared to others. It identifies the root cause of uneven workload distribution and provides recommendations to help you achieve optimal shard distribution for improved query performance and resource utilization. Similarly, Cluster Overload helps you identify elevated resource utilization, including CPU, memory, disk I/O, disk throughput, and disk utilization that can potentially lead to request throttling or rejections. It also provides scale-up recommendations so you can take timely action to protect your critical workloads. These new insights are available at no additional cost for OpenSearch version 2.17 or later in all Regions where the OpenSearch UI is available. See the complete list of supported Regions here. To learn more, visit the Cluster Insights documentation or view the complete catalog of available insights.

🆕 Amazon OpenSearch Service now offers Cluster Overload and Suboptimal Sharding Strategy insights for improved cluster stability, detecting resource issues and shard imbalances with actionable recommendations at no extra cost for OpenSearch version 2.17+.

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service adds new insights for improved cluster stability https://aws.amazon.com/opensearch-service/ has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides instant visibility into shard imbalances that cause uneven workload distribution, while Cluster Overload surfaces elevated cluster resource utilization that can lead to request throttling or rejections. Both insights come with details of affected resources along with actionable mitigation recommendations. Previously, identifying resource constraints and shard imbalances required manually correlating multiple metrics and logs, making it difficult to detect issues early. With these new insights, you can proactively monitor cluster health and take timely action. Suboptimal Sharding Strategy detects shard imbalances caused by indices with too few shards relative to the number of data nodes, or by shards carrying disproportionately large amounts of data compared to others. It identifies the root cause of uneven workload distribution and provides recommendations to help you achieve optimal shard distribution for improved query performance and resource utilization. Similarly, Cluster Overload helps you identify elevated resource utilization, including CPU, memory, disk I/O, disk throughput, and disk utilization that can potentially lead to request throttling or rejections. It also provides scale-up recommendations so you can take timely action to protect your critical workloads. These new insights are available at no additional cost for OpenSearch version 2.17 or later in all Regions where the OpenSearch UI is available. See the complete list of supported Regions https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. To learn more, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/cluster-insights.html or view the complete https://docs.aws.amazon.com/opensearch-service/latest/developerguide/insights-catalog.html.

Amazon OpenSearch Service adds new insights for improved cluster stability

https://aws.amazon.com/opensearch-service/ has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides ...

#AWS #AmazonOpensearchService

0 0 0 0
Preview
Amazon OpenSearch Service expands support for Graviton4 (c8g,m8g & r8g ) instances Amazon OpenSearch Service expands support for the latest generation Graviton4-based Amazon EC2 instance families. These new instance types are compute optimized (c8g), general purpose (m8g), and memory optimized (r8g, r8gd) instances. AWS Graviton4 processors provide up to 30% better performance than AWS Graviton3 processors with c8g, m8g and r8g & r8gd offering the best price performance for compute-intensive, general purpose, and memory-intensive workloads respectively. To learn more about Graviton4 improvements, please see the blog on r8g instances and the blog on c8g & m8g instances. Amazon OpenSearch Service Graviton4 instances are supported for all OpenSearch versions, and Elasticsearch (open source) versions 7.9 and 7.10. Apart from the regions already supported, one or more than one Graviton4 instance types are now also available in following region: Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Melbourne), Asia Pacific (Osaka), Asia Pacific (Thailand), Europe (Milan), Europe (Paris), Europe (Zurich), Middle East (UAE), AWS GovCloud (US-West) and AWS GovCloud (US-East). For region specific availability & pricing, visit our pricing page. To learn more about Amazon OpenSearch Service and its capabilities, visit our product page.

🆕 Amazon OpenSearch now supports Graviton4 instances (c8g, m8g, r8g), offering up to 30% better performance than Graviton3 for compute-intensive tasks. Available in new regions like Asia Pacific and Europe. Check AWS pricing page for details.

#AWS #AmazonOpensearchService #AwsGovcloudUs

0 0 0 0
Preview
Amazon OpenSearch Service now supports storage optimized i7i instances Amazon OpenSearch Service now supports latest generation x86 based high performance Storage Optimized i7i instances. Powered by 5th generation Intel Xeon Scalable processors, I7i instances deliver up to 23% better compute performance and more than 10% better price performance over previous generation I4i instances. I7i instances have 3rd generation AWS Nitro SSDs with up to 50% better real-time storage performance, up to 50% lower storage I/O latency, and up to 60% lower storage I/O latency variability compared to I4i instances. Built on the AWS Nitro System, these instances offload CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads. Amazon OpenSearch Service supports i7i instances in following AWS Regions US East (N. Virginia, Ohio), US West (N. California, Oregon), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Spain, Stockholm, Zurich ), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo), Middle East (UAE), South America (São Paulo) & AWS GovCloud (US-West). For region specific availability & pricing, visit our pricing page. To learn more about Amazon OpenSearch Service and its capabilities, visit our product page.

🆕 Amazon OpenSearch Service now supports high-performance i7i instances with better compute and storage performance, lower latency, and enhanced security, available in multiple global regions. For pricing, visit our page.

#AWS #AmazonOpensearchService #AwsGovcloudUs

0 0 0 0
Amazon OpenSearch Service now supports storage optimized i7i instances Amazon OpenSearch Service now supports latest generation x86 based high performance Storage Optimized i7i instances. Powered by 5th generation Intel Xeon Scalable processors, I7i instances deliver up to 23% better compute performance and more than 10% better price performance over previous generation I4i instances. I7i instances have 3rd generation AWS Nitro SSDs with up to 50% better real-time storage performance, up to 50% lower storage I/O latency, and up to 60% lower storage I/O latency variability compared to I4i instances. Built on the https://aws.amazon.com/ec2/nitro/, these instances offload CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads. Amazon OpenSearch Service supports i7i instances in following https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ US East (N. Virginia, Ohio), US West (N. California, Oregon), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Spain, Stockholm, Zurich ), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo), Middle East (UAE), South America (São Paulo) & AWS GovCloud (US-West). For region specific availability & pricing, visit our https://aws.amazon.com/opensearch-service/pricing/. To learn more about Amazon OpenSearch Service and its capabilities, visit our https://aws.amazon.com/opensearch-service/.

Amazon OpenSearch Service now supports storage optimized i7i instances

Amazon OpenSearch Service now supports latest generation x86 based high performance Storage Optimized i7i instances. Powered by 5th generation Intel Xeon Scalable processors, ...

#AWS #AmazonOpensearchService #AwsGovcloudUs

0 0 0 0
Amazon OpenSearch Service expands support for Graviton4 (c8g,m8g & r8g ) instances Amazon OpenSearch Service expands support for the latest generation Graviton4-based Amazon EC2 instance families. These new instance types are compute optimized (c8g), general purpose (m8g), and memory optimized (r8g, r8gd) instances. AWS Graviton4 processors provide up to 30% better performance than AWS Graviton3 processors with c8g, m8g and r8g & r8gd offering the best price performance for compute-intensive, general purpose, and memory-intensive workloads respectively. To learn more about Graviton4 improvements, please see the https://aws.amazon.com/blogs/aws/aws-graviton4-based-amazon-ec2-r8g-instances-best-price-performance-in-amazon-ec2/ on r8g instances and the https://aws.amazon.com/blogs/aws/run-your-compute-intensive-and-general-purpose-workloads-sustainably-with-the-new-amazon-ec2-c8g-m8g-instances/ on c8g & m8g instances. Amazon OpenSearch Service Graviton4 instances are supported for all OpenSearch versions, and Elasticsearch (open source) versions 7.9 and 7.10. Apart from the regions already supported, one or more than one Graviton4 instance types are now also available in following region: Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Melbourne), Asia Pacific (Osaka), Asia Pacific (Thailand), Europe (Milan), Europe (Paris), Europe (Zurich), Middle East (UAE), AWS GovCloud (US-West) and AWS GovCloud (US-East). For region specific availability & pricing, visit our https://aws.amazon.com/opensearch-service/pricing/. To learn more about Amazon OpenSearch Service and its capabilities, visit our https://aws.amazon.com/opensearch-service/.

Amazon OpenSearch Service expands support for Graviton4 (c8g,m8g & r8g ) instances

Amazon OpenSearch Service expands support for the latest generation Graviton4-based Amazon EC2 instance families. These new instance types are compute optimized (c8g...

#AWS #AmazonOpensearchService #AwsGovcloudUs

0 0 0 0
AWS Weekly Roundup: Amazon EC2 M8azn instances, new open weights models in Amazon Bedrock, and more (February 16, 2026) I joined AWS in 2021, and since then I’ve watched the Amazon Elastic Compute Cloud (Amazon EC2) instance family grow at a pace that still surprises me. From AWS Graviton-powered instances to specialized accelerated computing options, it feels like every few months there’s a new instance type landing that pushes performance boundaries further. As of […]

AWS Weekly Roundup: Amazon EC2 M8azn instances, new open weights models in Amazon Bedrock, and more (February 16, 2026)

I joined AWS in 2021, and since then I’ve watched the Amazon Elastic ...

#AWS #AmazonBedrock #AmazonElasticKubernetesService #AmazonOpensearchService #AmazonRds #WeekInReview

0 0 0 0
Amazon OpenSearch Serverless now supports Collection Groups Amazon OpenSearch Serverless now supports Collection Groups, a new capability that enables you to share OpenSearch Compute Units (OCUs) across collections with different AWS KMS keys. This new capability delivers enhanced cost optimization through a shared compute model that reduces overall OCU expenses while maintaining collection-level security and access controls. Additionally, Collection Groups introduce the ability to specify minimum OCU allocations alongside maximum OCU limits, allowing you to provision compute capacity upfront at startup for more predictable performance. Collection Groups are particularly valuable for multi-tenant workloads where different tenants require data encryption with separate KMS keys while still benefiting from shared compute resources. By grouping collections together, you can optimize OCU utilization across workloads, reduce costs through resource sharing, and maintain the security isolation required by different encryption keys. The minimum OCU setting ensures your collections have guaranteed baseline capacity from the moment they start, eliminating cold start delays and providing consistent performance for latency-sensitive applications. Collection groups are available in all regions where Amazon OpenSearch Serverless is currently https://docs.aws.amazon.com/general/latest/gr/opensearch-service.html. To learn more about configuring and managing collection groups, visit the https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless-collection-groups.html.

Amazon OpenSearch Serverless now supports Collection Groups

Amazon OpenSearch Serverless now supports Collection Groups, a new capability that enables you to share OpenSearch Compute Units (OCUs) across collections with different AWS KMS keys. This new capability...

#AWS #AmazonOpensearchService

0 0 0 0
Amazon OpenSearch Service improves vector database performance and cost with GPU acceleration and auto-optimization Build and optimize large-scale vector databases up to 10 times faster and at a quarter of the cost with new GPU acceleration and auto-optimization capabilities that automatically balance search quality, speed, and resource usage.

Amazon OpenSearch Service improves vector database performance and cost with GPU acceleration and auto-optimization

Build and optimize large-scale vector databases up to 10 times faster and at a quarter of the cost with new GPU accelerati...

#AWS #AmazonOpensearchService #Analytics #Launch #News

0 0 0 0