Pickering Interfaces has announced a family of 1,200V programmable resistor modules in a single-slot PXI or PXIe form factor. 40-230 is the PXI series, and 42-230 boards have a PXIe …

The post 1,200V PXI or PXIe programmable resistors appeared first on Electronics Weekly .

Hamamatsu has introduced a series of non-cooled linear near-infra-red image sensors with up to 256 pixels. Designed for multi-channel spectro-photometry, G1682x devices are front-illuminated InGaAs sensors intended for real-time analysis …

The post 256 pixel linear infra red sensor array appeared first on Electronics Weekly .

Vishay has introduced a series of multi-turn, surface-mount cermet trimmers for industrial use over -55 to +140°C. The 4 x 4mm potentiometers, called the TSM41, are sealed to IP67. They …

The post 4 x 4mm multi-turn trimmers for industrial environments appeared first on Electronics Weekly .

Amazon Q Business, the generative AI-powered assistant for finding information, gaining insight, and taking action at work, today introduced Response Events, a new feature that provides real-time visibility into the assistant’s query processing steps. This capability allows users to observe how their queries are processed, creating transparency and trust in their interactions with Amazon Q Business.

Previously, users had no visibility into how Amazon Q Business processed their queries and generated responses, making it challenging to understand the reasoning behind answers. This lack of transparency created a black-box experience that limited organizations’ ability to audit and trust AI-generated responses. With Response Events, users can now track processing steps in real-time across multiple components: RAG for enterprise-specific knowledge, uploaded files in chat sessions, and interactions with both built-in and custom plugins if enabled.

Response Events are available by default for all chat conversations within Amazon Q Business and in all AWS Regions where Amazon Q Business is available. To learn more about Amazon Q Business how it can enhance your organization’s productivity, visit the Amazon Q Business webpage .

Amazon FSx now offers customers the option to use Internet Protocol version 6 (IPv6) for access to Amazon FSx for OpenZFS file systems.

More and more customers are adopting IPv6 to mitigate IPv4 address exhaustion in their private networks or to satisfy government mandates such as the US Office of Management and Budget (OMB) M-21-07 memorandum. With this launch, customers can now access their file systems using IPv4, IPv6, or dual-stack clients without the need for complex infrastructure to handle IPv6 to IPv4 address translation.

IPv6 support for new FSx for OpenZFS file systems is now available in all AWS Commercial, AWS GovCloud (US), and AWS China regions where Amazon FSx is available, with IPv6 support for existing FSx for OpenZFS file systems coming in an upcoming weekly maintenance window. To learn more, visit the Amazon FSx user guide .

 AWS IAM Identity Center introduces support for user background sessions, a new feature which allows Amazon SageMaker Studio users to initiate long-running jobs that continue to run in the background even after a user logs off from their computer. User background sessions leverage permissions tied to a user’s identity and their corporate directory group associations while accessing data across multiple AWS services including Amazon Athena, Amazon EMR, AWS Lake Formation, Amazon Redshift, and Amazon S3.

Building on IAM Identity Center’s trusted identity propagation (TIP)  capability, this feature allows SageMaker Studio jobs to run for up to 90 days without requiring users to stay signed in. When launching jobs such as SageMaker Training, Processing, or Pipeline executions, IAM Identity Center creates a new user background session that runs independently until job completion or the background session duration limit is reached, whichever comes first. Administrators can track the creation of user background sessions via AWS CloudTrail events, update the background session duration for their IAM Identity Center instance and terminate background sessions for different users in their organization.

AWS IAM Identity Center helps you securely connect your workforce identities and manage their access centrally across AWS applications. For more information on user background sessions, see here . For the list of supported regions and compatible AWS services supported with user background sessions, refer to the Amazon SageMaker Studio page, linked here . 

Today, AWS Resource Explorer introduces support for filtering on multiple values in both the Search and ListResources APIs. This new feature allows customers to build targeted queries to find resources more easily.

The new filtering feature allows customers to search for resources based on multiple criteria simultaneously, improving upon the previous process where they had to query each individual facet and combine the search results. For example, customers can now find all storage-types tagged as non-production by querying “tag.key:environment tag.value:dev,test,integ service:dynamodb,rds,ebs…”. Importantly, customers with large AWS Organizations can now scope their Resource Explorer Views to specific listed accounts, rather than being scoped to an entire Organization or Organizational Unit. To scope multi-account views to a specific set of accounts, add a view filter with the “account:” operator, and a comma-separated list of account IDs to be included in search results.

This feature is available in all AWS Regions where AWS Resource Explorer is supported. For specific regional availability, please refer to the AWS Regional Services List .

To learn more about this new feature visit the AWS Resource Explorer documentation page . You can start using this enhanced querying capability immediately through the AWS Management Console, AWS CLI, or AWS SDKs.

Today, Amazon Elastic Kubernetes Service (Amazon EKS) expands support for Cilium as the Container Networking Interface (CNI) for Amazon EKS Hybrid Nodes. Cilium is a Cloud-Native Computing Foundation (CNCF) graduated project that provides core networking capabilities for Kubernetes workloads. Now, you can receive support from AWS for a broader set of Cilium features when using Cilium with Amazon EKS Hybrid Nodes including application ingress, in-cluster load balancing, Kubernetes network policies, and kube-proxy replacement mode.

Kubernetes clusters require a CNI for connectivity between pods running in the cluster, but most Kubernetes applications require additional components, such as ingress controllers and load balancers, to serve and secure network traffic with other external systems or users. These additional capabilities are integrated features of Cilium, built on Cilium’s eBPF-powered networking and security. Now, Amazon EKS Hybrid Nodes users can receive support from AWS for Cilium’s Ingress and Gateway features, Border Gateway Protocol (BGP) Control Plane, Load Balancer IP Address Management (LB IPAM), kube-proxy replacement, and Kubernetes network policies.

AWS supports the Amazon VPC CNI for Amazon EKS nodes in AWS Cloud, which is optimized for Amazon VPC networking with built-in features such as enhanced subnet discovery, Kubernetes network policies, and multiple network interfaces per pod. Cilium support for Amazon EKS Hybrid Nodes is available in all AWS Regions where Amazon EKS Hybrid Nodes is available. To learn more about Cilium support for Amazon EKS Hybrid Nodes, see Configure CNI for hybrid nodes in the Amazon EKS User Guide.

AWS Security Incident Response now allows you to choose membership coverage for specific AWS organizational units (OUs) within an AWS Organization. While memberships previously covered all accounts in the selected AWS Organization, you now have the flexibility to choose which OUs to cover making it easier to try out the service and support your existing IR processes. 

AWS Security Incident Response combines the power of automated monitoring and investigation, accelerated communication and coordination, and direct 24/7 access to the AWS Customer Incident Response Team (CIRT) to quickly prepare for, respond to, and recover from security events. This new feature allows you to enable Security Incident Response for specific types of workloads, such as production workloads, or for specific business subsidiaries that are grouped as OUs in their AWS Organization. You can also start with a pilot OU to evaluate the service’s effectiveness and refine processes before expanding coverage to your entire AWS Organization. All accounts within the selected OUs, including accounts under child OUs, are covered by the membership. Accounts added or removed from selected OUs will automatically update the coverage, making it easy for you to manage your AWS Security Incident Response membership.

Get started today by visiting AWS Security Incident Response via the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kit (SDK). To learn more, see the AWS Security Incident Response documentation . For additional information on managing OUs with AWS Organizations, visit the AWS Organizations page .

We are excited to announce that Amazon SageMaker Studio now supports trusted identity propagation  (TIP), enabling admins to trace actions taken in SageMaker Studio back to a human user. It also enables administrators to manage permissions based on user identity to AWS Lake Formation and Amazon S3 Access Grants .

Starting today, SageMaker Studio now supports trusted identity propagation for AWS services, including AWS Lake Formation, Amazon S3, Amazon EMR, Amazon EMR-Serverless, Amazon Redshift and Amazon Athena. Customers can enable trusted identity propagation for SageMaker Studio domains, either at domain creation or while updating an existing domain. With this capability, customers can apply fine grained access controls using S3 Access Grants, Lake Formation, or Redshift Data APIs to govern user access to data in their SageMaker Studio notebooks. Customers’ Training and Processing jobs in Studio notebooks will integrate with S3 Access Grants.

With this change, administrators can trace creation of user interactive sessions as well as user background sessions across Studio applications (JupyterLab and CodeEditor) via AWS CloudTrail events . As an example, administrators can now track which user creates SageMaker Pipeline steps to run experiments using SageMaker MLFlow, trains ML models using SageMaker Training, and deploys using SageMaker Inference.

This feature is available in all AWS Regions where Amazon SageMaker Studio with AWS IAM Identity Center support is currently available, excluding China regions, and GovCloud (US) regions. To learn more, visit our documentation .