Today, AWS IoT Device Management announces the preview of managed integrations, a new feature that enables you to simplify control and management of a diverse set of devices across multiple manufacturers and connectivity protocols. The new feature helps you streamline cloud onboarding of Internet of Things (IoT) devices and enables you to control both self-managed and third-party devices, including cloud-based devices, from a single application.

Managed integrations provides cloud and device Software Development Kits (SDKs) for device connectivity and protocol support for ZigBee, Z-Wave, and Wi-Fi specifications, eliminating the need to handle dedicated connectivity protocols from different manufacturers separately. A unified API coupled with a catalog of cloud-to-cloud connectors and 80+ device data model templates enable you to control both proprietary and third-party devices from a single application. Additionally, you can easily process and integrate device data from those devices for building home security, energy management, and elderly care monitoring solutions. Managed integrations for AWS IoT Device Management also provides built-in capabilities for barcode scanning and direct pairing of devices, delivering additional mechanisms to simplify device onboarding and integration complexities.

The managed integrations feature is available in Canada (Central) and Europe (Ireland) AWS Regions. To learn more, see technical documentation and read this blog. To get started, log in to the AWS IoT console or use the AWS Command Line Interface (AWS CLI).

​Today, AWS IoT Device Management announces the preview of managed integrations, a new feature that enables you to simplify control and management of a diverse set of devices across multiple manufacturers and connectivity protocols. The new feature helps you streamline cloud onboarding of Internet of Things (IoT) devices and enables you to control both self-managed and third-party devices, including cloud-based devices, from a single application. Managed integrations provides cloud and device Software Development Kits (SDKs) for device connectivity and protocol support for ZigBee, Z-Wave, and Wi-Fi specifications, eliminating the need to handle dedicated connectivity protocols from different manufacturers separately. A unified API coupled with a catalog of cloud-to-cloud connectors and 80+ device data model templates enable you to control both proprietary and third-party devices from a single application. Additionally, you can easily process and integrate device data from those devices for building home security, energy management, and elderly care monitoring solutions. Managed integrations for AWS IoT Device Management also provides built-in capabilities for barcode scanning and direct pairing of devices, delivering additional mechanisms to simplify device onboarding and integration complexities. The managed integrations feature is available in Canada (Central) and Europe (Ireland) AWS Regions. To learn more, see technical documentation and read this blog. To get started, log in to the AWS IoT console or use the AWS Command Line Interface (AWS CLI).  

AWS announces the preview of new AWS Outposts racks designed specifically for on-premises high throughput, network-intensive workloads. With these new Outposts racks, telecom service providers (telcos) can extend AWS infrastructure and services to telco locations, enabling them to deploy on-premises network functions requiring low latency, high throughput, and real-time performance.

The new Outposts racks feature new Amazon Elastic Compute Cloud (Amazon EC2) 4th Generation Intel Xeon Scalable-based (Sapphire Rapids) bare metal instances along with a high-performance bare metal network fabric. This architecture delivers the low latency and high throughput required for demanding 5G workloads, such as User Plane Function (UPF) and Radio Access Network (RAN) Central Unit (CU) network functions.

Telcos can now use Amazon EKS (Elastic Kubernetes Service) and built-in EKS add-ons to automate deployment and scaling of micro-services based 5G network functions for high throughput and performance. Telcos can now use the same AWS infrastructure, AWS services, APIs, tools, and a common continuous integration and continuous delivery (CI/CD) pipeline wherever their workloads reside. This consistent cloud experience eases operational burden, reduces integration costs, and maximizes new feature development velocity for operators.

The new AWS Outposts racks are currently available in preview in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Singapore).
 

​AWS announces the preview of new AWS Outposts racks designed specifically for on-premises high throughput, network-intensive workloads. With these new Outposts racks, telecom service providers (telcos) can extend AWS infrastructure and services to telco locations, enabling them to deploy on-premises network functions requiring low latency, high throughput, and real-time performance. The new Outposts racks feature new Amazon Elastic Compute Cloud (Amazon EC2) 4th Generation Intel Xeon Scalable-based (Sapphire Rapids) bare metal instances along with a high-performance bare metal network fabric. This architecture delivers the low latency and high throughput required for demanding 5G workloads, such as User Plane Function (UPF) and Radio Access Network (RAN) Central Unit (CU) network functions. Telcos can now use Amazon EKS (Elastic Kubernetes Service) and built-in EKS add-ons to automate deployment and scaling of micro-services based 5G network functions for high throughput and performance. Telcos can now use the same AWS infrastructure, AWS services, APIs, tools, and a common continuous integration and continuous delivery (CI/CD) pipeline wherever their workloads reside. This consistent cloud experience eases operational burden, reduces integration costs, and maximizes new feature development velocity for operators. The new AWS Outposts racks are currently available in preview in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), and Asia Pacific (Singapore).    

Amazon Connect now supports outbound campaign calling to Brazil in the US East (Virginia) and US West (Oregon) regions, making it easier to proactively communicate across voice, SMS, and email for use cases such as delivery notifications, marketing promotions, appointment reminders, or debt collection. Communication capabilities include features such as point-of-dial checks, calling controls for time of day, time zone, number of attempts per contact, and predictive dialing with integrated voicemail detection. A list management capability provided by Amazon Pinpoint can also be used to build customer journeys and multi-channel user contact experiences. Outbound campaigns can be enabled within the AWS Connect Console.

With Amazon Connect outbound campaigns, you only pay-as-you-go for the high-volume outbound service usage, associated telephony charges and any monthly target audience charges via Amazon Pinpoint. To learn more, visit our webpage.

​Amazon Connect now supports outbound campaign calling to Brazil in the US East (Virginia) and US West (Oregon) regions, making it easier to proactively communicate across voice, SMS, and email for use cases such as delivery notifications, marketing promotions, appointment reminders, or debt collection. Communication capabilities include features such as point-of-dial checks, calling controls for time of day, time zone, number of attempts per contact, and predictive dialing with integrated voicemail detection. A list management capability provided by Amazon Pinpoint can also be used to build customer journeys and multi-channel user contact experiences. Outbound campaigns can be enabled within the AWS Connect Console. With Amazon Connect outbound campaigns, you only pay-as-you-go for the high-volume outbound service usage, associated telephony charges and any monthly target audience charges via Amazon Pinpoint. To learn more, visit our webpage.  

AWS Amplify now supports HttpOnly cookies for server-rendered Next.js applications when using Amazon Cognito’s Managed Login. This enhancement builds upon existing cookie functionality in server-rendered sites, opting in to the HttpOnly attribute strengthens your application’s security posture by blocking client-side JavaScript from accessing cookie contents.

With HttpOnly cookies, your applications gain an additional layer of protection against cross-site scripting (XSS) attacks. This ensures that sensitive information remains secure and will only be transmitted between the browser and the server, and is particularly valuable when handling authentication tokens in your web applications. The contents of cookies with HttpOnly attributes can only be read by the server, requiring your requests to flow through the server before reaching other services.

This feature is now available in all AWS regions where AWS Amplify and Amazon Cognito are supported.

To learn more, visit the AWS Amplify documentation for Server-Side Rendering.

​AWS Amplify now supports HttpOnly cookies for server-rendered Next.js applications when using Amazon Cognito’s Managed Login. This enhancement builds upon existing cookie functionality in server-rendered sites, opting in to the HttpOnly attribute strengthens your application’s security posture by blocking client-side JavaScript from accessing cookie contents. With HttpOnly cookies, your applications gain an additional layer of protection against cross-site scripting (XSS) attacks. This ensures that sensitive information remains secure and will only be transmitted between the browser and the server, and is particularly valuable when handling authentication tokens in your web applications. The contents of cookies with HttpOnly attributes can only be read by the server, requiring your requests to flow through the server before reaching other services. This feature is now available in all AWS regions where AWS Amplify and Amazon Cognito are supported. To learn more, visit the AWS Amplify documentation for Server-Side Rendering.  

The post Conozcan Microsoft Dragon Copilot: su nuevo asistente de IA para el flujo de trabajo clínico appeared first on Source LATAM.

​The post Conozcan Microsoft Dragon Copilot: su nuevo asistente de IA para el flujo de trabajo clínico appeared first on Source LATAM.  

Amazon Connect now allows agents to exchange shifts with each other, providing greater schedule flexibility without compromising service levels. With this launch, agents can initiate shift trades directly, allowing them to manage unexpected life events without using time off. Additionally, contact center managers can now automate some approvals while ensuring others are approved manually — reducing admin work without sacrificing controls when needed. For example, supervisors can automate approvals for agents handling non-critical tasks, such as routine customer inquiries, while manually approving requests from agents who handle sensitive customer segments, like healthcare or high-value enterprise accounts.

This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more and get started, visit the Amazon Connect agent scheduling guide or watch the Amazon Connect Enablement shift exchange videos, for a step by step walkthrough of this feature.

​Amazon Connect now allows agents to exchange shifts with each other, providing greater schedule flexibility without compromising service levels. With this launch, agents can initiate shift trades directly, allowing them to manage unexpected life events without using time off. Additionally, contact center managers can now automate some approvals while ensuring others are approved manually — reducing admin work without sacrificing controls when needed. For example, supervisors can automate approvals for agents handling non-critical tasks, such as routine customer inquiries, while manually approving requests from agents who handle sensitive customer segments, like healthcare or high-value enterprise accounts. This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more and get started, visit the Amazon Connect agent scheduling guide or watch the Amazon Connect Enablement shift exchange videos, for a step by step walkthrough of this feature.  

Amazon Data Lifecycle Manager now supports AWS PrivateLink to connect directly to the Amazon Data Lifecycle Manager APIs in your virtual private cloud (VPC) instead of connecting over the internet.

Customers create Amazon Data Lifecycle Manager policies to automate the creation, retention, and management of EBS Snapshots and EBS-backed Amazon Machine Images (AMIs). When you use AWS PrivateLink to access Amazon Data Lifecycle Manager APIs, communication between your VPC and Amazon Data Lifecycle Manager API is conducted privately within the AWS network, providing a secure pathway for your data. An AWS PrivateLink endpoint connects your VPC directly to the Amazon Data Lifecycle Manager API.

This feature is available in all AWS Regions where Amazon Data Lifecycle Manager is available. You can create an AWS PrivateLink to connect to Amazon Data Lifecycle Manager using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands. To learn more about using AWS PrivateLink, please refer to our documentation.

​Amazon Data Lifecycle Manager now supports AWS PrivateLink to connect directly to the Amazon Data Lifecycle Manager APIs in your virtual private cloud (VPC) instead of connecting over the internet. Customers create Amazon Data Lifecycle Manager policies to automate the creation, retention, and management of EBS Snapshots and EBS-backed Amazon Machine Images (AMIs). When you use AWS PrivateLink to access Amazon Data Lifecycle Manager APIs, communication between your VPC and Amazon Data Lifecycle Manager API is conducted privately within the AWS network, providing a secure pathway for your data. An AWS PrivateLink endpoint connects your VPC directly to the Amazon Data Lifecycle Manager API. This feature is available in all AWS Regions where Amazon Data Lifecycle Manager is available. You can create an AWS PrivateLink to connect to Amazon Data Lifecycle Manager using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands. To learn more about using AWS PrivateLink, please refer to our documentation.  

Amazon Connect Contact Lens now provides generative AI-powered contact categorization in five additional regions, making it easy to identify top drivers, customer experience, and agent behavior for your contacts. With this launch, you can use natural language instructions to define a criteria to automatically categorize customer contacts (e.g., “show me calls where customers attempted payment”). Contact Lens automatically labels interactions matching your criteria and extracts relevant conversation points. In addition, you can receive alerts and generate tasks on categorized contacts, and search for contacts using the automated labels. This feature helps managers easily categorize contacts for scenarios such as identifying customer interest in specific products, assessing customer satisfaction, monitoring whether agents exhibited professional behavior on calls, and more.

This feature is supported in English language and is available in five additional AWS regions including Europe (London), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney) and Canada (Central). To learn more, please visit our documentation and our webpage. This feature is included within Contact Lens conversational analytics price at no additional cost. For information about Contact Lens pricing, please visit our pricing page.

​Amazon Connect Contact Lens now provides generative AI-powered contact categorization in five additional regions, making it easy to identify top drivers, customer experience, and agent behavior for your contacts. With this launch, you can use natural language instructions to define a criteria to automatically categorize customer contacts (e.g., “show me calls where customers attempted payment”). Contact Lens automatically labels interactions matching your criteria and extracts relevant conversation points. In addition, you can receive alerts and generate tasks on categorized contacts, and search for contacts using the automated labels. This feature helps managers easily categorize contacts for scenarios such as identifying customer interest in specific products, assessing customer satisfaction, monitoring whether agents exhibited professional behavior on calls, and more. This feature is supported in English language and is available in five additional AWS regions including Europe (London), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney) and Canada (Central). To learn more, please visit our documentation and our webpage. This feature is included within Contact Lens conversational analytics price at no additional cost. For information about Contact Lens pricing, please visit our pricing page.  

Starting today, EC2 Fleet customers can override the Block Device Mapping specified in the Launch Template when launching a new fleet. With this release, customers save the effort of creating and associating new Launch Templates with their fleet requests, when they need to customize the Block Device Mapping but keep rest of the instance configurations the same.

Customers use EC2 Fleet to access wider EC2 capacity across instance types and availability zones within a single launch request. To provide their EC2 instance configurations such as Amazon Machine Images, Key pair etc, customers associate a Launch Template with their Fleet requests. They can override the values specified for select parameters in the Launch Template for each instance type. With this release, customers can also override Block Device Mapping parameters specified in the Launch Template. With Block Device Mapping, customers can launch additional EBS volumes or instance store volumes to attach to an instance, or update the Block Device Mapping specified in the Amazon Machine Image that you use to launch the instances.

The feature is available in all commercial AWS regions and the AWS GovCloud (US) Regions. To learn more, refer the API references and EC2 user guide.

​Starting today, EC2 Fleet customers can override the Block Device Mapping specified in the Launch Template when launching a new fleet. With this release, customers save the effort of creating and associating new Launch Templates with their fleet requests, when they need to customize the Block Device Mapping but keep rest of the instance configurations the same. Customers use EC2 Fleet to access wider EC2 capacity across instance types and availability zones within a single launch request. To provide their EC2 instance configurations such as Amazon Machine Images, Key pair etc, customers associate a Launch Template with their Fleet requests. They can override the values specified for select parameters in the Launch Template for each instance type. With this release, customers can also override Block Device Mapping parameters specified in the Launch Template. With Block Device Mapping, customers can launch additional EBS volumes or instance store volumes to attach to an instance, or update the Block Device Mapping specified in the Amazon Machine Image that you use to launch the instances. The feature is available in all commercial AWS regions and the AWS GovCloud (US) Regions. To learn more, refer the API references and EC2 user guide.  

AWS Elastic Beanstalk now enables customers to build and deploy Tomcat 11 applications on Amazon Linux 2023 (AL2023) platform. This latest platform support allows developers to leverage the newest Tomcat features while benefiting from AL2023’s enhanced security and performance features.

AWS Elastic Beanstalk is a service that provides the ability to deploy and manage applications in AWS without worrying about the infrastructure that runs those applications. Tomcat 11 on AL2023 allows developers to take advantage of the latest Jakarta EE specifications. Developers can create Elastic Beanstalk environments running Corretto 17 and 21 with Tomcat 11 on AL2023 through the Elastic Beanstalk Console, CLI, or API.

This platform is generally available in commercial regions where Elastic Beanstalk is available including the AWS GovCloud (US) Regions. For a complete list of regions and service offerings, see AWS Regions.

For more information about Corretto 17 and 21 with Tomcat 11 and Linux Platforms, see the Elastic Beanstalk developer guide. To learn more about Elastic Beanstalk, visit the Elastic Beanstalk product page.

​AWS Elastic Beanstalk now enables customers to build and deploy Tomcat 11 applications on Amazon Linux 2023 (AL2023) platform. This latest platform support allows developers to leverage the newest Tomcat features while benefiting from AL2023’s enhanced security and performance features.
AWS Elastic Beanstalk is a service that provides the ability to deploy and manage applications in AWS without worrying about the infrastructure that runs those applications. Tomcat 11 on AL2023 allows developers to take advantage of the latest Jakarta EE specifications. Developers can create Elastic Beanstalk environments running Corretto 17 and 21 with Tomcat 11 on AL2023 through the Elastic Beanstalk Console, CLI, or API.
This platform is generally available in commercial regions where Elastic Beanstalk is available including the AWS GovCloud (US) Regions. For a complete list of regions and service offerings, see AWS Regions.
For more information about Corretto 17 and 21 with Tomcat 11 and Linux Platforms, see the Elastic Beanstalk developer guide. To learn more about Elastic Beanstalk, visit the Elastic Beanstalk product page.