Publicado el Deja un comentario

Introducing AWS CDK Refactor (Preview)

AWS Cloud Development Kit (CDK) CLI now enables safe infrastructure refactoring through the new ‘cdk refactor’ command in preview. This feature allows developers to rename constructs, move resources between stacks, and reorganize CDK applications while preserving the state of deployed resources. By leveraging AWS CloudFormation’s refactor capabilities with automated mapping computation, CDK Refactor eliminates the risk of unintended resource replacement during code restructuring.
Previously, infrastructure as code maintenance often requires reorganizing resources and improving code structure, but these changes traditionally risked replacing existing resources due to logical ID changes. With the CDK Refactor feature, developers can confidently implement architectural improvements like breaking down monolithic stacks, introducing inheritance patterns, or upgrading to higher-level constructs without complex migration procedures or risking downtime of stateful resources. This allows teams to continuously evolve their infrastructure code while maintaining the stability of their production environments.

The AWS CDK Refactor feature is available in all AWS Regions where the AWS CDK is supported.

For more information and a walkthrough of the feature, check out the blog post and the documentation. You can read more about the AWS CDK here.

 

​AWS Cloud Development Kit (CDK) CLI now enables safe infrastructure refactoring through the new ‘cdk refactor’ command in preview. This feature allows developers to rename constructs, move resources between stacks, and reorganize CDK applications while preserving the state of deployed resources. By leveraging AWS CloudFormation’s refactor capabilities with automated mapping computation, CDK Refactor eliminates the risk of unintended resource replacement during code restructuring. Previously, infrastructure as code maintenance often requires reorganizing resources and improving code structure, but these changes traditionally risked replacing existing resources due to logical ID changes. With the CDK Refactor feature, developers can confidently implement architectural improvements like breaking down monolithic stacks, introducing inheritance patterns, or upgrading to higher-level constructs without complex migration procedures or risking downtime of stateful resources. This allows teams to continuously evolve their infrastructure code while maintaining the stability of their production environments.
The AWS CDK Refactor feature is available in all AWS Regions where the AWS CDK is supported.
For more information and a walkthrough of the feature, check out the blog post and the documentation. You can read more about the AWS CDK here.  

Publicado el Deja un comentario

Amazon Bedrock AgentCore Gateway supports AWS PrivateLink invocation and invocation logging

Amazon Bedrock AgentCore Gateway now supports AWS PrivateLink invocation and invocation logging through Amazon CloudWatch, Amazon S3 and Amazon Data Firehose. Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to agent tools at scale. With the PrivateLink support and invocation logging, you can apply network and governance requirements to agents and tools through AgentCore Gateway.

The AWS PrivateLink support allows users and agents from a virtual private cloud (VPC) network to access AgentCore Gateway without going through the public internet. With invocation logging, you gain visibility into each invocation log and can deep dive into issues or audit activities.

Amazon Bedrock AgentCore is currently in preview and it is available in US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Frankfurt). Learn more about the features from the AWS documentation. Learn more about Amazon Bedrock AgentCore and it’s services in the News Blog.

 

​Amazon Bedrock AgentCore Gateway now supports AWS PrivateLink invocation and invocation logging through Amazon CloudWatch, Amazon S3 and Amazon Data Firehose. Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to agent tools at scale. With the PrivateLink support and invocation logging, you can apply network and governance requirements to agents and tools through AgentCore Gateway. The AWS PrivateLink support allows users and agents from a virtual private cloud (VPC) network to access AgentCore Gateway without going through the public internet. With invocation logging, you gain visibility into each invocation log and can deep dive into issues or audit activities. Amazon Bedrock AgentCore is currently in preview and it is available in US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Frankfurt). Learn more about the features from the AWS documentation. Learn more about Amazon Bedrock AgentCore and it’s services in the News Blog.  

Publicado el Deja un comentario

AWS Elastic Beanstalk now supports IPv6 in dual stack configuration for Application and Network Load Balancers

AWS Elastic Beanstalk now supports dual-stack configuration for both Application Load Balancers (ALB) and Network Load Balancers (NLB), allowing environments to serve both IPv4 and IPv6 protocols. You can now set the IpAddressType option to «dualstack,» and Elastic Beanstalk will automatically configure your load balancer with dual-stack support, creating both A and AAAA DNS records. You can seamlessly update existing IPv4 environments to dual-stack or revert back as needed.

This capability helps you reach users on IPv6-only networks while maintaining full IPv4 compatibility, supporting global accessibility requirements and IPv6 adoption mandates. The feature automatically handles DNS record management, simplifying IPv6 deployment for your applications and ensuring optimal performance for all users.

This feature is available in all AWS regions that support Elastic Beanstalk and Application and Network Load Balancers.

For detailed configuration steps, see the Elastic Beanstalk Developer Guide and Load Balancer documentation. Learn more about IPv6 networking in the Amazon VPC User Guide.

 

​AWS Elastic Beanstalk now supports dual-stack configuration for both Application Load Balancers (ALB) and Network Load Balancers (NLB), allowing environments to serve both IPv4 and IPv6 protocols. You can now set the IpAddressType option to «dualstack,» and Elastic Beanstalk will automatically configure your load balancer with dual-stack support, creating both A and AAAA DNS records. You can seamlessly update existing IPv4 environments to dual-stack or revert back as needed. This capability helps you reach users on IPv6-only networks while maintaining full IPv4 compatibility, supporting global accessibility requirements and IPv6 adoption mandates. The feature automatically handles DNS record management, simplifying IPv6 deployment for your applications and ensuring optimal performance for all users.
This feature is available in all AWS regions that support Elastic Beanstalk and Application and Network Load Balancers.
For detailed configuration steps, see the Elastic Beanstalk Developer Guide and Load Balancer documentation. Learn more about IPv6 networking in the Amazon VPC User Guide.  

Publicado el Deja un comentario

AWS Backup now supports selective backup of ACLs and ObjectTags in Amazon S3 backups

AWS Backup now lets you choose whether to include Access Control Lists (ACLs) and ObjectTags when backing up your Amazon S3 buckets.

Previously, AWS Backup included these metadata components for all objects by default. This new capability lets you customize your backup approach based on your recovery needs, so you can include only the metadata you need.

This capability is available in all AWS Regions where AWS Backup for Amazon S3 is available. For pricing and regional availability information, see the AWS Backup pricing page.

To learn more about AWS Backup for Amazon S3, visit the product page and technical documentation. To get started, visit the AWS Backup console

 

​AWS Backup now lets you choose whether to include Access Control Lists (ACLs) and ObjectTags when backing up your Amazon S3 buckets. Previously, AWS Backup included these metadata components for all objects by default. This new capability lets you customize your backup approach based on your recovery needs, so you can include only the metadata you need. This capability is available in all AWS Regions where AWS Backup for Amazon S3 is available. For pricing and regional availability information, see the AWS Backup pricing page. To learn more about AWS Backup for Amazon S3, visit the product page and technical documentation. To get started, visit the AWS Backup console.   

Publicado el Deja un comentario

Amazon EC2 I8g instances now available in AWS US East (Ohio) region

AWS is announcing the general availability of Amazon EC2 Storage Optimized I8g instances in US East (Ohio) region. I8g instances offer the best performance in Amazon EC2 for storage-intensive workloads. I8g instances are powered by AWS Graviton4 processors that deliver up to 60% better compute performance compared to previous generation I4g instances. I8g instances use the latest third generation AWS Nitro SSDs, local NVMe storage that deliver up to 65% better real-time storage performance per TB while offering up to 50% lower storage I/O latency and up to 60% lower storage I/O latency variability. These instances are built on the AWS Nitro System, which offloads CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads.

Amazon EC2 I8g instances are designed for I/O intensive workloads that require rapid data access and real-time latency from storage. These instances excel at handling transactional, real-time, distributed databases, including MySQL, PostgreSQL, Hbase and NoSQL solutions like Aerospike, MongoDB, ClickHouse, and Apache Druid. They’re also optimized for real-time analytics platforms such as Apache Spark, data lakehouse and AI LLM pre-processing for training. I8g instances are available in 10 different sizes with up to 48xlarge including one metal size, 1.5 TiB of memory, and 45 TB local instance storage. They deliver up to 100 Gbps of network performance bandwidth, and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS).

To learn more, visit the EC2 I8g page.

 

​AWS is announcing the general availability of Amazon EC2 Storage Optimized I8g instances in US East (Ohio) region. I8g instances offer the best performance in Amazon EC2 for storage-intensive workloads. I8g instances are powered by AWS Graviton4 processors that deliver up to 60% better compute performance compared to previous generation I4g instances. I8g instances use the latest third generation AWS Nitro SSDs, local NVMe storage that deliver up to 65% better real-time storage performance per TB while offering up to 50% lower storage I/O latency and up to 60% lower storage I/O latency variability. These instances are built on the AWS Nitro System, which offloads CPU virtualization, storage, and networking functions to dedicated hardware and software enhancing the performance and security for your workloads. Amazon EC2 I8g instances are designed for I/O intensive workloads that require rapid data access and real-time latency from storage. These instances excel at handling transactional, real-time, distributed databases, including MySQL, PostgreSQL, Hbase and NoSQL solutions like Aerospike, MongoDB, ClickHouse, and Apache Druid. They’re also optimized for real-time analytics platforms such as Apache Spark, data lakehouse and AI LLM pre-processing for training. I8g instances are available in 10 different sizes with up to 48xlarge including one metal size, 1.5 TiB of memory, and 45 TB local instance storage. They deliver up to 100 Gbps of network performance bandwidth, and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS). To learn more, visit the EC2 I8g page.  

Publicado el Deja un comentario

Amazon CloudWatch Network Monitoring adds flow visibility between Regions

With flow monitors in Amazon CloudWatch Network Monitoring, you can now monitor network performance of traffic flowing between AWS Regions across the AWS global network. Flow monitors provide near real-time visibility of network performance for workloads between compute instances such as Amazon EC2 and Amazon EKS, and AWS services such as Amazon S3 and Amazon DynamoDB. Flow monitors provide metrics to help you rapidly detect and attribute network-driven impairments for your workloads.

With this release, flow monitors now help you to assess whether network performance issues on the AWS global network between a local and a remote Region are impacting your workloads. Because the flow monitor’s network health indicator (NHI) now also captures the health of the AWS global network on your workload’s network paths between Regions, you can quickly identify whether impairments in a local Region, in the AWS global network, or in the remote Region are affecting your workloads. This feature extends network visibility for flows to a remote Region’s public IP address, and for private traffic flowing to a remote Region over Amazon VPC peering or AWS Transit Gateway peering.

For the full list of the AWS Regions where Network Monitoring for AWS workloads is available, visit the Regions list. To learn more, visit the Amazon CloudWatch Network Monitoring documentation.

 

​With flow monitors in Amazon CloudWatch Network Monitoring, you can now monitor network performance of traffic flowing between AWS Regions across the AWS global network. Flow monitors provide near real-time visibility of network performance for workloads between compute instances such as Amazon EC2 and Amazon EKS, and AWS services such as Amazon S3 and Amazon DynamoDB. Flow monitors provide metrics to help you rapidly detect and attribute network-driven impairments for your workloads. With this release, flow monitors now help you to assess whether network performance issues on the AWS global network between a local and a remote Region are impacting your workloads. Because the flow monitor’s network health indicator (NHI) now also captures the health of the AWS global network on your workload’s network paths between Regions, you can quickly identify whether impairments in a local Region, in the AWS global network, or in the remote Region are affecting your workloads. This feature extends network visibility for flows to a remote Region’s public IP address, and for private traffic flowing to a remote Region over Amazon VPC peering or AWS Transit Gateway peering. For the full list of the AWS Regions where Network Monitoring for AWS workloads is available, visit the Regions list. To learn more, visit the Amazon CloudWatch Network Monitoring documentation.  

Publicado el Deja un comentario

AWS HealthImaging now supports OpenID Connect (OIDC) authentication for DICOMweb APIs

AWS HealthImaging now supports OAuth 2.0-compatible identity providers for authentication of DICOMweb requests using OpenID Connect (OIDC). With OIDC authentication, you can manage secure access to DICOM resources using your organization’s standard procedures for creating, enabling, and disabling user accounts.

With this launch, you can now use existing identity providers (IdPs)—such as Amazon Cognito, Okta, or Auth0—to issue JSON Web Tokens (JWTs) that authorize secure access to your DICOMweb endpoints. This launch makes it simpler to integrate AWS HealthImaging into existing medical imaging applications and expands HealthImaging’s support of DICOMweb standard interfaces that rely on OAuth 2.0-compatible authentication. Support for OIDC is limited to DICOMweb REST API requests. HealthImaging includes native support for AWS Identity and Access Management (IAM) users and roles for authentication of all API requests.

Support for OpenID Connect (OIDC) is available in all AWS Regions where AWS HealthImaging is generally available: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland).

To learn more, visit Using DICOMweb with AWS HealthImaging.

 

​AWS HealthImaging now supports OAuth 2.0-compatible identity providers for authentication of DICOMweb requests using OpenID Connect (OIDC). With OIDC authentication, you can manage secure access to DICOM resources using your organization’s standard procedures for creating, enabling, and disabling user accounts. With this launch, you can now use existing identity providers (IdPs)—such as Amazon Cognito, Okta, or Auth0—to issue JSON Web Tokens (JWTs) that authorize secure access to your DICOMweb endpoints. This launch makes it simpler to integrate AWS HealthImaging into existing medical imaging applications and expands HealthImaging’s support of DICOMweb standard interfaces that rely on OAuth 2.0-compatible authentication. Support for OIDC is limited to DICOMweb REST API requests. HealthImaging includes native support for AWS Identity and Access Management (IAM) users and roles for authentication of all API requests. Support for OpenID Connect (OIDC) is available in all AWS Regions where AWS HealthImaging is generally available: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland). To learn more, visit Using DICOMweb with AWS HealthImaging.  

Publicado el Deja un comentario

AWS IoT SiteWise now supports retraining of anomaly detection models

Today, AWS announced new capabilities for native anomaly detection in AWS IoT SiteWise. This release includes automated model retraining, flexible promotion modes, and exposed model metrics, all designed to enhance the anomaly detection feature.

The automated retraining capability allows models to be automatically retrained on a schedule ranging from a minimum of 30 days to a maximum of one year, eliminating the need to manually retrain models. This feature ensures that models stay up-to-date with changing equipment conditions or configurations, thereby maintaining optimal performance over time.

Additionally, flexible promotion modes give customers the choice between service-managed and customer-managed model promotion. Automatic promotion enables AWS IoT SiteWise to evaluate and promote the best-performing model without customer intervention, while manual promotion allows customers to review comprehensive, exposed model metrics—including precision, recall, and Area Under the ROC Curve (AUC)—before deciding which model version to activate. This flexibility allows choice between a hands-off or human oversight approach. 

Multivariate anomaly detection is available in US East (N. Virginia) , Europe (Ireland) , and Asia Pacific (Sydney) AWS Regions where AWS IoT SiteWise is offered. To learn more, read the launch blog and user guide

 

​Today, AWS announced new capabilities for native anomaly detection in AWS IoT SiteWise. This release includes automated model retraining, flexible promotion modes, and exposed model metrics, all designed to enhance the anomaly detection feature. The automated retraining capability allows models to be automatically retrained on a schedule ranging from a minimum of 30 days to a maximum of one year, eliminating the need to manually retrain models. This feature ensures that models stay up-to-date with changing equipment conditions or configurations, thereby maintaining optimal performance over time. Additionally, flexible promotion modes give customers the choice between service-managed and customer-managed model promotion. Automatic promotion enables AWS IoT SiteWise to evaluate and promote the best-performing model without customer intervention, while manual promotion allows customers to review comprehensive, exposed model metrics—including precision, recall, and Area Under the ROC Curve (AUC)—before deciding which model version to activate. This flexibility allows choice between a hands-off or human oversight approach.  Multivariate anomaly detection is available in US East (N. Virginia) , Europe (Ireland) , and Asia Pacific (Sydney) AWS Regions where AWS IoT SiteWise is offered. To learn more, read the launch blog and user guide.   

Publicado el Deja un comentario

Amazon IVS now supports private ingest via interface VPC endpoints

Amazon Interactive Video Service (Amazon IVS) now supports media ingest via interface VPC endpoints powered by AWS PrivateLink. With this launch, you can securely broadcast RTMP(S) streams to IVS Low-Latency channels or IVS Real-Time stages without sending traffic over the public internet. You can create interface VPC endpoints to privately connect your applications to Amazon IVS from within your VPC or from on-premises environments over AWS Direct Connect. This provides private, reliable connectivity for your live video workflows.

Amazon IVS support for media ingest via interface VPC endpoints is available today in the US West (Oregon), Europe (Frankfurt), and Europe (Ireland) AWS Regions. Standard AWS PrivateLink pricing applies. See the AWS PrivateLink pricing page for details.

To learn more, please visit the Amazon IVS private ingest documentation page.

 

​Amazon Interactive Video Service (Amazon IVS) now supports media ingest via interface VPC endpoints powered by AWS PrivateLink. With this launch, you can securely broadcast RTMP(S) streams to IVS Low-Latency channels or IVS Real-Time stages without sending traffic over the public internet. You can create interface VPC endpoints to privately connect your applications to Amazon IVS from within your VPC or from on-premises environments over AWS Direct Connect. This provides private, reliable connectivity for your live video workflows.
Amazon IVS support for media ingest via interface VPC endpoints is available today in the US West (Oregon), Europe (Frankfurt), and Europe (Ireland) AWS Regions. Standard AWS PrivateLink pricing applies. See the AWS PrivateLink pricing page for details.
To learn more, please visit the Amazon IVS private ingest documentation page.  

Publicado el Deja un comentario

BrainKey y Microsoft Azure: Avanzar en la investigación de la salud cerebral con IA responsable

septiembre 10, 2025

BrainKey y Microsoft Azure: Avanzar en la investigación de la salud cerebral con IA responsable

Doctora habla con un paciente mientras le muestra una tablet

Por: Microsoft para Startups.

A veces, las condiciones médicas y los diagnósticos más desafiantes requieren un cambio de perspectiva. Las nuevas empresas innovadoras que utilizan IA y Microsoft Azure han encontrado nuevas formas de introducir esas perspectivas en la práctica de la medicina, todos los días.

Mientras Owen Phillips, director ejecutivo de BrainKey, neurocientífico capacitado en Stanford, observaba cómo la salud cognitiva de su madre se deterioraba con rapidez, se encontró en un lugar donde ninguna cantidad de experiencia académica podría haberlo preparado para experimentar, y ninguna solución existente parecía capaz de diagnosticar su condición.

A pesar de sus profundas conexiones en el campo de la medicina, su condición permaneció sin diagnosticar, hasta que la tecnología que construía en su startup, BrainKey, al final ayudó a descubrir el verdadero problema: una afección tratable llamada hidrocefalia normotensiva.

Ese momento se convirtió en el catalizador de la misión de BrainKey: capacitar a los pacientes y médicos con información más temprana y precisa sobre la salud del cerebro por medio de IA e imágenes médicas.

Detrás de todo lo que hacemos en BrainKey está este impulso para ayudar a las personas a evitar el tipo de incertidumbre y dolor por el que pasó mi familia. Queremos que la salud del cerebro sea más accesible, comprensible y procesable.

—Owen Phillips, director ejecutivo de BrainKey

Construir una IA responsable que detecte patrones que otros pasan por alto

La «clave» de BrainKey es el uso de IA avanzada para analizar resonancias magnéticas y detectar cambios sutiles en el cerebro, a menudo antes de que aparezcan los síntomas. ¿Cómo? Por medio de modelos que se entrenan en un vasto conjunto de datos normativos recopilados de clínicas de todo el mundo. Estos conjuntos de datos masivos permiten que la tecnología BrainKey estime la «edad cerebral» e identifique signos tempranos de deterioro neurológico.

Pero BrainKey no se detiene en el análisis. Han construido una interfaz de visualización tridimensional que también permite a los pacientes explorar sus propios escáneres cerebrales en un formato intuitivo y fácil de usar. Este enfoque en la experiencia del usuario, junto con el rigor científico, es lo que distingue a BrainKey.

No solo construimos herramientas para médicos. Creamos herramientas que ayudan a las familias a comprender lo que les sucede a sus seres queridos.

—Nathan Strong, director de tecnología de BrainKey

Escalado con Azure: una plataforma creada para la precisión, el rendimiento y la privacidad

Para respaldar su creciente base de usuarios y cargas de trabajo intensivas en datos, BrainKey recurrió a Microsoft Azure. Su infraestructura usa Azure Kubernetes Service (AKS) para el proceso escalable, Azure Blob Storage para el control seguro de datos y Terraform para la administración flexible de la infraestructura.

Lidiamos con cargas de trabajo en ráfagas: algunas horas son tranquilas; otras están llenos de análisis. El escalado automático de Azure y la compatibilidad con nodos heterogéneos han sido fundamentales para administrarlo de manera eficiente.

—Nathan Strong, director de tecnología de BrainKey

La seguridad y el cumplimiento también son las principales prioridades. La arquitectura de BrainKey es compatible por completo con HIPAA, con datos cifrados en reposo y en tránsito. Para optimizar aún más la solución, BrainKey se ha integrado con Nuance PowerShare, una plataforma propiedad de Microsoft, para facilitar el intercambio de datos con los proveedores de atención médica.

Uso del ecosistema de Microsoft para respaldar la innovación en la atención médica

El recorrido de BrainKey con Microsoft comenzó a través del programa Microsoft for Startups en 2019, donde recibieron créditos, soporte técnico y acceso a una red global.

Desde entonces, la asociación se ha profundizado, con el equipo de Iniciativas Digitales y Estratégicas (DSI, por sus siglas en inglés) de Microsoft que desempeña un papel fundamental en la optimización de la arquitectura de BrainKey y la exploración de oportunidades de comercialización.

El soporte de Microsoft ha sido fenomenal. Desde revisiones técnicas hasta introducciones estratégicas, nos han ayudado a avanzar más rápido y de manera más inteligente.

— Owen Phillips, neurocientífico formado en Stanford

BrainKey ahora ha comenzado a explorar cómo integrarse con Microsoft Azure Marketplace, lo que permite a los proveedores de atención médica adquirir su solución a través de los canales existentes de Microsoft. Esto abre la puerta a una adopción más amplia y una colaboración más profunda con los equipos de cuentas de atención médica de Microsoft.

De las clínicas a Microsoft Azure: Apoyar la salud del cerebro en la nube

Con un acuerdo reciente firmado con uno de los proveedores de imágenes por resonancia magnética (MRI, por sus siglas en inglés) más grandes de los Estados Unidos, BrainKey se ha comenzado a preparar para escalar con rapidez. ¿Su objetivo? Llevar su plataforma de salud cerebral impulsada por IA a clínicas de todo el país y, de manera eventual, del mundo.

Construimos la infraestructura ahora para respaldar un crecimiento masivo. Azure nos brinda la escalabilidad que necesitamos para que esto esté disponible para todos, no solo para unos pocos. Más adelante, incluiremos Brainkey en Azure Marketplace. Este es un hito importante para nosotros, ya que hará que nuestra tecnología sea más accesible para los proveedores de atención médica de todo el mundo y permitirá una integración perfecta en los flujos de trabajo clínicos existentes.

— Owen Phillips, neurocientífico formado en Stanford

A medida que BrainKey continúa su crecimiento, su misión se mantiene clara: ayudar a millones de personas a comprender mejor sus cerebros, recibir diagnósticos más tempranos y vivir vidas más saludables. Y Microsoft ayuda a garantizar que la tecnología desempeñe un papel transformador para llevarlos allí.

Empiecen a usar Microsoft for Startups hoy mismo

The post BrainKey y Microsoft Azure: Avanzar en la investigación de la salud cerebral con IA responsable appeared first on Source LATAM.

 

​The post BrainKey y Microsoft Azure: Avanzar en la investigación de la salud cerebral con IA responsable appeared first on Source LATAM.