Ayar Labs of San Jose, the co-packaged optics (CPO) specialist, and Taiwan ASIC house Alchip  have joined forces to address the needs of  hyperscalers  for AI accelerators and platforms that …

The post Ayar Labs hooks up with Alchip on co-packaged optics appeared first on Electronics Weekly .

The European Space Agency (ESA) has selected the first three missions to secure a flight via its Flight Ticket Initiative, courtesy of Avio and Isar Aerospace. The Flight Ticket Initiative has …

The post ESA chooses first missions for its Flight Ticket Initiative appeared first on Electronics Weekly .

Yesterday SpaceX said it will buy wireless spectrum licences from EchoStar for around $17bn to facilitate Starlink’s direct-to-cell service. The spectrum bands involved –  AWS-4 and H-block – are said …

The post SpaceX spectrum buy will end mobile dead zones anywhere in the world appeared first on Electronics Weekly .

Despite a flat market for the next couple of years the RF front-end module market, which was worth $15.4bn in 2024, will be worth more than $17bn by 2030, says …

The post China coming for the RF front-end module market appeared first on Electronics Weekly .

AWS Config now tracks resource tags for IAM policy resource types, enhancing the granularity of metadata you can capture to assess, audit, and evaluate configurations of your IAM policies.

With this enhancement, you can now track resource tags and their changes for IAM Policies directly in your Config recorder. This capability allows you to scope both Config-managed and custom rule evaluations based on resource tags, ensuring your IAM policies maintain desired configurations. Additionally, you can leverage Config aggregators to selectively aggregate IAM policies across multiple accounts using tags, streamlining your multi-account governance.

This feature is now available across all supported AWS Regions at no additional cost. Resource tags are automatically populated in Config when you record IAM policy resource types. For recording IAM policy resource type in your Config recorder, please refer our documentation .

Today, we are announcing improvements to the Amazon Q Developer chat experience in Amazon SageMaker Unified Studio Jupyter notebooks and adding Amazon Q Developer in the command line in Jupyter notebooks and Code Editor. By integrating with Model Context Protocol (MCP) servers, Amazon Q Developer is aware of your SageMaker Unified Studio project resources, including data, compute, and code, and provides personalized assistance for data engineering and machine learning development work.

These new capabilities provide highly relevant responses to assist with tasks like code refactoring, file modification, and troubleshooting. This helps data scientists and data engineers quickly set up their integrated development environments and work more efficiently while maintaining transparency into how the AI assistant is acting on their behalf.

These features are available at no additional cost with the Amazon Q Developer Free Tier in all AWS Regions where Amazon SageMaker Unified Studio is available. To make even more use of these features, we recommend enabling Amazon Q Developer Pro. To do so, please refer to the documentation .

Today, AWS announced the general availability of Custom Blueprints, a new feature in Amazon SageMaker Unified Studio, part of the next generation of Amazon SageMaker. This feature allows customers to use their own managed policies as per their corporate security requirements to create a project role in SageMaker Unified Studio. Customers can either replace the managed policies provide by Amazon SageMaker Unified Studio as part of the tooling blueprint with their custom policies or enrich the existing policies by appending additional policies.

In addition to allowing you to bring your own managed policies, Custom Blueprints is designed to provide you the ability to configure the infrastructure and resources that you want to deploy in the project created in Amazon SageMaker Unified Studio. Using your own AWS CloudFormation templates you can define and customize the parameters and configuration for any AWS resources such as Amazon EMR on EC2, AWS Glue Data Catalog, and Amazon Redshift. You can replace the service managed blueprints with your custom blueprints in order to ensure standardization across your entire organization. The sample templates to create your custom blueprints are available here .

The ability to use Custom Blueprint is available in all AWS Commercial Regions where the next generation of Amazon SageMaker is available. See the supported regions list for more details. For instructions on how to get started, visit the Amazon SageMaker documentation .

Amazon CloudFront expands its IPv6 capabilities by introducing support for IPv6 connectivity to origin servers, allowing customers to implement end-to-end IPv6 content delivery for their web applications. Support for IPv6 origins enables customers to send IPv6 traffic all the way to their origins, allowing them to meet their architectural and regulatory requirements for IPv6 adoption. End-to-end IPv6 support improves network performance for end users connecting over IPv6 networks, and also removes concerns for IPv4 address exhaustion for origin infrastructure.

Previously, CloudFront only supported IPv4 connectivity to origins, despite accepting IPv6 connections from end users. Customers using CloudFront can configure their custom origins to use IPv4-only (default), IPv6-only, or dual-stack connectivity. When using dual-stack, CloudFront will automatically choose between IPv4 and IPv6 addresses to ensure even distribution of traffic towards origin over both.

Customers can configure IPv6 origins in all supported AWS Commercial Regions. Customers can configure IPv6-only or dual-stack origins with CloudFront, excluding Amazon S3 and VPC origins. To learn more IPv6 support with CloudFront, visit the CloudFront documentation.

Today, we are announcing a new capability that NetworkX now supports Neptune Analytics as a graph store. With this release, developers can continue to use familiar NetworkX APIs while automatically offloading graph algorithm workloads to Neptune’s scalable, high-performance analytics engine. This makes it simple to scale graph computations on demand without refactoring code, combining the ease of local development with the performance and elasticity of a fully managed AWS service.

Previously, when datasets grew beyond the limits of a local environment, users had to turn to third-party services—rebuilding their graph models to fit proprietary formats, exporting and importing data, and learning entirely new systems. With the new nx-neptune integration, developers only need an AWS account and credentials; the solution automatically handles graph data modeling, data movement (Zero-ETL), and infrastructure management. It provisions a Neptune Analytics instance, runs the requested algorithm, returns results directly to the user, and then tears down the infrastructure for a cost-effective, serverless-like experience—all without requiring the user to leave their familiar Python workflow.

NetworkX is a widely used open-source Python library for creating, analyzing, and visualizing complex graphs. It offers an extensive collection of graph algorithms and utilities, making it a popular choice among researchers, data scientists, and developers for prototyping and experimenting with graph-based applications. To learn more about the Neptune–NetworkX Integration, visit the documentation .

 

AWS WAF now includes 500 MB of CloudWatch Logs Vended Logs Ingestion for every 1 million WAF requests processed, at no additional cost. This helps customers better manage their WAF logging costs while maintaining comprehensive security visibility.

WAF logs in CloudWatch provide valuable insights for security analysis, compliance, and troubleshooting. Customers can leverage CloudWatch’s advanced analytics capabilities, including Log Insights queries, anomaly detection, and dashboards, to monitor and analyze their web application traffic patterns and security events. The included logs allocation is automatically applied based on WAF requests usage on your AWS bill at month end, making it easy to take advantage of the new pricing.

The free WAF logs allocation is across WAF specific Vended Logs to CloudWatch and S3. Usage beyond the included 500 MB per 1 million WAF requests will be charged at AWS WAF specific Vended Logs pricing in CloudWatch. For pricing details, please visit the AWS WAF pricing page.

To learn more about WAF logging capabilities and how to get started, visit the AWS WAF documentation.