In 2004, the following discussion on IP took place between Jerry Ardizzone, US president of Arm; Kurt Wolf, director of IP and library alliances at TSMC; Phil Dworsky, director of …

The post What Is IP? appeared first on Electronics Weekly .

Exeunt Sycamore and Bristlecone. And enter, stage left, Google’s Willow, which it describes as a state-of-the-art quantum chip…

The post Gadget-in-Extremis: Willow, Google’s most pwerful quantum chip appeared first on Electronics Weekly .

After the jury in the Arm v Qualcomm case had been out for nine hours yesterday, it delivered a mixed verdict. The jury was asked to decide three questions:. Did  …

The post Qualcomm vs Arm lawsuit decision appeared first on Electronics Weekly .

AWS PrivateLink now supports native cross-region connectivity in the following additional Regions: North America (N.California, Ohio, Canada Central), Europe (Stockholm, Paris, London, Milan, Frankfurt), Africa (Cape Town), Middle East (Bahrain) and Asia Pacific (Osaka, Hong Kong, Seoul, Mumbai).

This launch enables customers to connect to VPC endpoint services hosted in other AWS Regions in the same AWS pa rtition over Interface endpoints. As a service provider, you can enable access to your VPCE service for customers in all existing and upcoming AWS Regions without the need to setup additional infrastructure in each region. As a service consumer, you can privately connect to VPCE services in other AWS Regions without the need to setup cross-region peering or exposing your data over the public internet. Cross-region enabled VPCE services can be accessed through Interface endpoints at a private IP address in your VPC, enabling simpler and more secure inter-region connectivity.

To learn about pricing for this feature, please see the AWS PrivateLink pricing page . To learn more, read our blog and visit AWS PrivateLink in the Amazon VPC Developer Guide.

You can now remove queues and routing profiles that are no longer required in your contact center directly from the Amazon Connect admin website, in addition to the API-based deletion that was previously supported. For example, if your team set up sample queues to test a use case that are no longer needed, or you are consolidating your routing profiles because you have reorganized agents, you can now click to remove the unwanted resources.

To get started, open the Amazon Connect admin website and navigate to the queues or routing profile page. Use the delete action to remove unneeded rows and free up service quotas for that resource. The updated UIs are available in all AWS Regions where Amazon Connect is offered. For more information, see the administrator guide . To learn more about Amazon Connect, the AWS contact center as a service solution on the cloud, please visit the Amazon Connect website .
 

Amazon RDS for Db2 now enables the creation of multiple Db2 databases within a database instance. This enhanced capability offers greater flexibility in managing databases and optimizing licenses for various enterprise workloads.

Customers can now provision and manage up to 50 Db2 databases within a single RDS for Db2 instance, eliminating the need to deploy and license databases individually for each RDS instance. Customers using multiple databases can quickly create, activate, deactivate or drop databases, enabling them to reduce the overhead of managing separate RDS for Db2 instances. To create multiple databases within an Amazon RDS for Db2 instance, simply set up an RDS instance in the AWS Management Console or using the AWS CLI, then use the create_database stored procedure to create multiple Db2 databases on that RDS instance.

Amazon RDS makes it simple to set up, operate, and scale Db2 deployments in the cloud. To learn more about Amazon RDS for Db2, check Amazon RDS for Db2 User Guide and Amazon RDS for Db2 pricing page for pricing details and regional availability.
 

Amazon Location Service announces the availability of dual-stack endpoints, enabling customers to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual-stack clients. These dual-stack endpoints are accessible through a new AWS DNS domain name, while existing Amazon Location Service endpoints remain available to ensure backward compatibility.

The transition to IPv6 is essential due to the ongoing expansion of the internet, which is rapidly depleting available IPv4 addresses. With simultaneous support for both IPv4 and IPv6 on Amazon Location Service endpoints, customers can gradually migrate their systems and applications to IPv6-based architectures as needed. This flexibility allows businesses to meet IPv6 compliance requirements while maintaining uninterrupted connectivity through IPv4 for those not yet utilizing IPv6.

IPv6 support for Amazon Location Service is now available in all regions where the service is generally available (GA).

See here for a full list of supported endpoints and instructions on how to access them via AWS SDKs and CLI . To learn more about Amazon Location Service, please visit Amazon Location Service Product Page and developer guide .
 

Amazon Connect provides a refreshed experience for configuring hierarchies on the admin website, giving customers better ways to navigate complex organizational structures quickly and accurately. Hierarchies are a way for customers to organize their agents into teams and groups for reporting purposes (e.g. by department, location, or skill sets). Now customers can visualize their tree structure and find resources using free-text type-ahead search. Because this UI is now powered by public APIs, customers can leverage AWS CloudTrail to log, view and audit all changes to hierarchy groups and structures regardless of who made them or how.

The updated UI with AWS CloudTrail support is available in all AWS Regions where Amazon Connect is offered. For more information, see Viewing Events with CloudTrail event history . To learn more about Amazon Connect, the AWS contact center as a service solution on the cloud, please visit the Amazon Connect website .
 

Amazon EventBridge API destinations now support proactive OAuth token refresh for public and private OAuth authorization endpoints. This capability helps you to preemptively mitigate delays and errors during invocations when the OAuth access token is close to expiration.

EventBridge API destinations are HTTPS endpoints that you can invoke as the target of an event bus rule, or pipe, similar to how you invoke an AWS service or resource as a target. Using API destinations, you can route events between AWS services, integrated software as a service (SaaS) applications, and public or private applications by using API calls. Now, when you invoke an API destination with an OAuth token that is close to expiration, EventBridge asynchronously requests a new token from your OAuth endpoint, reducing authorization errors and delays due to expired tokens.

Amazon EventBridge API destinations proactive OAuth token refresh is available at no additional cost across all AWS Regions where EventBridge API destinations is available . Please refer to the API destinations user guide for details.
 

Amazon Connect now records all changes made on the Agent status page as events in AWS CloudTrail. This enables you to look in AWS CloudTrail to identify which admin website user added, updated or disabled an agent status, for example adding ‘Break’ and ‘Training’ to the standard available and offline choices. Now you have the same logging capabilities available on other resources such as users, queues, and flows that help you analyze and monitor changes to your contact center.

The updated UI with AWS CloudTrail support is available in all AWS Regions where Amazon Connect is offered. For more information, see Viewing Events with CloudTrail event history . To learn more about Amazon Connect, the AWS contact center as a service solution on the cloud, please visit the Amazon Connect website .