Amazon OpenSearch Service Expands Graviton4 Support
AWS announced in February 2026 that Amazon OpenSearch Service expanded support for Graviton4-based instance families, including c8g, m8g, r8g, and r8gd. The update added broader regional availability and gave more teams a practical path to move search clusters onto newer Arm hardware.
What Changed
According to AWS, the supported Graviton4 families now cover:
- c8g for compute-heavy indexing and query workloads
- m8g for general-purpose search clusters
- r8g / r8gd for memory-heavy OpenSearch domains
AWS positions these instances as offering up to 30 percent better performance than Graviton3 for the relevant workload classes.
Why It Matters
For OpenSearch users, this is less about a brand-new feature and more about deployment flexibility. Teams standardizing on Graviton for application tiers can now extend that choice deeper into the search layer, reducing architecture sprawl and improving price-performance consistency across environments.
Operational Considerations
Before migrating production domains:
- confirm plugin compatibility
- benchmark shard allocation and heap usage on the new instance family
- review region-by-region availability for disaster recovery plans
- validate snapshot, restore, and scaling workflows on the target Graviton4 nodes
For AWS teams already running search-heavy workloads, the February 2026 OpenSearch update makes Graviton4 a more realistic default choice than it was in late 2025.
Talk to the engineer who will own your stack.
No account managers, no offshore handoff. Senior DevOps, direct. Tell us what you are dealing with and you get a straight answer.
Related News
On July 30 AWS Quietly Trims a Dozen Services and Walking Back Its Own AI Bets Is the Real Story
On June 30, 2026, AWS closed roughly a dozen services to new customers effective July 30, and the list is mostly its own first-generation AI and search products: Kendra, Q Business, and Bedrock Agents, now renamed Classic. But retire means three different things in this announcement, maintenance mode where existing customers keep running fully supported, sunset with a real end-of-support date, and already ended. This sorts every service into its bucket, explains why the AI cull is a consolidation onto Bedrock rather than a retreat, and covers the two migrations that need actual work: WorkSpaces PCoIP to DCV by October 2027, and Kendra to Bedrock Knowledge Bases.
CloudThe Node.js 20 Lambda Deadline Everyone Is Citing Is Wrong and the Real Risk Already Started
The AWS Lambda Node.js 20 deadline everyone is citing, August 31 and September 30, 2026, is out of date. AWS moved the block-create date to February 1, 2027 and block-update to March 3, 2027. But the number that matters is April 30, 2026, when the Node.js 20 runtime stopped getting language security patches. This covers what each date really means, the OS-versus-runtime patching nuance most guides miss, a one-command way to find every affected function, and the safe migration to nodejs22.x or nodejs24.x.
CloudAzure Returns 410 Gone for GPT-4o on October 1 and Auto-Upgrade Skips the Deployments That Matter
On October 1, 2026, Azure OpenAI in Microsoft Foundry retires the GA gpt-4o (2024-11-20) and gpt-4o-mini (2024-07-18) versions, after which calls to a retired deployment return HTTP 410 Gone. Standard-family deployments are auto-upgraded region by region, but Provisioned (PTU) deployments and anything set to NoAutoUpgrade are not, and Microsoft says the date is not extendable.