Publicado el Deja un comentario

Amplify Hosting announces support for IAM roles for server-side rendered (SSR) applications

We’re excited to announce the launch of IAM compute roles for AWS Amplify Hosting, enabling secure connections to other AWS resources from server-side rendered applications. This allows developers to integrate their SSR applications with AWS services while maintaining robust security practices.

Use Cases Unlocked:

  • Secure credential management for SSR applications
  • Direct integration with AWS services like Secrets Manager and Parameter Store
  • Support for database connections (RDS, DynamoDB)
  • Granular permission controls
  • Branch-specific role configurations

This feature is available in all 20 AWS Amplify Hosting regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Osaka) Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Milan), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain) and South America (São Paulo).

To learn more, read the documentation. To get started with a tutorial, check out our blog post.

 

​We’re excited to announce the launch of IAM compute roles for AWS Amplify Hosting, enabling secure connections to other AWS resources from server-side rendered applications. This allows developers to integrate their SSR applications with AWS services while maintaining robust security practices.
Use Cases Unlocked:

Secure credential management for SSR applications
Direct integration with AWS services like Secrets Manager and Parameter Store
Support for database connections (RDS, DynamoDB)
Granular permission controls
Branch-specific role configurations

This feature is available in all 20 AWS Amplify Hosting regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Osaka) Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Milan), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain) and South America (São Paulo).
To learn more, read the documentation. To get started with a tutorial, check out our blog post.  

Publicado el Deja un comentario

AWS Storage Gateway is now available in AWS Mexico (Central) Region

AWS Storage Gateway expands availability to the AWS Mexico (Central) Region enabling customers to deploy and manage hybrid cloud storage for their on-premises workloads.

AWS Storage Gateway is a hybrid cloud storage service that provides on-premises applications access to virtually unlimited storage in the cloud. You can use AWS Storage Gateway for backing up and archiving data to AWS, providing on-premises file shares backed by cloud storage, and providing on-premises applications low latency access to data in the cloud.

Visit the AWS Storage Gateway product page to learn more. Access the AWS Storage Gateway console to get started. To see all the Regions where AWS Storage Gateway is available, please visit the AWS Region table.
 

 

​AWS Storage Gateway expands availability to the AWS Mexico (Central) Region enabling customers to deploy and manage hybrid cloud storage for their on-premises workloads. AWS Storage Gateway is a hybrid cloud storage service that provides on-premises applications access to virtually unlimited storage in the cloud. You can use AWS Storage Gateway for backing up and archiving data to AWS, providing on-premises file shares backed by cloud storage, and providing on-premises applications low latency access to data in the cloud. Visit the AWS Storage Gateway product page to learn more. Access the AWS Storage Gateway console to get started. To see all the Regions where AWS Storage Gateway is available, please visit the AWS Region table.    

Publicado el Deja un comentario

Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá

febrero 18, 2025

Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá

Por: Kees Hertogh, vicepresidente de marketing de salud y ciencias de la vida.

En el panorama sanitario actual, que evoluciona con rapidez, la transformación digital ya no es un lujo, sino una necesidad. Uno de los componentes más críticos de esta transformación es el sistema de historia clínica electrónica (HCE), que desempeña un papel fundamental en las operaciones de atención médica y la prestación de atención. Las organizaciones exploran de manera activa alternativas para sus infraestructuras locales tradicionales para superar desafíos significativos, incluidos los altos gastos de capital, los frecuentes y costosos ciclos de actualización de hardware, los protocolos de seguridad obsoletos y, lo que es más importante, la administración de la red de datos de los sistemas en silos. Al aprovechar los sistemas EHR conectados en la nube, los proveedores también pueden desbloquear todo el potencial de sus datos y ofrecer aún más innovaciones de IA basadas en datos.

Azure para cargas de trabajo críticas

La migración de sistemas EHR a Microsoft Azure proporciona a las organizaciones sanitarias una plataforma sólida para cargas de trabajo de misión crítica, lo que garantiza un rendimiento optimizado, un acceso rápido a los datos, una recuperación ante desastres integrada y funciones de seguridad mejoradas, como la detección de amenazas impulsada por IA y la supervisión automatizada del cumplimiento. Además, Azure maximiza las inversiones en la nube, al ofrecer nuevas posibilidades para aprovechar los datos y aprovechar las innovaciones de IA.

Los datos están en el corazón de la atención médica. Los hospitales producen más de 50 petabytes de datos en más de 10 sistemas aislados cada año. A medida que el sector sanitario se enfrenta al doble reto de gestionar grandes cantidades de datos no estructurados y a la escasez de mano de obra, hasta el 97% de los datos sanitarios no se utilizan, lo que pone de manifiesto una importante oportunidad perdida para la excelencia operativa y un mejor conocimiento de los pacientes.1 Una de las mayores ventajas para los clientes sanitarios de Azure es la capacidad de unificar sus datos sanitarios multimodales para el análisis y la inteligencia artificial con soluciones de  datos sanitarios de Microsoft Fabric que les permite ingerir, almacenar y analizar datos de diversos orígenes y modalidades. Mientras que Fabric unifica los datos, Microsoft Purview ofrece el servicio de gobernanza de datos que les ayuda a clasificar los datos en todo el patrimonio de datos, incluida la identificación de datos confidenciales. La integración de Microsoft Purview con las soluciones de datos sanitarios en Fabric no solo refuerza la seguridad, sino que también les ayuda a garantizar el cumplimiento, lo que permite a las organizaciones sanitarias gobernar sus datos con confianza. Somos muy conscientes de las expectativas del sector en el que se utiliza nuestra tecnología, y esta es una de las muchas razones por las que nuestros clientes sanitarios confían en Azure para las cargas de trabajo críticas.

A medida que ofrecemos innovaciones de datos, vemos que nuestros clientes utilizan sus datos conectados en un amplio espectro de capacidades de IA. Con Azure AI, las organizaciones sanitarias pueden acelerar la innovación a través de análisis predictivos, automatizar las tareas clínicas y mejorar las interacciones con los pacientes con la ayuda de soluciones de IA ambiental como DAX Copilot (integrado de manera directa en los sistemas EHR), así como aprovechar  los modelos de IA para el sector sanitario de Microsoft en Azure AI Foundry y GitHub, una colección de modelos de IA generativa multimodal de última generación que benefician a los flujos de trabajo de imágenes y radiología.

Soporte mejorado para misiones críticas

Las cargas de trabajo de misión crítica exigen un soporte integral. En 2024, Microsoft Unified mejoró su soporte para cargas de trabajo de misión crítica en la atención médica a través de sus ofertas de misión crítica. Esta iniciativa proporciona apoyo proactivo para mejorar la salud, la resiliencia y el rendimiento de los sistemas de atención médica a través de evaluaciones periódicas, orientación y recomendaciones de optimización, lo que garantiza la continuidad del negocio y aborda los desafíos únicos de la atención médica.

Colaboración para la excelencia tecnológica: una asociación estratégica que se destaca

Nuestro compromiso con la misión crítica se refleja en nuestras colaboraciones con los principales proveedores de EHR, como Epic®. Esta larga relación de más de 20 años ha dado lugar a una solución optimizada para Epic® en Azure, que ofrece una plataforma sólida y diseñada de manera especial, respaldada por una arquitectura de referencia conjunta. De manera reciente, Microsoft anunció la ampliación de la escalabilidad en Azure para las organizaciones sanitarias, en concreto para ejecutar la base de datos operativa (ODB, por sus siglas en inglés) Chronicles* de Epic®, para aumentar su capacidad a 65 millones de referencias globales por segundo (GRefs/s), lo que supone una mejora del 171% con respecto a 2023 en la nueva serie de máquinas virtuales Mbv3.

La colaboración con Epic® se extiende mucho más allá de la infraestructura de la nube, a varios productos y capacidades que forman parte de Microsoft Cloud for Healthcare. Epic® y Microsoft han ampliado su colaboración para integrar tecnologías avanzadas de IA como Microsoft Azure OpenAI Service y DAX Copilot en el sistema EHR de Epic®. La integración ayuda a proporcionar información clínica impulsada por IA, agilizar los procesos administrativos y mejorar la productividad de los médicos a través de funciones como el resumen de notas y las sugerencias de codificación automatizadas.

Ofrecer valor más allá de la infraestructura: la promesa de Microsoft Cloud for Healthcare

La asociación integral de Microsoft con Epic® es una de las muchas razones por las que Azure es la nube elegida por muchos de nuestros clientes de atención médica.

La decisión de trasladar las cargas de trabajo de misión crítica a la nube a menudo no se trata solo de la infraestructura. Clientes como Mercy eligieron Azure no solo para modernizar su infraestructura, sino también para extraer valor de archivos de datos de gran tamaño. La transformación digital de Mercy en Azure le permitió conectar datos antes aislados y usar varios servicios de Microsoft, como Azure Data Lake, para obtener resultados comerciales positivos. Por ejemplo, al dotar a los equipos de atención de los equipos de atención de paneles inteligentes y de información sobre los factores que determinan el alta de los pacientes, Mercy ha podido reducir de manera significativa la duración de las estancias de los pacientes. Mercy emplea Azure AI Document Intelligence para escanear y reconocer la información de las tarjetas de seguro de los pacientes, que luego se actualiza automáticamente en sus registros de EHR.

Reconocemos el deseo de nuestros clientes de tener una transformación digital completa en la nube que trascienda todas las capas de la pila, y Microsoft Cloud for Healthcare nos permite cumplir esa promesa. Encapsula un amplio espectro de innovaciones de datos e inteligencia artificial de Microsoft, diseñadas en específico para la industria de la salud, lo que permite a nuestros clientes alcanzar sus objetivos en la nube de manera más rápida y sencilla. De manera reciente, Microsoft anunció varias innovaciones como parte de la cartera, incluidos nuevos modelos de IA  para el cuidado de la salud en Azure AI Foundry, capacidades para soluciones de datos de atención médica en Microsoft Fabric, el servicio de agente de atención médica en Copilot Studio y una solución de flujo de trabajo de enfermería impulsada por IA.

A medida que los clientes se dan cuenta del valor de consolidar sus inversiones en TI en torno a un único proveedor, Azure se adopta cada vez más para las cargas de trabajo críticas. Al conectar y ofrecer valor sin problemas en todas las capas de la pila, Azure para misión crítica amplía el retorno de las inversiones en la nube de un cliente. Clientes como St. Luke’s University Health System cosechan los beneficios de su migración de Epic® a Azure al aprovechar varias sinergias en la cartera de Microsoft, como la interoperabilidad de Microsoft Teams con Epic®. La seguridad es de suma importancia cuando se trata de registros de pacientes, y clientes como Jefferson Health migran sus entornos de Epic® a Azure con gran confianza con Microsoft Defender para la detección y respuesta de puntos de conexión.

Pasos siguientes

A medida que continuamos con la transformación de las cargas de trabajo de misión crítica en la nube, facilitamos a nuestros socios y clientes la creación de experiencias conectadas en cada punto de atención, empoderar a su personal de atención médica y desbloquear el valor de sus datos, todo con privacidad y seguridad sin concesiones. Microsoft Cloud for Healthcare apoya a las organizaciones sanitarias en cada paso de su recorrido hacia la configuración de un futuro más saludable.

*Epic® y Chronicles son marcas comerciales de Epic Systems Corporation.

1 Foro Económico Mundial, 4 maneras en que los datos mejoran la atención médica, diciembre de 2019.

The post Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá appeared first on Source LATAM.

 

​The post Azure para cargas de trabajo críticas en el sector sanitario: EHR y más allá appeared first on Source LATAM.  

Publicado el Deja un comentario

AWS Lambda adds application performance monitoring (APM) for Java and .NET runtimes via Application Signals

AWS Lambda now supports Amazon CloudWatch Application Signals, an application performance monitoring (APM) solution, for Java and .NET managed runtimes, enabling developers and operators to easily monitor the health and performance of their serverless applications built using Lambda.

We previously announced support for Application Signals for Lambda functions for Python and Node.js managed runtimes. With this launch, you can now enable Application Signals for Lambda functions using Java 11, Java 17, Java 21, and .NET 8 Lambda managed runtimes. Once enabled, Application Signals provides pre-built, standardized dashboards for critical application metrics (such as throughput, availability, latency, faults, and errors), correlated traces, and interactions between the Lambda function and its dependencies (such as other AWS services), without requiring any manual instrumentation or code changes from developers. This gives operators a single-pane-of-glass view of the health of the application and enables them to drill down to establish the root cause of performance anomalies.

To get started, visit the Configuration tab in Lambda console and enable Application Signals for your function with just one click in the “Monitoring and operational tools” section. To learn more, visit the Lambda developer guide, Application Signals developer guide, and Application Signals for Lambda blog post.

Application Signals for Lambda is available in all commercial AWS Regions where Lambda and CloudWatch Application Signals are available. To take advantage of the new, cost-effective pricing for Application Signals, opt-in to the Transaction Search capability of Application Signals. To learn more about Application Signals pricing, visit the CloudWatch pricing page.
 

 

​AWS Lambda now supports Amazon CloudWatch Application Signals, an application performance monitoring (APM) solution, for Java and .NET managed runtimes, enabling developers and operators to easily monitor the health and performance of their serverless applications built using Lambda. We previously announced support for Application Signals for Lambda functions for Python and Node.js managed runtimes. With this launch, you can now enable Application Signals for Lambda functions using Java 11, Java 17, Java 21, and .NET 8 Lambda managed runtimes. Once enabled, Application Signals provides pre-built, standardized dashboards for critical application metrics (such as throughput, availability, latency, faults, and errors), correlated traces, and interactions between the Lambda function and its dependencies (such as other AWS services), without requiring any manual instrumentation or code changes from developers. This gives operators a single-pane-of-glass view of the health of the application and enables them to drill down to establish the root cause of performance anomalies. To get started, visit the Configuration tab in Lambda console and enable Application Signals for your function with just one click in the “Monitoring and operational tools” section. To learn more, visit the Lambda developer guide, Application Signals developer guide, and Application Signals for Lambda blog post. Application Signals for Lambda is available in all commercial AWS Regions where Lambda and CloudWatch Application Signals are available. To take advantage of the new, cost-effective pricing for Application Signals, opt-in to the Transaction Search capability of Application Signals. To learn more about Application Signals pricing, visit the CloudWatch pricing page.    

Publicado el Deja un comentario

Amazon Q Developer now supports upgrade to Java 21

Amazon Q Developer transformation capabilities that allow customers to upgrade Java applications using Maven to Java 21 are now available. Developers interested in leveraging the enhanced performance, security, interoperability, and modern features of Java 21 can use the generative AI capabilities of Amazon Q Developer to accelerate code upgrades to Java 21.

With this added support for Java Development Kit (JDK) 21, customers can upgrade the Java version of their applications using Maven from source versions 8, 11, 17, or 21 to target versions 17 or 21. Customers can also continue to upgrade libraries and frameworks used in Java 17 or Java 21 compatible applications without upgrading JDK versions. The Java transformation capabilities are available both in IDE (Visual Studio Code and JetBrains IntelliJ IDEA) and CLI (Linux and MacOS).

To learn more, please visit Amazon Q Developer transformation capabilities webpage and documentation.
 

 

​Amazon Q Developer transformation capabilities that allow customers to upgrade Java applications using Maven to Java 21 are now available. Developers interested in leveraging the enhanced performance, security, interoperability, and modern features of Java 21 can use the generative AI capabilities of Amazon Q Developer to accelerate code upgrades to Java 21. With this added support for Java Development Kit (JDK) 21, customers can upgrade the Java version of their applications using Maven from source versions 8, 11, 17, or 21 to target versions 17 or 21. Customers can also continue to upgrade libraries and frameworks used in Java 17 or Java 21 compatible applications without upgrading JDK versions. The Java transformation capabilities are available both in IDE (Visual Studio Code and JetBrains IntelliJ IDEA) and CLI (Linux and MacOS). To learn more, please visit Amazon Q Developer transformation capabilities webpage and documentation.    

Publicado el Deja un comentario

Amazon SES now offers tiered pricing for Virtual Deliverability Manager

Today, Amazon Simple Email Service (SES) launched a new pricing structure for Virtual Deliverability Manager (VDM), giving customers reduced charges at higher levels of usage. Customers can benefit from lower total VDM charges without the need to change account configuration, sending practices, or billing setup. This can lower customer total cost of ownership for VDM as their usage increases.

Previously, all customers using VDM paid a fixed price per message sent. Customers could turn VDM on or off whenever needed, and they paid only for what they used without any commitment or fixed monthly charges. Now, customers will see their charges per message for VDM decrease as their sending volume exceeds specific thresholds each month. After crossing each threshold in a given billing month, each subsequent message processed by VDM is charged at a lower rate. This reduces the total cost of using VDM for high volume senders.

SES supports tiered pricing for VDM in all AWS regions where SES is available.

For more information, see the documentation for the SES pricing page.

 

​Today, Amazon Simple Email Service (SES) launched a new pricing structure for Virtual Deliverability Manager (VDM), giving customers reduced charges at higher levels of usage. Customers can benefit from lower total VDM charges without the need to change account configuration, sending practices, or billing setup. This can lower customer total cost of ownership for VDM as their usage increases. Previously, all customers using VDM paid a fixed price per message sent. Customers could turn VDM on or off whenever needed, and they paid only for what they used without any commitment or fixed monthly charges. Now, customers will see their charges per message for VDM decrease as their sending volume exceeds specific thresholds each month. After crossing each threshold in a given billing month, each subsequent message processed by VDM is charged at a lower rate. This reduces the total cost of using VDM for high volume senders. SES supports tiered pricing for VDM in all AWS regions where SES is available. For more information, see the documentation for the SES pricing page.  

Publicado el Deja un comentario

AWS CloudTrail network activity events for VPC endpoints are now generally available

With the launch of AWS CloudTrail network activity for VPC endpoints, you now have additional visibility into AWS API activity that traverses your VPC endpoints, enabling you to strengthen your data perimeter and implement better detective controls. You can enable network activity events for VPC endpoints for five AWS Services: Amazon S3, Amazon EC2, AWS Key Management Service (AWS KMS), AWS Secrets Manager, and AWS CloudTrail.

With network activity events for VPC endpoints, you can view details of who is accessing resources within your network giving you greater ability to identify and respond to malicious or unauthorized actions in your data perimeter. For example, as the VPC endpoint owner, you can view logs of actions that were denied due to VPC endpoint policies or determine if an actor outside of your data perimeter is trying to access the data in your S3 buckets.

You can enable logging for network activity events logging for your VPC endpoints using the AWS CloudTrail console, AWS CLI, and SDKs. When creating a new trail or event data store or editing an existing one, you can select network activity events for supported services that you wish to monitor; you can configure to log all API calls, or log only the accessDenied calls, and you can use advanced event selectors for additional filtering controls.

Network activity events for VPC endpoints are available in all commercial AWS Regions. Refer to CloudTrail pricing to learn more about network activity events pricing and the documentation to get started.

 

​With the launch of AWS CloudTrail network activity for VPC endpoints, you now have additional visibility into AWS API activity that traverses your VPC endpoints, enabling you to strengthen your data perimeter and implement better detective controls. You can enable network activity events for VPC endpoints for five AWS Services: Amazon S3, Amazon EC2, AWS Key Management Service (AWS KMS), AWS Secrets Manager, and AWS CloudTrail. With network activity events for VPC endpoints, you can view details of who is accessing resources within your network giving you greater ability to identify and respond to malicious or unauthorized actions in your data perimeter. For example, as the VPC endpoint owner, you can view logs of actions that were denied due to VPC endpoint policies or determine if an actor outside of your data perimeter is trying to access the data in your S3 buckets. You can enable logging for network activity events logging for your VPC endpoints using the AWS CloudTrail console, AWS CLI, and SDKs. When creating a new trail or event data store or editing an existing one, you can select network activity events for supported services that you wish to monitor; you can configure to log all API calls, or log only the accessDenied calls, and you can use advanced event selectors for additional filtering controls. Network activity events for VPC endpoints are available in all commercial AWS Regions. Refer to CloudTrail pricing to learn more about network activity events pricing and the documentation to get started.  

Publicado el Deja un comentario

Amazon Inspector enhances the security engine for container images scanning

Today, Amazon Inspector announced an upgrade to the engine powering its container image scanning for Amazon Elastic Container Registry (ECR). This upgrade will provide you with a more comprehensive view of the vulnerabilities in the third-party dependencies used in your container images. The enhancement to the engine will happen automatically without any action or disruption to your existing workflows. Existing customers can expect to see some findings closed as the new engine re-evaluates all the existing resources to better assess risks, while also surfacing new vulnerabilities as per the new engine’s dependency collection.

Amazon Inspector is a vulnerability management service that continually scans AWS workloads including Amazon EC2 instances, container images, and AWS Lambda functions for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization.

This improved version of container image scanning within ECR is available in all commercial and AWS GovCloud (US) Regions where Amazon Inspector is available.

 

​Today, Amazon Inspector announced an upgrade to the engine powering its container image scanning for Amazon Elastic Container Registry (ECR). This upgrade will provide you with a more comprehensive view of the vulnerabilities in the third-party dependencies used in your container images. The enhancement to the engine will happen automatically without any action or disruption to your existing workflows. Existing customers can expect to see some findings closed as the new engine re-evaluates all the existing resources to better assess risks, while also surfacing new vulnerabilities as per the new engine’s dependency collection. Amazon Inspector is a vulnerability management service that continually scans AWS workloads including Amazon EC2 instances, container images, and AWS Lambda functions for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization. This improved version of container image scanning within ECR is available in all commercial and AWS GovCloud (US) Regions where Amazon Inspector is available.

Getting started with Amazon Inspector
Amazon Inspector free trial  

Publicado el Deja un comentario

Amazon EC2 C7g instances are now available in the AWS Europe (Zurich) Region

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C7g instances are available in the AWS Europe (Zurich) Region. These instances are powered by AWS Graviton3 processors that provide up to 25% better compute performance compared to AWS Graviton2 processors, and built on top of the the AWS Nitro System, a collection of AWS designed innovations that deliver efficient, flexible, and secure cloud services with isolated multi-tenancy, private networking, and fast local storage.

Amazon EC2 Graviton3 instances also use up to 60% less energy to reduce your cloud carbon footprint for the same performance than comparable EC2 instances. For increased scalability, these instances are available in 9 different instance sizes, including bare metal, and offer up to 30 Gbps networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (EBS).

To learn more, see Amazon EC2 C7g. To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fast Start program and Porting Advisor for Graviton. To get started, see the AWS Management Console.

 

​Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C7g instances are available in the AWS Europe (Zurich) Region. These instances are powered by AWS Graviton3 processors that provide up to 25% better compute performance compared to AWS Graviton2 processors, and built on top of the the AWS Nitro System, a collection of AWS designed innovations that deliver efficient, flexible, and secure cloud services with isolated multi-tenancy, private networking, and fast local storage. Amazon EC2 Graviton3 instances also use up to 60% less energy to reduce your cloud carbon footprint for the same performance than comparable EC2 instances. For increased scalability, these instances are available in 9 different instance sizes, including bare metal, and offer up to 30 Gbps networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (EBS). To learn more, see Amazon EC2 C7g. To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fast Start program and Porting Advisor for Graviton. To get started, see the AWS Management Console.