Amazon Bedrock now supports NVIDIA Nemotron 3 Super, an open hybrid Mixture-of-Experts (MoE) model designed for complex multi-agent applications. Built for agentic workloads, Nemotron 3 Super delivers fast, and cost-efficient inference enabling AI agents to maintain focus and accuracy across long, multi-step tasks without losing context. Fully open with weights, datasets, and recipes, the model supports easy customization and secure deployment, making it well-suited for enterprises, startups, and individual developers building multi-agent workflows, and advanced reasoning applications.

Amazon Bedrock gives customers access to Nemotron 3 Super through a single, fully managed API — with no infrastructure to provision or models to host. Bedrock’s serverless inference, built-in security controls, and compatibility with OpenAI API specifications make it easy to integrate Nemotron 3 Super into existing workflows and deploy at production scale with confidence.

NVIDIA Nemotron 3 Super is now available in Amazon Bedrock across select AWS Regions. For the full list of available AWS Regions, refer to the documentation. To learn more and get started, visit the Amazon Bedrock console or the service documentation here. To get started with Amazon Bedrock OpenAI API-compatible service endpoints, visit documentation here.

 

​Amazon Bedrock now supports NVIDIA Nemotron 3 Super, an open hybrid Mixture-of-Experts (MoE) model designed for complex multi-agent applications. Built for agentic workloads, Nemotron 3 Super delivers fast, and cost-efficient inference enabling AI agents to maintain focus and accuracy across long, multi-step tasks without losing context. Fully open with weights, datasets, and recipes, the model supports easy customization and secure deployment, making it well-suited for enterprises, startups, and individual developers building multi-agent workflows, and advanced reasoning applications.
Amazon Bedrock gives customers access to Nemotron 3 Super through a single, fully managed API — with no infrastructure to provision or models to host. Bedrock’s serverless inference, built-in security controls, and compatibility with OpenAI API specifications make it easy to integrate Nemotron 3 Super into existing workflows and deploy at production scale with confidence.
NVIDIA Nemotron 3 Super is now available in Amazon Bedrock across select AWS Regions. For the full list of available AWS Regions, refer to the documentation. To learn more and get started, visit the Amazon Bedrock console or the service documentation here. To get started with Amazon Bedrock OpenAI API-compatible service endpoints, visit documentation here.  

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) M6in and M6idn instances are available in AWS London Region. These sixth-generation network optimized instances, powered by 3^rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances. Customers can use M6in and M6idn instances to scale their performance and throughput of network-intensive workloads such as high-performance file systems, distributed web scale in-memory caches, caching fleets, real-time big data analytics, and Telco applications such as 5G User Plane Function.

M6in and M6idn instances are available in 10 different instance sizes including metal, offering up to 128 vCPUs and 512 GiB of memory. They deliver up to 100Gbps of Amazon Elastic Block Store (EBS) bandwidth, and up to 400K IOPS. M6in and M6idn instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes. M6idn instances offer up to 7.6 TB of high-speed, low-latency instance storage.

With this regional expansion, M6in and M6idn instances are available in the following AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Ireland, Frankfurt, Spain, Stockholm, Zurich, London), Asia Pacific (Mumbai, Singapore, Tokyo, Sydney, Seoul), Canada (Central), and AWS GovCloud (US-West). Customers can purchase the new instances through Savings Plans, On-Demand, and Spot instances. To learn more, see M6in and M6idn instances page. 

 

​Starting today, Amazon Elastic Compute Cloud (Amazon EC2) M6in and M6idn instances are available in AWS London Region. These sixth-generation network optimized instances, powered by 3rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances. Customers can use M6in and M6idn instances to scale their performance and throughput of network-intensive workloads such as high-performance file systems, distributed web scale in-memory caches, caching fleets, real-time big data analytics, and Telco applications such as 5G User Plane Function.
M6in and M6idn instances are available in 10 different instance sizes including metal, offering up to 128 vCPUs and 512 GiB of memory. They deliver up to 100Gbps of Amazon Elastic Block Store (EBS) bandwidth, and up to 400K IOPS. M6in and M6idn instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes. M6idn instances offer up to 7.6 TB of high-speed, low-latency instance storage.
With this regional expansion, M6in and M6idn instances are available in the following AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Ireland, Frankfurt, Spain, Stockholm, Zurich, London), Asia Pacific (Mumbai, Singapore, Tokyo, Sydney, Seoul), Canada (Central), and AWS GovCloud (US-West). Customers can purchase the new instances through Savings Plans, On-Demand, and Spot instances. To learn more, see M6in and M6idn instances page.   

Amazon EC2 High Memory U7i instances with 6TB of memory (u7i-6tb.112xlarge) are now available in AWS Asia Pacific (Malaysia). U7i instances are part of AWS 7th generation and are powered by custom fourth generation Intel Xeon Scalable Processors (Sapphire Rapids). U7i-6tb instances offer 6TiB of DDR5 memory, enabling customers to scale transaction processing throughput in a fast-growing data environment.

U7i-6tb instances deliver 448 vCPUs with up to 100 Gbps of Amazon EBS bandwidth for faster data loading and backups, 100 Gbps of network bandwidth, and ENA Express. U7i instances are ideal for customers using mission-critical in-memory databases like SAP HANA, Oracle, and SQL Server.

To learn more about U7i instances, visit the High Memory instances page.

 

​Amazon EC2 High Memory U7i instances with 6TB of memory (u7i-6tb.112xlarge) are now available in AWS Asia Pacific (Malaysia). U7i instances are part of AWS 7th generation and are powered by custom fourth generation Intel Xeon Scalable Processors (Sapphire Rapids). U7i-6tb instances offer 6TiB of DDR5 memory, enabling customers to scale transaction processing throughput in a fast-growing data environment.
U7i-6tb instances deliver 448 vCPUs with up to 100 Gbps of Amazon EBS bandwidth for faster data loading and backups, 100 Gbps of network bandwidth, and ENA Express. U7i instances are ideal for customers using mission-critical in-memory databases like SAP HANA, Oracle, and SQL Server.
To learn more about U7i instances, visit the High Memory instances page.  

Amazon Elastic Container Registry (Amazon ECR) pull through cache now supports Chainguard’s registry as an upstream source. With today’s release, customers now benefit from the security and availability of Amazon ECR for private Chainguard images.

As customers continue to scale their use of Chainguard images, keeping them synchronized with Chainguard’s registry becomes increasingly important. With ECR’s pull through cache feature, customers can keep Chainguard images in sync without additional workflows or tools to manage. Amazon ECR’s pull through cache supports frequent registry syncs, helping to keep container images sourced from Chainguard up to date. Later, customers can apply ECR features such as image scanning and lifecycle policies to their cached Chainguard images.

The pull through cache for Chainguard is available in all AWS Regions where Amazon ECR pull through cache is supported. To get started, review our documentation.

 

​Amazon Elastic Container Registry (Amazon ECR) pull through cache now supports Chainguard’s registry as an upstream source. With today’s release, customers now benefit from the security and availability of Amazon ECR for private Chainguard images. As customers continue to scale their use of Chainguard images, keeping them synchronized with Chainguard’s registry becomes increasingly important. With ECR’s pull through cache feature, customers can keep Chainguard images in sync without additional workflows or tools to manage. Amazon ECR’s pull through cache supports frequent registry syncs, helping to keep container images sourced from Chainguard up to date. Later, customers can apply ECR features such as image scanning and lifecycle policies to their cached Chainguard images. The pull through cache for Chainguard is available in all AWS Regions where Amazon ECR pull through cache is supported. To get started, review our documentation.  

You can now create Amazon S3 Access Grants in the AWS Asia Pacific (New Zealand) Region.

Amazon S3 Access Grants map identities in directories such as Microsoft Entra ID, or AWS Identity and Access Management (IAM) principals, to datasets in S3. This helps you manage data permissions at scale by automatically granting S3 access to end users based on their corporate identity.

Visit the AWS Region Table for complete regional availability information. To learn more about Amazon S3 Access Grants, visit our product page.

 

​You can now create Amazon S3 Access Grants in the AWS Asia Pacific (New Zealand) Region.
Amazon S3 Access Grants map identities in directories such as Microsoft Entra ID, or AWS Identity and Access Management (IAM) principals, to datasets in S3. This helps you manage data permissions at scale by automatically granting S3 access to end users based on their corporate identity.
Visit the AWS Region Table for complete regional availability information. To learn more about Amazon S3 Access Grants, visit our product page.  

AWS Config announces the launch of an additional 75 managed Config rules for various use cases such as security, durability, and operations. You can now search, discover, enable and manage these additional rules directly from AWS Config and govern more use cases for your AWS environment.

With this launch, you can now enable these controls across your account or across your organization. For example, you can assess your security posture across AWS Amplify, Amazon SageMaker, Amazon Route 53, and more. Additionally, you can leverage Conformance Packs to group these new controls and deploy across an account or across organization, streamlining your multi-account governance.

For the full list of recently released rules, visit the AWS Config developer guide. For description of each rule and the AWS Regions in which it is available, please refer our Config managed rules documentation. To start using Config rules, please refer our documentation.

New Rules Launched:

1. ACM_CERTIFICATE_TRANSPARENT_LOGGING_ENABLED
2. AMPLIFY_APP_BUILD_SPEC_CONFIGURED
3. AMPLIFY_APP_PLATFORM_CHECK
4. AMPLIFY_BRANCH_AUTO_BUILD_ENABLED
5. AMPLIFY_BRANCH_BUILD_SPEC_CONFIGURED
6. AMPLIFY_BRANCH_FRAMEWORK_CONFIGURED
7. AMPLIFY_BRANCH_PULL_REQUEST_PREVIEW_ENABLED
8. APIGATEWAY_DOMAIN_NAME_TLS_CHECK
9. APIGATEWAYV2_INTEGRATION_PRIVATE_HTTPS_ENABLED
10. APPINTEGRATIONS_APPLICATION_APPROVED_ORIGINS_CHECK
11. APPINTEGRATIONS_APPLICATION_TAGGED
12. APPMESH_MESH_IP_PREF_CHECK
13. APPMESH_VIRTUAL_GATEWAY_LISTENERS_HEALTH_CHECK_ENABLED
14. APPMESH_VIRTUAL_NODE_LISTENERS_HEALTH_CHECK_ENABLED
15. APPMESH_VIRTUAL_NODE_LISTENERS_OUTLIER_DETECT_ENABLED
16. APPMESH_VIRTUAL_NODE_SERVICE_BACKENDS_TLS_ENFORCED
17. CLOUDTRAIL_EVENT_DATA_STORE_MULTI_REGION
18. CLOUDWATCH_ALARM_DESCRIPTION
19. CODEARTIFACT_REPOSITORY_TAGGED
20. CODEBUILD_PROJECT_TAGGED
21. EC2_IPAMSCOPE_TAGGED
22. EC2_LAUNCHTEMPLATE_EBS_ENCRYPTED
23. ECS_SERVICE_PROPAGATE_TAGS_ENABLED
24. ELBV2_TARGETGROUP_HEALTHCHECK_PROTOCOL_ENCRYPTED
25. ELBV2_TARGETGROUP_PROTOCOL_ENCRYPTED
26. EVENTSCHEMAS_DISCOVERER_TAGGED
27. EVENTSCHEMAS_REGISTRY_TAGGED
28. GROUNDSTATION_CONFIG_TAGGED
29. GROUNDSTATION_DATAFLOWENDPOINTGROUP_TAGGED
30. GROUNDSTATION_MISSIONPROFILE_TAGGED
31. HEALTHLAKE_FHIRDATASTORE_TAGGED
32. IAM_OIDC_PROVIDER_CLIENT_ID_LIST_CHECK
33. IAM_POLICY_DESCRIPTION
34. IMAGEBUILDER_DISTRIBUTIONCONFIGURATION_TAGGED
35. IMAGEBUILDER_IMAGEPIPELINE_TAGGED
36. IMAGEBUILDER_IMAGERECIPE_EBS_VOLUMES_ENCRYPTED
37. IMAGEBUILDER_IMAGERECIPE_TAGGED
38. IMAGEBUILDER_INFRASTRUCTURECONFIGURATION_TAGGED
39. KINESISVIDEO_SIGNALINGCHANNEL_TAGGED
40. KINESISVIDEO_STREAM_TAGGED
41. LAMBDA_FUNCTION_APPLICATION_LOG_LEVEL_CHECK
42. LAMBDA_FUNCTION_LOG_FORMAT_JSON
43. LAMBDA_FUNCTION_SYSTEM_LOG_LEVEL_CHECK
44. LIGHTSAIL_BUCKET_OBJECT_VERSIONING_ENABLED
45. MEDIAPACKAGE_PACKAGINGCONFIGURATION_TAGGED
46. MEDIATAILOR_PLAYBACKCONFIGURATION_TAGGED
47. MEMORYDB_SUBNETGROUP_TAGGED
48. NEPTUNE_CLUSTER_SNAPSHOT_IAM_DATABASE_AUTH_ENABLED
49. OPENSEARCHSERVERLESS_COLLECTION_DESCRIPTION
50. OPENSEARCHSERVERLESS_COLLECTION_STANDBYREPLICAS_ENABLED
51. PANORAMA_PACKAGE_TAGGED
52. RDS_CLUSTER_BACKUP_RETENTION_CHECK
53. RDS_GLOBAL_CLUSTER_AURORA_MYSQL_SUPPORTED_VERSION
54. RESILIENCEHUB_APP_TAGGED
55. RESILIENCEHUB_RESILIENCYPOLICY_TAGGED
56. ROUTE53_RECOVERY_CONTROL_CLUSTER_TAGGED
57. ROUTE53_RECOVERY_READINESS_CELL_TAGGED
58. ROUTE53_RECOVERY_READINESS_READINESS_CHECK_TAGGED
59. ROUTE53_RECOVERY_READINESS_RECOVERY_GROUP_TAGGED
60. ROUTE53_RECOVERY_READINESS_RESOURCE_SET_TAGGED
61. ROUTE53_RESOLVER_RESOLVER_ENDPOINT_TAGGED
62. S3_DIRECTORY_BUCKET_LIFECYCLE_POLICY_RULE_CHECK
63. SAGEMAKER_DATA_QUALITY_JOB_ENCRYPT_IN_TRANSIT
64. SAGEMAKER_DATA_QUALITY_JOB_ISOLATION
65. SAGEMAKER_FEATUREGROUP_DESCRIPTION
66. SAGEMAKER_INFERENCEEXPERIMENT_TAGGED
67. SAGEMAKER_MODEL_BIAS_JOB_ENCRYPT_IN_TRANSIT
68. SAGEMAKER_MODEL_BIAS_JOB_ISOLATION
69. SAGEMAKER_MODEL_EXPLAINABILITY_JOB_ENCRYPT_IN_TRANSIT
70. SAGEMAKER_MODEL_QUALITY_JOB_ENCRYPT_TRANSIT
71. SAGEMAKER_MONITORING_SCHEDULE_ISOLATION
72. SIGNER_SIGNINGPROFILE_TAGGED
73. TRANSFER_CONNECTOR_AS2_ENCRYPTION_ALGORITHM_CHECK
74. TRANSFER_CONNECTOR_AS2_MDN_SIGNING_ALGORITHM_CHECK
75. TRANSFER_CONNECTOR_AS2_SIGNING_ALGORITHM_CHECK

 

​AWS Config announces the launch of an additional 75 managed Config rules for various use cases such as security, durability, and operations. You can now search, discover, enable and manage these additional rules directly from AWS Config and govern more use cases for your AWS environment. With this launch, you can now enable these controls across your account or across your organization. For example, you can assess your security posture across AWS Amplify, Amazon SageMaker, Amazon Route 53, and more. Additionally, you can leverage Conformance Packs to group these new controls and deploy across an account or across organization, streamlining your multi-account governance. For the full list of recently released rules, visit the AWS Config developer guide. For description of each rule and the AWS Regions in which it is available, please refer our Config managed rules documentation. To start using Config rules, please refer our documentation. New Rules Launched:

ACM_CERTIFICATE_TRANSPARENT_LOGGING_ENABLED
AMPLIFY_APP_BUILD_SPEC_CONFIGURED
AMPLIFY_APP_PLATFORM_CHECK
AMPLIFY_BRANCH_AUTO_BUILD_ENABLED
AMPLIFY_BRANCH_BUILD_SPEC_CONFIGURED
AMPLIFY_BRANCH_FRAMEWORK_CONFIGURED
AMPLIFY_BRANCH_PULL_REQUEST_PREVIEW_ENABLED
APIGATEWAY_DOMAIN_NAME_TLS_CHECK
APIGATEWAYV2_INTEGRATION_PRIVATE_HTTPS_ENABLED
APPINTEGRATIONS_APPLICATION_APPROVED_ORIGINS_CHECK
APPINTEGRATIONS_APPLICATION_TAGGED
APPMESH_MESH_IP_PREF_CHECK
APPMESH_VIRTUAL_GATEWAY_LISTENERS_HEALTH_CHECK_ENABLED
APPMESH_VIRTUAL_NODE_LISTENERS_HEALTH_CHECK_ENABLED
APPMESH_VIRTUAL_NODE_LISTENERS_OUTLIER_DETECT_ENABLED
APPMESH_VIRTUAL_NODE_SERVICE_BACKENDS_TLS_ENFORCED
CLOUDTRAIL_EVENT_DATA_STORE_MULTI_REGION
CLOUDWATCH_ALARM_DESCRIPTION
CODEARTIFACT_REPOSITORY_TAGGED
CODEBUILD_PROJECT_TAGGED
EC2_IPAMSCOPE_TAGGED
EC2_LAUNCHTEMPLATE_EBS_ENCRYPTED
ECS_SERVICE_PROPAGATE_TAGS_ENABLED
ELBV2_TARGETGROUP_HEALTHCHECK_PROTOCOL_ENCRYPTED
ELBV2_TARGETGROUP_PROTOCOL_ENCRYPTED
EVENTSCHEMAS_DISCOVERER_TAGGED
EVENTSCHEMAS_REGISTRY_TAGGED
GROUNDSTATION_CONFIG_TAGGED
GROUNDSTATION_DATAFLOWENDPOINTGROUP_TAGGED
GROUNDSTATION_MISSIONPROFILE_TAGGED
HEALTHLAKE_FHIRDATASTORE_TAGGED
IAM_OIDC_PROVIDER_CLIENT_ID_LIST_CHECK
IAM_POLICY_DESCRIPTION
IMAGEBUILDER_DISTRIBUTIONCONFIGURATION_TAGGED
IMAGEBUILDER_IMAGEPIPELINE_TAGGED
IMAGEBUILDER_IMAGERECIPE_EBS_VOLUMES_ENCRYPTED
IMAGEBUILDER_IMAGERECIPE_TAGGED
IMAGEBUILDER_INFRASTRUCTURECONFIGURATION_TAGGED
KINESISVIDEO_SIGNALINGCHANNEL_TAGGED
KINESISVIDEO_STREAM_TAGGED
LAMBDA_FUNCTION_APPLICATION_LOG_LEVEL_CHECK
LAMBDA_FUNCTION_LOG_FORMAT_JSON
LAMBDA_FUNCTION_SYSTEM_LOG_LEVEL_CHECK
LIGHTSAIL_BUCKET_OBJECT_VERSIONING_ENABLED
MEDIAPACKAGE_PACKAGINGCONFIGURATION_TAGGED
MEDIATAILOR_PLAYBACKCONFIGURATION_TAGGED
MEMORYDB_SUBNETGROUP_TAGGED
NEPTUNE_CLUSTER_SNAPSHOT_IAM_DATABASE_AUTH_ENABLED
OPENSEARCHSERVERLESS_COLLECTION_DESCRIPTION
OPENSEARCHSERVERLESS_COLLECTION_STANDBYREPLICAS_ENABLED
PANORAMA_PACKAGE_TAGGED
RDS_CLUSTER_BACKUP_RETENTION_CHECK
RDS_GLOBAL_CLUSTER_AURORA_MYSQL_SUPPORTED_VERSION
RESILIENCEHUB_APP_TAGGED
RESILIENCEHUB_RESILIENCYPOLICY_TAGGED
ROUTE53_RECOVERY_CONTROL_CLUSTER_TAGGED
ROUTE53_RECOVERY_READINESS_CELL_TAGGED
ROUTE53_RECOVERY_READINESS_READINESS_CHECK_TAGGED
ROUTE53_RECOVERY_READINESS_RECOVERY_GROUP_TAGGED
ROUTE53_RECOVERY_READINESS_RESOURCE_SET_TAGGED
ROUTE53_RESOLVER_RESOLVER_ENDPOINT_TAGGED
S3_DIRECTORY_BUCKET_LIFECYCLE_POLICY_RULE_CHECK
SAGEMAKER_DATA_QUALITY_JOB_ENCRYPT_IN_TRANSIT
SAGEMAKER_DATA_QUALITY_JOB_ISOLATION
SAGEMAKER_FEATUREGROUP_DESCRIPTION
SAGEMAKER_INFERENCEEXPERIMENT_TAGGED
SAGEMAKER_MODEL_BIAS_JOB_ENCRYPT_IN_TRANSIT
SAGEMAKER_MODEL_BIAS_JOB_ISOLATION
SAGEMAKER_MODEL_EXPLAINABILITY_JOB_ENCRYPT_IN_TRANSIT
SAGEMAKER_MODEL_QUALITY_JOB_ENCRYPT_TRANSIT
SAGEMAKER_MONITORING_SCHEDULE_ISOLATION
SIGNER_SIGNINGPROFILE_TAGGED
TRANSFER_CONNECTOR_AS2_ENCRYPTION_ALGORITHM_CHECK
TRANSFER_CONNECTOR_AS2_MDN_SIGNING_ALGORITHM_CHECK
TRANSFER_CONNECTOR_AS2_SIGNING_ALGORITHM_CHECK  

Starting today, the compute-optimized Amazon EC2 C8a instances are available in the Asia Pacific (Tokyo) region. C8a instances are powered by 5th Gen AMD EPYC processors (formerly code named Turin) with a maximum frequency of 4.5 GHz, delivering up to 30% higher performance and up to 19% better price-performance compared to C7a instances.

C8a instances deliver 33% more memory bandwidth compared to C7a instances, making these instances ideal for latency sensitive workloads. Compared to Amazon EC2 C7a instances, they are up to 57% faster for GroovyJVM allowing better response times for Java-based applications. C8a instances offer 12 sizes including 2 bare metal sizes. This range of instance sizes allows customers to precisely match their workload requirements.

C8a instances are built on AWS Nitro System and are ideal for high performance, compute-intensive workloads such as batch processing, distributed analytics, high performance computing (HPC), ad serving, highly-scalable multiplayer gaming, and video encoding.

To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information visit the Amazon EC2 C8a instance page.

 

​Starting today, the compute-optimized Amazon EC2 C8a instances are available in the Asia Pacific (Tokyo) region. C8a instances are powered by 5th Gen AMD EPYC processors (formerly code named Turin) with a maximum frequency of 4.5 GHz, delivering up to 30% higher performance and up to 19% better price-performance compared to C7a instances. C8a instances deliver 33% more memory bandwidth compared to C7a instances, making these instances ideal for latency sensitive workloads. Compared to Amazon EC2 C7a instances, they are up to 57% faster for GroovyJVM allowing better response times for Java-based applications. C8a instances offer 12 sizes including 2 bare metal sizes. This range of instance sizes allows customers to precisely match their workload requirements. C8a instances are built on AWS Nitro System and are ideal for high performance, compute-intensive workloads such as batch processing, distributed analytics, high performance computing (HPC), ad serving, highly-scalable multiplayer gaming, and video encoding. To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information visit the Amazon EC2 C8a instance page.  

Starting today, AWS Elemental MediaConnect supports NDI® (Network Device Interface) as a live video source, enabling broadcasters and live production teams to ingest NDI streams and convert them to transport stream outputs such as SRT for downstream distribution. NDI is a widely adopted IP video technology used in live production environments and supported by more than 500 hardware products and 400 software applications.

With this new capability, live production teams can bridge NDI-based production environments with standards-based cloud distribution workflows without requiring custom transcoding or protocol conversion infrastructure. For example, you can route an NDI feed from an EC2 instance running NDI Tools directly into a MediaConnect flow, convert it to a transport stream, and pass it downstream to AWS Elemental MediaLive for transcoding and AWS Elemental MediaPackage for origin and packaging. This eliminates the complexity of egressing NDI content from the AWS Cloud and enables seamless integration with existing IP-based broadcast workflows.

NDI support is available in most regions where MediaConnect is currently deployed. For more information and details on pricing, please refer to the NDI documentation and the MediaConnect pricing page.

 

​Starting today, AWS Elemental MediaConnect supports NDI® (Network Device Interface) as a live video source, enabling broadcasters and live production teams to ingest NDI streams and convert them to transport stream outputs such as SRT for downstream distribution. NDI is a widely adopted IP video technology used in live production environments and supported by more than 500 hardware products and 400 software applications. With this new capability, live production teams can bridge NDI-based production environments with standards-based cloud distribution workflows without requiring custom transcoding or protocol conversion infrastructure. For example, you can route an NDI feed from an EC2 instance running NDI Tools directly into a MediaConnect flow, convert it to a transport stream, and pass it downstream to AWS Elemental MediaLive for transcoding and AWS Elemental MediaPackage for origin and packaging. This eliminates the complexity of egressing NDI content from the AWS Cloud and enables seamless integration with existing IP-based broadcast workflows. NDI support is available in most regions where MediaConnect is currently deployed. For more information and details on pricing, please refer to the NDI documentation and the MediaConnect pricing page.  

Amazon Redshift improves the performance of BI dashboards and ETL workloads by speeding up new queries by up to 7x. This significantly improves the response times of low-latency SQL queries, such as those used in near real-time analytics applications, BI dashboards, ETL pipelines, and autonomous, goal-seeking AI agents. Customers experience substantially faster query response times as Redshift accelerates the process of preparing the SQL query for execution. Queries start faster and return results quicker. This improvement is automatically enabled at no additional cost.

To deliver this major improvement, Redshift added a new optimization to query compilation where new queries are processed immediately using composition. Composition is a technique that generates a lightweight arrangement of pre-existing logic while simultaneously creating highly optimized, query-specific code that is compiled and executed across available compute resources to further boost performance. Composition removes compilation from the critical path of query execution and provides immediate execution while compilation proceeds in the background. With this optimization, new queries processed by Redshift start faster and deliver performance consistent with subsequent runs.

This optimization is enabled by default for any SQL query across all provisioned clusters and serverless workgroups, in all commercial AWS Regions where Amazon Redshift operates. It is available on the Redshift current track with other tracks following in upcoming patch releases. No action is required from customers to benefit from this enhancement, and it is free of charge.

 

​Amazon Redshift improves the performance of BI dashboards and ETL workloads by speeding up new queries by up to 7x. This significantly improves the response times of low-latency SQL queries, such as those used in near real-time analytics applications, BI dashboards, ETL pipelines, and autonomous, goal-seeking AI agents. Customers experience substantially faster query response times as Redshift accelerates the process of preparing the SQL query for execution. Queries start faster and return results quicker. This improvement is automatically enabled at no additional cost. To deliver this major improvement, Redshift added a new optimization to query compilation where new queries are processed immediately using composition. Composition is a technique that generates a lightweight arrangement of pre-existing logic while simultaneously creating highly optimized, query-specific code that is compiled and executed across available compute resources to further boost performance. Composition removes compilation from the critical path of query execution and provides immediate execution while compilation proceeds in the background. With this optimization, new queries processed by Redshift start faster and deliver performance consistent with subsequent runs. This optimization is enabled by default for any SQL query across all provisioned clusters and serverless workgroups, in all commercial AWS Regions where Amazon Redshift operates. It is available on the Redshift current track with other tracks following in upcoming patch releases. No action is required from customers to benefit from this enhancement, and it is free of charge.  

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.

 

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