Mikroe has introduced a ‘Click’ format development board which supports Bluetooth LE Audio Unicast and Auracast. It is based around a Bluetooth 5.4 module from Cambridge UK based IOT747, called …

The post Bluetooth LE audio Click development board appeared first on Electronics Weekly .

Seoul National University of Science and Technology has mimicked the tiny feet of starfish to make tiny grippers for underwater ‘soft’ robots. Gecko feet have already done something similar for …

The post Starfish inspires gripper surface for underwater robots appeared first on Electronics Weekly .

In the quarter to the end of July, Nvidia had sales of $46.7 billion which was 56% up y-o-y – the smallest y-o-y percentage increase for two years. Profit was …

The post Nvidia has $46.7bn Q2 forecasts $54bn Q3 appeared first on Electronics Weekly .

You can now downgrade to minor Apache Airflow versions on Amazon Managed Workflows for Apache Airflow (MWAA). 

Amazon MWAA is a managed orchestration service for Apache Airflow that makes it easier to set up and operate end-to-end data pipelines in the cloud. This in-place minor Apache Airflow version option allows you to downgrade your MWAA Apache Airflow version to any other supported minor version . 

You can launch a new Apache Airflow environment on Amazon MWAA with just a few clicks in the AWS Management Console  in all currently supported Amazon MWAA regions . To learn more about Apache Airflow minor version downgrade visit the Amazon MWAA documentation .

Apache, Apache Airflow, and Airflow are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.

Amazon RDS now supports Redo Transport Compression, a feature that compresses redo data before it is transmitted to a standby database. By reducing the amount of data sent over the network, it improves redo transport performance. Because of faster redo log transport, customers can achieve a lower Recovery Point Objective (RPO), which is the amount of data loss that may occur when promoting a replica in situations where the primary instance becomes unavailable.

Compression and decompression of redo data consumes CPU resources on both the primary and standby databases. Customers should ensure that sufficient CPU capacity is available to handle this increased workload, and use Redo Transport Compression in situations where reduced network traffic and improved RPO outweigh the CPU overhead of compression. To enable the feature, set redo_compression parameter in the Parameter Group for your database instance. Redo Log Compression is available for both mounted and read replicas, and requires Oracle Enterprise Edition with Oracle Advanced Compression Licensing .

Redo Transport Compression is available in all AWS Regions where Amazon RDS for Oracle is available. To learn more about using Redo Transport Compression, visit the Amazon RDS User Guide .

Starting today, Amazon GameLift Streams  offers enhanced flexibility for managing default applications in stream groups. You can now create new stream groups without specifying a default application and modify or remove the default application in the existing stream group.

The key improvements include:

• Ability to create a stream group without a default application
• Ability to select and modify the default application in an existing stream group
• Ability to unlink a default application without having to delete the entire stream group
• Automatic selection of a new default application when no default exists, before streaming an application, ensuring the stream group always has a default when available

Each stream group can have one application set as default, which is pre-cached to help reduce the stream startup time. You can now switch the default status between any linked applications to optimize the performance without recreating stream groups.

To take advantage of these improvements, you can use the updated Amazon GameLift Streams APIs or the service console to manage your default application configurations. The UpdateStreamGroup API includes a new optional field for the default application identifier. The AssociateApplications and DisassociateApplications APIs have also been updated to handle default application changes. For more information about default applications, see Multi-application stream groups  in the Developer Guide.

These enhancements provide a better experience as you build and scale your cloud gaming infrastructure.

AWS App Runner now supports IPv6-based inbound and outbound traffic on both public and private App Runner service endpoints. This helps customers meet IPv6 compliance requirements, and removes the need for handling address translation between IPv4 and IPv6.

App Runner is a fully-managed service that makes it easier for developers to quickly deploy containerized web applications and APIs to the cloud, at scale, and without managing infrastructure. Previously, IPv6 was only supported on incoming traffic through public endpoints. You can configure IPv6 by selecting the dual-stack option in your networking configuration on new or existing services. 

AWS App Runner support for IPv6 is available in all AWS Regions where AWS App Runner is available . For more information about how to manage dual-stack support for your App Runner service, see Networking with App Runner  in the AWS App Runner Developer Guide.

Today, Amazon Braket introduced a local device emulator that enables developers to test verbatim circuits with device-specific characteristics before running on quantum hardware. This feature accelerates development by providing early feedback on circuit compatibility and expected behavior under realistic noise conditions, helping customers validate their quantum programs and develop noise-aware algorithms without incurring hardware costs.

The local device emulator offers several key capabilities:

• Validates circuit compatibility with target quantum devices, including qubit connectivity, native gate sets, and device topology constraints
• Simulates quantum circuits with depolarizing channels applied to one-qubit and two-qubit gates based on device calibration data
• Provides realistic predictions of program behavior on noisy hardware using local density matrix simulation
• Supports both real-time and historical calibration data for device emulation

Braket users can instantiate device emulators directly from AWS quantum devices or from custom device properties using the Amazon Braket SDK. The emulator seamlessly integrates with existing workflows, allowing developers to catch compatibility issues early and efficiently iterate on their quantum algorithms before running them on actual quantum hardware.

For more information, visit the Amazon Braket developer guide , read the launch blog post , and explore our example notebook demonstrating the local device emulator.

Today, AWS Client VPN announces support for remote access to IPv6 workloads, allowing customers to establish secure VPN connections to their IPv6-enabled VPC resources. This new capability enables customers to meet their compliance and IPv6 network adoption goals. Now organizations can support IPv4, IPv6, and dual-stack resource connectivity through their Client VPN endpoints.

Previously, Client VPN only supported remote access to IPv4-enabled AWS workloads. With this feature, administrators can now support IPv6-enabled resources using IPv6-only or dual-stack Client VPN endpoints. Organizations can now directly connect their remote users to IPv6 resources and maintain end-to-end IPv6-only connectivity. For example, organizations can now use IPv6-enabled devices to remotely access IPv6-enabled resources in VPC via Client VPN, preserving end-to-end IPv6 connectivity. This feature simplifies network architecture for organizations using IPv6 while preserving native protocol preferences.

This feature is available in all regions where AWS Client VPN is generally available, except the Middle East (Bahrain) Region, and comes with no additional cost. Customers can use IPv6 and dual-stack endpoints at the current endpoint per-hour price.

To learn more about Client VPN:

• Visit the AWS Client VPN product page
• Read the AWS Client VPN documentation
• Read the AWS Client VPN user guide

 

Amazon SageMaker HyperPod now supports the Amazon Elastic Block Store (EBS) Container Storage Interface (CSI) driver, enabling customers to dynamically provision and manage persistent storage for machine learning workloads on SageMaker HyperPod EKS clusters. This capability allows customers to create, attach, and manage EBS volumes through Kubernetes persistent volume claims, providing storage that persists across pod restarts and node replacements. Customers deploying training and inference workloads need flexible storage allocation while maintaining high performance, but previously required manual EBS volume management outside Kubernetes workflows.

EBS CSI driver support enables customers to dynamically provision volumes based on model requirements, resize volumes without service disruption, and create snapshots for backup and recovery. For training workloads, this provides persistent storage for datasets, model checkpoints, and shared artifacts. For inference workloads, customers can provision model storage, create caching volumes, and maintain event logging. The integration supports both static and dynamic provisioning through Kubernetes storage classes, optimizing storage costs and performance.

To get started, install the Amazon EBS CSI driver as an EKS add-on on your HyperPod EKS cluster, then provision EBS volumes using standard Kubernetes persistent volume claims and storage classes. The EBS CSI driver manages the complete lifecycle of EBS volumes, including creation, attachment, mounting, and cleanup. Volume encryption with customer-managed KMS keys is supported, and volumes can be resized and snapshotted through standard Kubernetes operations.

This feature is available in all AWS Regions where SageMaker HyperPod EKS clusters are supported. To learn more about EBS CSI driver support, see the Amazon SageMaker HyperPod User Guide .