TSMC said last week at its Technology Symposium that  it will start high volume production on its N2 process using GAA transistors  this year, and that production on its N2P …

The post The shoot-out at 2nm appeared first on Electronics Weekly .

Children from Cambourne, near Cambridge, are set to represent the UK in the Asia Pacific FIRST LEGO Robotics Open Championship, which will be held in Sydney in July. To reach …

The post Cambourne kids head to Australia for FIRST LEGO Robotics Championship appeared first on Electronics Weekly .

Powerbox is aiming at ground-based defense applications and harsh industrial environments with a 1,000W IP65 ruggedised ac-dc power supply series. ECD1000A comes in a metal enclosure with baseplate conduction cooling …

The post 1kW harsh environment PSU sealed to IP65 appeared first on Electronics Weekly .

In 2006, Freescale and NXP were bought by private equity funds Blackstone and KKR for $17.6 billion and $8 billion (for an 80% stake) respectively, thereby sparking an intense debate …

The post Partners or Villains? appeared first on Electronics Weekly .

We often write about AI and STEM, and here is another interesting new Gadget Book worthy of our virtual library – She, DISRUPTS.

The post Gadget Book: She, DISRUPTS appeared first on Electronics Weekly .

Intending to map the ground from small aircraft and drones, researchers in China have made a singe-photon radar. It achieves resolution better than 40cm from 2.1km altitude using around two …

The post 450mW single-photo radar maps the ground with 40cm resolution appeared first on Electronics Weekly .

Network Load Balancer (NLB) now supports Resource Map, a tool in the console that displays all your NLB resources and their relationships in a visual format on a single page, providing you a clear understanding of your NLB architecture. NLB’s resource map shows relationships between your load balancer’s listeners, target groups, and targets. The feature highlights relationships and routing paths between resources and provides useful additional details like target group health overview and health status for individual targets. The simplified user interface makes it easier to identify any undesirable configurations, facilitates appropriate edits, and provides a visual representation of the configuration changes on your load balancer. Resource maps also have a filtered view called “Unhealthy target map”, which shows all unhealthy targets and the resources associated with them to simplify troubleshooting. This feature is available in all commercial AWS Regions, AWS GovCloud (US) Regions and China Regions. To learn more about NLB Resource Map, visit our documentation.

You can now restore your Amazon Managed Service for Apache Flink application to the previous running version and application state from the most recent, successful snapshot. This feature will work when your application is running and is most useful when you want to immediately rollback to the previous application version to mitigate downstream impact of an application update. Prior to this launch, you could only rollback applications that were in updating or autoscaling statuses.  Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Amazon Managed Service for Apache Flink reduces the complexity of building and managing Apache Flink applications and integrates with Amazon Managed Streaming for Apache Kafka (Amazon MSK), Amazon Kinesis Data Streams, Amazon OpenSearch Service, Amazon DynamoDB streams, Amazon Simple Storage Service (Amazon S3), custom integrations, and more using built-in connectors.  For a list of the AWS Regions where Amazon Managed Service for Apache Flink is available, please see the AWS Region Table. You can learn more about Amazon Managed Service for Apache Flink here.

Customers can now create and manage default policies across their entire organization or organizational unit (OU) with AWS CloudFormation StackSets. Default policies work in conjunction with customers’ existing backup mechanisms to only create EBS-backed AMIs and EBS Snapshots of instances and volumes without recent backups. This helps administrators ensure that all member accounts have comprehensive backup protection without creating duplicate backups or increasing management overhead and cost.  Amazon Data Lifecycle Manager default policies target instances and/or volumes in a region and will automate the creation and retention of backups for resources which have not been recently backed-up. Customers can set their default policy to exclude non-critical workloads by specifying exclusion parameters such as volume type, resource tags, and boot volumes. Now with CloudFormation StackSets and the provided sample templates, administrators can easily create and manage default policies in all AWS Regions and in all member accounts to ensure they are all compliant with the organization’s back up requirements. Amazon Data Lifecycle Manager default policies and the CloudFormation StackSets sample template for default policies are available in all AWS Regions. There is no cost associated with creating and managing these policies. Customers only pay for the storage cost associated with any EBS Snapshots that are created. The CloudFormation StackSets sample templates to “Create and manage default policies for EBS Snapshots and EBS-backed Amazon Machine Images (AMIs)” are now available through the AWS Management Console, AWS SDKs, or the AWS Command Line Interface (CLI). To learn about this feature, read the blogpost and our documentation. 

AWS CodePipeline V2 type pipelines now support stage level rollback to help customers to confidently deploy changes to their production environment. When a pipeline execution fails in a stage due to any action(s) failing, customers can quickly get that stage to a known good state by rolling back to a previously successful pipeline execution in that stage. Customers can roll back changes in any stage, whether succeeded or failed, except the Source stage. Customers can either manually initiate a rollback for a stage from the console, API, CLI or SDK, or configure a stage in the pipeline definition to automatically opt in to rollback in case of failure. When a rollback is initiated, a new pipeline execution is started in that stage with the changes from the selected pipeline execution (manual rollback), or with the source changes from the most recent successful pipeline execution in that stage (automated rollback).  To learn more about using manual and automated rollbacks in your pipeline, visit our documentation. For more information about AWS CodePipeline, visit our product page. Stage level rollback is available in all regions where AWS CodePipeline is supported.