AWS Direct Connect now supports 4-byte Autonomous System (AS) numbers for virtual interfaces. Direct Connect uses the standard Border Gateway Protocol to provide customers with private connectivity to the AWS global network. However, customers with complex, multi-tenant network topologies or who need to maintain consistent AS numbering across their entire network can run into challenges with the maximum limit of 65,536 possible 2-byte AS numbers. With 4-byte AS numbers, customers can now use the entire range supported by RFC 6793, up to 4,294,967,294.
Support for 4-byte AS numbers is now available in all AWS regions globally and on all Direct Connect virtual interface types. To get started, visit the AWS Direct Connect Console or use the updated APIs to create virtual interfaces with the new 4-byte AS numbers. For more information, check out the AWS Direct Connect documentation.

​AWS Direct Connect now supports 4-byte Autonomous System (AS) numbers for virtual interfaces. Direct Connect uses the standard Border Gateway Protocol to provide customers with private connectivity to the AWS global network. However, customers with complex, multi-tenant network topologies or who need to maintain consistent AS numbering across their entire network can run into challenges with the maximum limit of 65,536 possible 2-byte AS numbers. With 4-byte AS numbers, customers can now use the entire range supported by RFC 6793, up to 4,294,967,294. Support for 4-byte AS numbers is now available in all AWS regions globally and on all Direct Connect virtual interface types. To get started, visit the AWS Direct Connect Console or use the updated APIs to create virtual interfaces with the new 4-byte AS numbers. For more information, check out the AWS Direct Connect documentation.  

Today, AWS announces remote connection from Visual Studio Code (VS Code) to Amazon SageMaker Unified Studio. This new capability allows developers to leverage their VS Code setup while accessing the scalable compute resources of Amazon SageMaker. By connecting VS Code to SageMaker Unified Studio, you can maintain your existing development workflows and configurations within a unified environment for AWS analytics and AI/ML services.

SageMaker Unified Studio, part of the next generation of Amazon SageMaker, offers a broad set of fully managed cloud interactive development environments (IDE), including JupyterLab and Code Editor based on Code-OSS (Open Source Software) like VS Code. Starting today, you can use your customized local VS Code setup while accessing your compute resources and data in Amazon SageMaker. Authentication is simple and secure using the AWS Toolkit extension in VS Code. This integration provides a streamlined path from your local development environment to scalable infrastructure for running data processing, SQL analytics, and ML workflows.

This feature is available in all Regions where Amazon SageMaker Unified Studio is available. To learn more, refer to the Administrator Guide and User Guide. 

​Today, AWS announces remote connection from Visual Studio Code (VS Code) to Amazon SageMaker Unified Studio. This new capability allows developers to leverage their VS Code setup while accessing the scalable compute resources of Amazon SageMaker. By connecting VS Code to SageMaker Unified Studio, you can maintain your existing development workflows and configurations within a unified environment for AWS analytics and AI/ML services. SageMaker Unified Studio, part of the next generation of Amazon SageMaker, offers a broad set of fully managed cloud interactive development environments (IDE), including JupyterLab and Code Editor based on Code-OSS (Open Source Software) like VS Code. Starting today, you can use your customized local VS Code setup while accessing your compute resources and data in Amazon SageMaker. Authentication is simple and secure using the AWS Toolkit extension in VS Code. This integration provides a streamlined path from your local development environment to scalable infrastructure for running data processing, SQL analytics, and ML workflows. This feature is available in all Regions where Amazon SageMaker Unified Studio is available. To learn more, refer to the Administrator Guide and User Guide.   

Amazon Athena announces single sign-on support for its JDBC and ODBC drivers through AWS IAM Identity Center’s trusted identity propagation. This makes it simpler for organizations to manage end-user’s access to data when using 3rd party tools and implement identity-based data governance policies with a seamless sign-on experience.

With this new capability, data teams can seamlessly access data through their preferred 3rd party tools using their organizational credentials. When analysts run queries using the updated Athena JDBC (3.6.0) and ODBC (2.0.5.0) drivers, their access permissions defined in Lake Formation are applied and their actions logged. This streamlined workflow eliminates credential management overhead while ensuring consistent security policies, allowing data teams to focus on insights rather than access management. For example, data analysts using 3rd party BI tools or SQL clients can now connect to Athena using their corporate credentials, and their access to data will be restricted based on policies defined for their respective user identity or group membership in Lake Formation.

This feature is available in regions where Amazon Athena and AWS Identity Center’s trusted identity propagation are supported. To learn more about configuring identity support when using Athena drivers, see the Amazon Athena driver documentation.

​Amazon Athena announces single sign-on support for its JDBC and ODBC drivers through AWS IAM Identity Center’s trusted identity propagation. This makes it simpler for organizations to manage end-user’s access to data when using 3rd party tools and implement identity-based data governance policies with a seamless sign-on experience.
With this new capability, data teams can seamlessly access data through their preferred 3rd party tools using their organizational credentials. When analysts run queries using the updated Athena JDBC (3.6.0) and ODBC (2.0.5.0) drivers, their access permissions defined in Lake Formation are applied and their actions logged. This streamlined workflow eliminates credential management overhead while ensuring consistent security policies, allowing data teams to focus on insights rather than access management. For example, data analysts using 3rd party BI tools or SQL clients can now connect to Athena using their corporate credentials, and their access to data will be restricted based on policies defined for their respective user identity or group membership in Lake Formation.
This feature is available in regions where Amazon Athena and AWS Identity Center’s trusted identity propagation are supported. To learn more about configuring identity support when using Athena drivers, see the Amazon Athena driver documentation.  

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for vending logs to Amazon CloudWatch Logs.

With Amazon Managed Service for Prometheus collector logs you can now troubleshoot issues in your setup, from context on the Prometheus target discovery process including authentication issues to scraping process to status and errors such as timeouts to information on ingesting collected metrics to your Amazon Managed Service for Prometheus workspace, for example, remote-write failures due to workspace issues.

Amazon Managed Service for Prometheus collector logs are now generally available in all regions where Amazon Managed Service for Prometheus is available.

Please visit the Amazon CloudWatch pricing page to learn more about logs pricing. Get started with Managed Service for Prometheus collector logs by visiting our user guide.

​Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for vending logs to Amazon CloudWatch Logs.
With Amazon Managed Service for Prometheus collector logs you can now troubleshoot issues in your setup, from context on the Prometheus target discovery process including authentication issues to scraping process to status and errors such as timeouts to information on ingesting collected metrics to your Amazon Managed Service for Prometheus workspace, for example, remote-write failures due to workspace issues.
Amazon Managed Service for Prometheus collector logs are now generally available in all regions where Amazon Managed Service for Prometheus is available.
Please visit the Amazon CloudWatch pricing page to learn more about logs pricing. Get started with Managed Service for Prometheus collector logs by visiting our user guide.  

Amazon Elastic Container Service (Amazon ECS), a fully managed container orchestration service, now makes it easier to create and update task definitions in the AWS Management Console with generative AI assistance from Amazon Q Developer.

This new capability helps customers complete their task definitions faster and more efficiently using AI-generated code suggestions. Customers can use the inline chat capability to ask Amazon Q Developer to generate, explain, or refactor task definition JSON with a conversational interface. You can inject generated suggestions at any point in the task definition and accept or reject the changes proposed. Amazon ECS has also enhanced the existing inline suggestions feature to utilize Amazon Q Developer. Now in addition to the existing property-based inline suggestions, the Amazon Q Developer suggestions can autocomplete whole blocks of sample code.

These updates are available in regions where Amazon Q Developer is available, and can be enabled or disabled through settings in the console code editor or IAM permissions. See the AWS Developer Guide for further details.

​Amazon Elastic Container Service (Amazon ECS), a fully managed container orchestration service, now makes it easier to create and update task definitions in the AWS Management Console with generative AI assistance from Amazon Q Developer. This new capability helps customers complete their task definitions faster and more efficiently using AI-generated code suggestions. Customers can use the inline chat capability to ask Amazon Q Developer to generate, explain, or refactor task definition JSON with a conversational interface. You can inject generated suggestions at any point in the task definition and accept or reject the changes proposed. Amazon ECS has also enhanced the existing inline suggestions feature to utilize Amazon Q Developer. Now in addition to the existing property-based inline suggestions, the Amazon Q Developer suggestions can autocomplete whole blocks of sample code. These updates are available in regions where Amazon Q Developer is available, and can be enabled or disabled through settings in the console code editor or IAM permissions. See the AWS Developer Guide for further details.  

AWS launches LocalStack integration in Visual Studio Code (VS Code), enabling developers to easily test and debug serverless applications in their local IDE. With this new integration, developers can use LocalStack to locally emulate and test their serverless applications using familiar VS Code interface without switching between tools or managing complex setup, thus simplifying their local serverless development process.

LocalStack, an AWS Partner Network (APN) partner, enables developers to emulate AWS services such as AWS Lambda, Amazon SQS, Amazon API Gateway, and DynamoDB for local application development and testing. Previously, to use LocalStack to emulate AWS services in VS Code, developers had to manually configure ports, make code changes, and switch context between the IDE and LocalStack interface. Now, with LocalStack integration in VS Code, developers can connect to LocalStack environment from their IDE without manual configuration or code changes. This gives developers access to emulated AWS resources in the IDE, making it easy to build and test serverless applications locally. For example, they can now easily test and debug Lambda functions and their interactions with AWS services in a LocalStack emulated environment from their IDE.

This integration is now available to developers using the AWS Toolkit for VS Code (v3.74.0 or later). There is no additional cost from AWS for using this integration. To get started, follow the guided AWS Walkthrough in VS Code, which automatically installs the LocalStack CLI, guides through LocalStack account setup, and creates a LocalStack profile. Then, switch to LocalStack profile and deploy applications directly to the LocalStack environment. To learn more, visit the AWS News Blog, AWS Toolkit documentation, and the Lambda Developer Guide.

​AWS launches LocalStack integration in Visual Studio Code (VS Code), enabling developers to easily test and debug serverless applications in their local IDE. With this new integration, developers can use LocalStack to locally emulate and test their serverless applications using familiar VS Code interface without switching between tools or managing complex setup, thus simplifying their local serverless development process. LocalStack, an AWS Partner Network (APN) partner, enables developers to emulate AWS services such as AWS Lambda, Amazon SQS, Amazon API Gateway, and DynamoDB for local application development and testing. Previously, to use LocalStack to emulate AWS services in VS Code, developers had to manually configure ports, make code changes, and switch context between the IDE and LocalStack interface. Now, with LocalStack integration in VS Code, developers can connect to LocalStack environment from their IDE without manual configuration or code changes. This gives developers access to emulated AWS resources in the IDE, making it easy to build and test serverless applications locally. For example, they can now easily test and debug Lambda functions and their interactions with AWS services in a LocalStack emulated environment from their IDE. This integration is now available to developers using the AWS Toolkit for VS Code (v3.74.0 or later). There is no additional cost from AWS for using this integration. To get started, follow the guided AWS Walkthrough in VS Code, which automatically installs the LocalStack CLI, guides through LocalStack account setup, and creates a LocalStack profile. Then, switch to LocalStack profile and deploy applications directly to the LocalStack environment. To learn more, visit the AWS News Blog, AWS Toolkit documentation, and the Lambda Developer Guide.  

Amazon EventBridge is expanding the availability of its API destinations feature to the AWS Asia Pacific (Melbourne) and AWS Asia Pacific (Thailand) Regions.

EventBridge API destinations are HTTPS endpoints that you can invoke as the target of an event bus rule, similar to how you invoke an AWS service or resource as a target. API destinations provides flexible authentication options for HTTPS endpoints, such as API key and OAuth, storing and managing credentials securely in AWS Secrets Manager on your behalf.

To get started, visit the Amazon EventBridge documentation to learn more about configuring API destinations.

​Amazon EventBridge is expanding the availability of its API destinations feature to the AWS Asia Pacific (Melbourne) and AWS Asia Pacific (Thailand) Regions. EventBridge API destinations are HTTPS endpoints that you can invoke as the target of an event bus rule, similar to how you invoke an AWS service or resource as a target. API destinations provides flexible authentication options for HTTPS endpoints, such as API key and OAuth, storing and managing credentials securely in AWS Secrets Manager on your behalf. To get started, visit the Amazon EventBridge documentation to learn more about configuring API destinations.  

• Categoría: Noticias de Microsoft

septiembre 11, 2025

Convertirse en frontera: cómo los socios impulsan la próxima ola de innovación en IA

Por: Nina Harding.

Ha comenzado a surgir una nueva clase de organización: las Empresas Frontera. Estos líderes de la industria utilizan la IA para enriquecer las experiencias de los empleados, reinventar el compromiso del cliente, remodelar los procesos comerciales e imaginar el próximo gran salto en innovación. Se mueven más rápido, se adaptan más rápido y logran más, todo mientras establecen el estándar de lo que es posible en la era de la IA.

En Microsoft, sabemos que las Empresas Frontera combinan tecnología de clase mundial y ambición humana. Eso significa combinar el poder de las tecnologías de IA de Microsoft como Microsoft Copilot y Azure AI Foundry con la creatividad, la curiosidad y la colaboración de las personas. Es esta combinación la que transforma las ideas en impacto, para impulsar el crecimiento y la escala.

Adoptar una mentalidad de Cliente Cero para predicar con el ejemplo

En Microsoft, creemos en ser los primeros y mejores clientes de productos propios, o «Cliente Cero». Ese principio básico ha guiado nuestro enfoque de Copilot, con resultados profundos. En pocas palabras, una de las mejores maneras de demostrar el poder de la IA es experimentarla.

Mi equipo y yo hemos adoptado a plenitud la mentalidad de Cliente Cero, al utilizar y experimentar con la misma tecnología que recomendamos a nuestros clientes. La IA se ha convertido en una parte diaria de nuestro flujo de trabajo, y los miembros del equipo la utilizan para tareas importantes como crear agentes en Copilot Studio, aprovechar M365 Copilot en nuestros flujos de trabajo y compartir las mejores prácticas de manera abierta.

Ser Cliente Cero ofrece una gran cantidad de beneficios para nuestros clientes, que incluyen:

• ROI comprobado a través de la experiencia vivida: Al utilizar nuestra propia tecnología, podemos realizar un seguimiento de los resultados tangibles, desde el ahorro de costos y el aumento de la productividad hasta un mayor compromiso de los empleados y compartir esos conocimientos directo con los clientes. Nuestros propios datos se convierten en los puntos de prueba, convirtiéndonos en estudios de casos vivos.
• Capacitación y desarrollo de experiencia: Nuestro uso de primera mano de nuestras propias herramientas significa que profundizamos nuestras propias habilidades de IA y podemos guiar a los clientes con un conocimiento amplio y práctico en varios casos de uso.
• Impulsar la innovación: Al experimentar a nivel interno, descubrimos nuevas ideas y sacamos a la luz los posibles desafíos de forma temprana, para ayudar a los clientes a moverse más rápido con confianza.

Socios + Microsoft: Acelerar la frontera

Ahora es el momento del liderazgo de la IA. El Índice de Tendencias Laborales 2025 de Microsoft confirma lo que muchos de nosotros ya sentimos: 2025 es el año en que la IA despierta nuestro potencial.

• El 82% de los líderes dice que ahora es el momento de repensar la estrategia y las operaciones.
• El 81% espera que  los agentes de IA se integren en sus estrategias en los próximos 12 a 18 meses.

Las Empresas Frontera avanzan. Entre sus trabajadores del conocimiento:

• El 71% dice que su empresa prospera.
• El 55% informa que hace un trabajo más significativo.
• El 93% se siente optimista sobre el futuro.

Entonces, ¿cómo alimentamos la chispa?

La capacidad de IA escalable fusionada con el ingenio humano ya no es opcional. Es la nueva línea de base para la ventaja competitiva.

Socios que impulsan resultados de frontera

Una de las mejores ventajas de mi trabajo es ver la increíble innovación que ocurre en las Américas y cómo nuestros socios ayudan a las organizaciones de toda la región y el mundo a convertir el potencial de la IA en resultados medibles con las tecnologías de Microsoft.

Aquí hay solo un puñado de ejemplos:

Accenture (a través de la implementación de Azure AI Foundry):

• Logró una reducción del 50% en el tiempo para crear aplicaciones de IA.
• Proporcionó un aumento de eficiencia del 30% y una reducción de costos del 20%.
• Implementó más de 75 casos de uso de IA generativa, con 16 en plena producción.

EY (con Microsoft Copilot en Power Platform):

• Aumento de los pagos automáticos compensados en un 50%.
• Ahorro de 230 mil horas anuales gracias a procesos más eficientes.
• Reducción del tiempo de entrenamiento de dos semanas a solo dos días.

LTIMindtree (con Microsoft Security Copilot):

• Reducción del tiempo medio de detección y respuesta en un 20%.
• Mejora de la eficiencia y la productividad del equipo.
• Fortaleció la experiencia, el enfoque y la precisión del equipo.

Estas historias no son solo estadísticas impresionantes. Son la prueba de que las Empresas Frontera no son una visión lejana. Están aquí hoy.

El papel de los socios en la construcción de Empresas Frontera

Como socios de Microsoft, ustedes son la chispa esencial que ayuda a los clientes a evaluar su preparación para la IA, explorar casos de uso de alto impacto y establecer centros de excelencia. Es a través de su liderazgo que las organizaciones pasan de ser las primeras en adoptarlas a verdaderas Empresas Frontera, que brindan un impacto y un crecimiento innovadores para todos nosotros.

Ahora es el momento de pasar de las ideas al impacto. Así es como pueden liderar el camino:

• Sean su mejor caso de estudio: actúen como Cliente Cero al utilizar las soluciones que recomiendan, creen sus propios agentes e integren IA en sus operaciones. Su recorrido, respaldado por métricas, se convierte en una historia poderosa que pueden compartir.
• Suban de nivel a través del Programa de socios de Microsoft AI Cloud (MAICP, por sus siglas en inglés): al invertir en sus habilidades, obtener designaciones, profundizar especializaciones y maximizar beneficios e incentivos, no solo aceleran su propia transformación, sino que también modelan cómo se ven las Empresas Frontera en la práctica.

Estamos en un punto de inflexión. Las Empresas Frontera ya han comenzado a demostrar lo que es posible. Juntos, podemos ayudar a preparar a nuestros clientes para liderar sus industrias hacia el futuro.

Etiquetas:

• IA
• Transformación Digital

The post Convertirse en frontera: cómo los socios impulsan la próxima ola de innovación en IA appeared first on Source LATAM.

​The post Convertirse en frontera: cómo los socios impulsan la próxima ola de innovación en IA appeared first on Source LATAM.  

AWS announces VPC endpoints for Amazon CloudWatch Observability Access Manager (OAM). CloudWatch OAM enables you to programmatically manage cross-account observability settings within a region. The new VPC endpoints enhance your security posture by keeping traffic between your VPC and CloudWatch OAM within the AWS network, eliminating the need to traverse the public internet.

You can use Observability Access Manager to create and manage links between source accounts and monitoring accounts, enabling you to monitor and troubleshoot applications that span multiple accounts within a Region. With the new VPC endpoints, you can establish secure, private, and reliable connections between your VPC and CloudWatch Observability Access Manager. This allows you to maintain private connectivity while managing cross-account observability links and sinks, even from VPCs without internet access. This feature supports both IPv4 and IPv6 addressing, and you can use AWS PrivateLink’s built-in security controls—like security groups and VPC endpoint policies—to help secure access to your observability resources.

CloudWatch Observability Access Manager VPC endpoints are now available in all commercial AWS regions, the AWS GovCloud (US) Regions, and the China Regions.

To start using VPC endpoints for CloudWatch Observability Access Manager, refer to CloudWatch OAM endpoints for a list of supported Regional endpoints. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink.

​AWS announces VPC endpoints for Amazon CloudWatch Observability Access Manager (OAM). CloudWatch OAM enables you to programmatically manage cross-account observability settings within a region. The new VPC endpoints enhance your security posture by keeping traffic between your VPC and CloudWatch OAM within the AWS network, eliminating the need to traverse the public internet. You can use Observability Access Manager to create and manage links between source accounts and monitoring accounts, enabling you to monitor and troubleshoot applications that span multiple accounts within a Region. With the new VPC endpoints, you can establish secure, private, and reliable connections between your VPC and CloudWatch Observability Access Manager. This allows you to maintain private connectivity while managing cross-account observability links and sinks, even from VPCs without internet access. This feature supports both IPv4 and IPv6 addressing, and you can use AWS PrivateLink’s built-in security controls—like security groups and VPC endpoint policies—to help secure access to your observability resources. CloudWatch Observability Access Manager VPC endpoints are now available in all commercial AWS regions, the AWS GovCloud (US) Regions, and the China Regions. To start using VPC endpoints for CloudWatch Observability Access Manager, refer to CloudWatch OAM endpoints for a list of supported Regional endpoints. To learn more about AWS PrivateLink, see accessing AWS services through AWS PrivateLink.  

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C6in instances are available in AWS Region Asia Pacific (Thailand). These sixth-generation network optimized instances, powered by 3rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances.

Customers can use C6in instances to scale the performance of applications such as network virtual appliances (firewalls, virtual routers, load balancers), Telco 5G User Plane Function (UPF), data analytics, high performance computing (HPC), and CPU based AI/ML workloads. C6in instances are available in 10 different sizes with up to 128 vCPUs, including bare metal size. Amazon EC2 sixth-generation x86-based network optimized EC2 instances deliver up to 100Gbps of Amazon Elastic Block Store (Amazon EBS) bandwidth, and up to 400K IOPS. C6in instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes.

C6in instances are available in these AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Middle East (Bahrain, UAE), Israel (Tel Aviv), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo, Thailand), Africa (Cape Town), South America (Sao Paulo), Canada (Central), Canada West (Calgary), and AWS GovCloud (US-West, US-East). To learn more, see the Amazon EC2 C6in instances. To get started, see the AWS Management Console, AWS Command Line Interface (AWS CLI), and AWS SDKs. 

​Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C6in instances are available in AWS Region Asia Pacific (Thailand). These sixth-generation network optimized instances, powered by 3rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances. Customers can use C6in instances to scale the performance of applications such as network virtual appliances (firewalls, virtual routers, load balancers), Telco 5G User Plane Function (UPF), data analytics, high performance computing (HPC), and CPU based AI/ML workloads. C6in instances are available in 10 different sizes with up to 128 vCPUs, including bare metal size. Amazon EC2 sixth-generation x86-based network optimized EC2 instances deliver up to 100Gbps of Amazon Elastic Block Store (Amazon EBS) bandwidth, and up to 400K IOPS. C6in instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes. C6in instances are available in these AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Middle East (Bahrain, UAE), Israel (Tel Aviv), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Tokyo, Thailand), Africa (Cape Town), South America (Sao Paulo), Canada (Central), Canada West (Calgary), and AWS GovCloud (US-West, US-East). To learn more, see the Amazon EC2 C6in instances. To get started, see the AWS Management Console, AWS Command Line Interface (AWS CLI), and AWS SDKs.