UMC is looking at moving into developing a leading edge process capability which it hasn’t had for ten years. UMC CFO Liu Chitung told the Nikkei that the company is …

The post UMC looking at regaining leading edge process capability appeared first on Electronics Weekly .

Makimoto’s Wave, which tracks the swing of the chip industry between periods of  standardisation and customisation, looks good for at least the next decade, says Malcolm Penn, CEO of Future …

The post Makimoto’s Wave extended to ‘at least’ 2037 appeared first on Electronics Weekly .

TE Connectivity is moving to nickel-phosphorus coatings to reduce the CO2 footprint of its connector contact plating processes. Branding the plating stack Econidur, “according to TE internal analysis and calculations, …

The post TE adopts lower-CO2 plating for connector contacts appeared first on Electronics Weekly .

Starting today, you can enable Amazon CloudWatch metric (ResolverEndpointCapacityStatus) to monitor the status of the query capacity for Elastic Network Interfaces (ENIs) associated with your Route 53 Resolver endpoint in Amazon Virtual Private Cloud (VPC). The new metric enables you to quickly view whether the Resolver endpoint is at the risk of meeting the service limit for query capacity, and take remediation steps like instantiating additional ENIs to meet the capacity needs.

Before today, you could enable CloudWatch to monitor the number of DNS queries that were forwarded by Route 53 Resolver endpoints, over a default five-minute interval, and make further estimations on when your endpoints will meet the query limits. With this launch, you can now enable the new metric to get direct alerts on the current status of your Resolver endpoint capacity, without requiring you to make additional estimations for calculating capacity of each endpoint. The status is reported for each Resolver endpoint, indicating whether the endpoint is operating within the normal capacity limit (0 – OK), has at least one ENI exceeding 50% capacity utilization (1 – Warning), or has at least one ENI exceeding 75% capacity utilization (2 – Critical). The new metric simplifies capacity management for Route 53 Resolver endpoints by providing clear, actionable signals for scaling decisions, without requiring additional analysis on the query volume.

To learn more about the launch, read the documentation or visit the Route 53 Resolver page . There is no charge for the metric, although you will incur charges for usage of Resolver endpoints

Today, we’re announcing general availability of Amazon SageMaker HyperPod training operator, a purpose-built Kubernetes extension for resilient foundation model training on HyperPod.

Amazon SageMaker HyperPod empowers customers to accelerate AI model development across hundreds or thousands of GPUs with built-in resiliency, decreasing model training time by up to 40%. As training clusters expand, recovery from training interruptions becomes increasingly disruptive. Failure recovery traditionally requires a complete job restart across all nodes when even a single training process fails, resulting in additional downtime and increased costs. Moreover, identifying and resolving critical training issues such as stalled GPUs, low training throughput, and numerical instabilities, typically requires complex custom monitoring code, further extending development timelines and delaying time to market.

With the HyperPod training operator, customers can further enhance training resilience for Kubernetes workloads. Instead of a full job restart when failures occur, the HyperPod training operator performs surgical recovery, selectively restarting only the affected training resources for faster recovery from faults. It also introduces a customizable hanging job monitoring capability to help overcome problematic training scenarios including stalled training batches, non-numeric loss values, and performance degradation through simple YAML configurations. Getting started is simple: create a HyperPod cluster, install the training operator add-on, optionally define custom recovery policies for hanging jobs, and launch training.

This release is generally available in all AWS Regions where SageMaker HyperPod is currently supported.

See the documentation to learn more.

Amazon Connect can now integrate agent activities from third-party applications as Connect Tasks, which can be evaluated alongside work completed in Connect, providing managers with a unified application for quality management. You can programmatically ingest activities from third-party applications (such as application processing, social media posts, etc.) as completed Tasks within Connect, capturing details relevant for performance evaluation as Task attributes. Managers can then evaluate these external activities, alongside native Connect interactions to get a unified view of agent performance within Connect dashboards.

This feature is available in all regions where Contact Lens performance evaluations are already available. To learn more, please visit our documentation and our webpage . For information about Contact Lens pricing, please visit our pricing page .
 

Amazon Redshift now allows you to get started with Amazon Redshift Serverless with a lower data warehouse base capacity configuration of 4 Redshift Processing Units (RPUs). Amazon Redshift Serverless measures data warehouse capacity in RPUs, and you pay only for the duration of workloads you run in RPU-hours on a per-second basis. Previously, the minimum base capacity required to run Amazon Redshift Serverless was 8 RPUs. You can start using Amazon Redshift Serverless for as low as $1.50 per hour and pay only for the compute capacity your data warehouse consumes when it is active.

Amazon Redshift Serverless enables users to run and scale analytics without managing data warehouse clusters. The new lower capacity configuration makes Amazon Redshift Serverless suitable for both production and development environments, particularly when workloads require minimal compute and memory resources. This entry-level configuration supports data warehouses with up to 32 TB of Redshift managed storage, offering a maximum of 100 columns per table and 64 GB of memory.

Amazon Redshift Serverless with 4 RPU Minimum Capacity Option is generally available in the AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Europe (Ireland), Europe (Stockholm).

To get started, see the Amazon Redshift Serverless feature page , use cases , user documentation , API Reference , and pricing .
 

Amazon Elastic Container Services (Amazon ECS) now makes it easier to troubleshoot unhealthy tasks by adding the Task ID in service action events generated due to health failures.

Amazon ECS is designed to help easily launch and scale your applications. When your Amazon ECS task fails Elastic Load Balancing (ELB) health checks, Amazon ECS produces an unhealthy service action event. With today’s launch, the Task ID is also included as part of the generated event, so you can quickly pinpoint the Task in question for faster troubleshooting.

The new experience is now automatically enabled in all AWS Regions. See more details regarding unhealthy Service Events in the Amazon ECS documentation and how to set up Amazon EventBridge rules to capture Amazon ECS service action events .
 

Starting today, AWS Global Accelerator supports application endpoints in two additional AWS Regions, AWS Mexico (Central) Region and Asia Pacific (Malaysia) Region, expanding the number of supported AWS Regions to thirty one.

AWS Global Accelerator is a service that is designed to help you improve the availability, security, and performance of your internet-facing applications. By using the congestion-free AWS network, end-user traffic to your applications benefits from increased availability, DDoS protection at the edge, and higher performance relative to the public internet. Global Accelerator provides static IP addresses that act as fixed entry endpoints for your application resources in one or more AWS Regions, such as your Application Load Balancers, Network Load Balancers, Amazon EC2 instances, or Elastic IPs. Global Accelerator continually monitors the health of your application endpoints and offers deterministic fail-over for multi-region workloads without any DNS dependencies.

To get started, visit the AWS Global Accelerator website and review its documentation .
 

Zonal autoshift practice runs take place once a week to ensure your application is ready for a zonal shift. Now with on-demand practice runs, you can trigger a practice run anytime you want to and validate your application’s preparedness. When a practice run is started, a pre-check will be performed to ensure your application has balanced capacity across AZs. This check is done for Application Load Balancers, Network Load Balancers, and EC2 Auto Scaling groups.

To get started, you can initiate an on-demand practice run in the ARC console, API, or CLI. This allows you to test your application’s practice run configuration to ensure the alarms are configured correctly and your application behaves as expected. For both automated and on-demand practice, pre-checks for balanced capacity will validate your resource’s capacity and ensure it’s safe to start the practice. If the pre-check fails, you’ll be alerted, so you can take corrective action.

Zonal autoshift on-demand practice runs and practice run pre-checks for balanced capacity are available in all commercial AWS Regions , and including AWS GovCloud (US) Regions . To learn more, please refer to the ARC zonal autoshift documentation .