Starting today, Amazon Q Developer operational investigations is available in preview in 11 additional regions. With this launch, Amazon Q Developer operational investigations is now available in US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Asia Pacific (Tokyo), Asia Pacific (Hong Kong), Asia Pacific (Sydney), Asia Pacific (Singapore), and Asia Pacific (Mumbai).
Amazon Q Developer helps you accelerate operational investigations across your AWS environment in just a fraction of the time. With a deep understanding of your AWS cloud environment and resources, Amazon Q Developer looks for anomalies in your environment, surfaces related signals for you to explore, identifies potential root-cause hypotheses, and suggests next steps to help you remediate issues faster.
The new operational investigation capability within Amazon Q Developer is available at no additional cost during preview. To learn more, see getting started and best practices documentation.
Starting today, Amazon Q Developer operational investigations is available in preview in 11 additional regions. With this launch, Amazon Q Developer operational investigations is now available in US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Asia Pacific (Tokyo), Asia Pacific (Hong Kong), Asia Pacific (Sydney), Asia Pacific (Singapore), and Asia Pacific (Mumbai). Amazon Q Developer helps you accelerate operational investigations across your AWS environment in just a fraction of the time. With a deep understanding of your AWS cloud environment and resources, Amazon Q Developer looks for anomalies in your environment, surfaces related signals for you to explore, identifies potential root-cause hypotheses, and suggests next steps to help you remediate issues faster. The new operational investigation capability within Amazon Q Developer is available at no additional cost during preview. To learn more, see getting started and best practices documentation.
Amazon Bedrock Data Automation (BDA) now supports modality enablement, modality routing by file type, extraction of embedded hyperlinks when processing documents in Standard Output, and an increased overall document page limit of 3,000 pages. These new features give you more control over how your multimodal content is processed and improve BDA’s overall document extraction capabilities.
With Modality Enablement and Routing, you can configure which modalities (Document, Image, Audio, Video) should be enabled for a given project and manually specify the modality routing for specific file types. JPEG/JPG and PNG files can be processed as either Images or Documents based on your specific use case requirements. Similarly, MP4/M4V and MOV files can be processed as either video files or audio files, allowing you to choose the optimal processing path for your content.
Embedded Hyperlink Support enables BDA to detect and return embedded hyperlinks found in PDFs as part of the BDA standard output. This feature enhances the information extraction capabilities from documents, preserving valuable link references for applications such as knowledge bases, research tools, and content indexing systems.
Lastly, BDA now supports processing documents up to 3,000 pages per document, doubling the previous limit of 1,500 pages. This increased limit allows you to process larger documents without splitting them, simplifying workflows for enterprises dealing with long documents or document packets.
Amazon Bedrock Data Automation is generally available in the US West (Oregon) and US East (N. Virginia) AWS Regions.
Amazon Bedrock Data Automation (BDA) now supports modality enablement, modality routing by file type, extraction of embedded hyperlinks when processing documents in Standard Output, and an increased overall document page limit of 3,000 pages. These new features give you more control over how your multimodal content is processed and improve BDA’s overall document extraction capabilities. With Modality Enablement and Routing, you can configure which modalities (Document, Image, Audio, Video) should be enabled for a given project and manually specify the modality routing for specific file types. JPEG/JPG and PNG files can be processed as either Images or Documents based on your specific use case requirements. Similarly, MP4/M4V and MOV files can be processed as either video files or audio files, allowing you to choose the optimal processing path for your content. Embedded Hyperlink Support enables BDA to detect and return embedded hyperlinks found in PDFs as part of the BDA standard output. This feature enhances the information extraction capabilities from documents, preserving valuable link references for applications such as knowledge bases, research tools, and content indexing systems. Lastly, BDA now supports processing documents up to 3,000 pages per document, doubling the previous limit of 1,500 pages. This increased limit allows you to process larger documents without splitting them, simplifying workflows for enterprises dealing with long documents or document packets. Amazon Bedrock Data Automation is generally available in the US West (Oregon) and US East (N. Virginia) AWS Regions. To learn more, visit the Bedrock Data Automation page or view documentation.
Starting today, in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions, you can now deliver events from an Amazon EventBridge Event Bus directly to AWS services in another account. Using multiple accounts can improve security and streamline business processes while reducing the overall cost and complexity of your architecture.
Amazon EventBridge Event Bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. This launch allows you to directly target services in another account, without the need for additional infrastructure such as an intermediary EventBridge Event Bus or Lambda function, simplifying your architecture and reducing cost. For example, you can now route events from your EventBridge Event Bus directly to a different team’s SQS queue in a different account. The team receiving events does not need to learn about or maintain EventBridge resources and simply needs to grant IAM permissions to provide access to the queue. Events can be delivered cross-account to EventBridge targets that support resource-based IAM policies such as Amazon SQS, AWS Lambda, Amazon Kinesis Data Streams, Amazon SNS, and Amazon API Gateway.
In addition to the AWS GovCloud (US) Regions, direct delivery to cross-account targets is available in all commercial AWS Regions. To learn more, please read our blog post or visit our documentation. Pricing information is available on the EventBridge pricing page.
Starting today, in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions, you can now deliver events from an Amazon EventBridge Event Bus directly to AWS services in another account. Using multiple accounts can improve security and streamline business processes while reducing the overall cost and complexity of your architecture. Amazon EventBridge Event Bus is a serverless event broker that enables you to create scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. This launch allows you to directly target services in another account, without the need for additional infrastructure such as an intermediary EventBridge Event Bus or Lambda function, simplifying your architecture and reducing cost. For example, you can now route events from your EventBridge Event Bus directly to a different team’s SQS queue in a different account. The team receiving events does not need to learn about or maintain EventBridge resources and simply needs to grant IAM permissions to provide access to the queue. Events can be delivered cross-account to EventBridge targets that support resource-based IAM policies such as Amazon SQS, AWS Lambda, Amazon Kinesis Data Streams, Amazon SNS, and Amazon API Gateway. In addition to the AWS GovCloud (US) Regions, direct delivery to cross-account targets is available in all commercial AWS Regions. To learn more, please read our blog post or visit our documentation. Pricing information is available on the EventBridge pricing page.
Today, AWS Resource Groups is adding support for an additional 160 resource types for tag-based Resource Groups. Customers can now use Resource Groups to group and manage resources from services such as AWS Code Catalyst and AWS Chatbot.
AWS Resource Groups enables you to model, manage and automate tasks on large numbers of AWS resources by using tags to logically group your resources. You can create logical collections of resources such as applications, projects, and cost centers, and manage them on dimensions such as cost, performance, and compliance in AWS services such as myApplications, AWS Systems Manager and Amazon CloudWatch.
Resource Groups expanded resource type coverage is available in all AWS Regions, including the AWS GovCloud (US) Regions. You can access AWS Resource Groups through the AWS Management Console, the AWS SDK APIs, and the AWS CLI.
Today, AWS Resource Groups is adding support for an additional 160 resource types for tag-based Resource Groups. Customers can now use Resource Groups to group and manage resources from services such as AWS Code Catalyst and AWS Chatbot. AWS Resource Groups enables you to model, manage and automate tasks on large numbers of AWS resources by using tags to logically group your resources. You can create logical collections of resources such as applications, projects, and cost centers, and manage them on dimensions such as cost, performance, and compliance in AWS services such as myApplications, AWS Systems Manager and Amazon CloudWatch. Resource Groups expanded resource type coverage is available in all AWS Regions, including the AWS GovCloud (US) Regions. You can access AWS Resource Groups through the AWS Management Console, the AWS SDK APIs, and the AWS CLI. For more information about grouping resources, see the AWS Resource Groups user guide and the list of supported resource types. To get started, visit AWS Resource Groups console.
The Amazon Connect agent workspace now supports additional capabilities for third-party applications including the ability make outbound calls, accept, transfer, and clear contacts, and update agent status. These enhancements allow you to integrate applications that give agents more intuitive workflows. For example, agents can now initiate one-click outbound calls from a custom-built call history interface that presents their most recent customer interactions.
Third-party applications are available in the following AWS Regions: US East (N. Virginia), US-West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London).
The Amazon Connect agent workspace now supports additional capabilities for third-party applications including the ability make outbound calls, accept, transfer, and clear contacts, and update agent status. These enhancements allow you to integrate applications that give agents more intuitive workflows. For example, agents can now initiate one-click outbound calls from a custom-built call history interface that presents their most recent customer interactions. Third-party applications are available in the following AWS Regions: US East (N. Virginia), US-West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London). To learn more and get started, see our admin guide and developer guide.
Starting today, AWS AppSync Events, a fully managed service for serverless WebSocket APIs with full connection management, now supports data source integrations for channel namespaces. This new feature enables developers to associate AWS Lambda functions, Amazon DynamoDB tables, Amazon Aurora databases, and other data sources with channel namespace handlers to process published events and subscription requests. Developers can now connect directly to Lambda functions without writing code and leverage both request/response and event modes for synchronous and asynchronous operations.
With these new capabilities, developers can create sophisticated event processing workflows by transforming and filtering published events using Lambda functions, or save batches of events to DynamoDB using the new AppSyncJS batch utilities for DynamoDB. This integration enables complex interactive flows, making it easier for developers to build rich, real-time applications with features like data validation, event transformation, and persistent storage of events. By simplifying the architecture of real-time applications, this enhancement significantly reduces development time and operational overhead for front-end web and mobile development.
This feature is now available in all AWS Regions where AWS AppSync is offered, providing developers worldwide with access to these powerful new integration capabilities. Powertools for AWS Lambda new AppSync Events integration are also now available to easily write your Lambda functions.
To learn more about AWS AppSync Events and channel namespace integrations, visit thelaunch blog post, the AWS AppSync documentation, and the Powertools for Lambda documentation (TypeScript, Python, .NET). You can get started with these new features through the AWS AppSync console.
Starting today, AWS AppSync Events, a fully managed service for serverless WebSocket APIs with full connection management, now supports data source integrations for channel namespaces. This new feature enables developers to associate AWS Lambda functions, Amazon DynamoDB tables, Amazon Aurora databases, and other data sources with channel namespace handlers to process published events and subscription requests. Developers can now connect directly to Lambda functions without writing code and leverage both request/response and event modes for synchronous and asynchronous operations. With these new capabilities, developers can create sophisticated event processing workflows by transforming and filtering published events using Lambda functions, or save batches of events to DynamoDB using the new AppSyncJS batch utilities for DynamoDB. This integration enables complex interactive flows, making it easier for developers to build rich, real-time applications with features like data validation, event transformation, and persistent storage of events. By simplifying the architecture of real-time applications, this enhancement significantly reduces development time and operational overhead for front-end web and mobile development. This feature is now available in all AWS Regions where AWS AppSync is offered, providing developers worldwide with access to these powerful new integration capabilities. Powertools for AWS Lambda new AppSync Events integration are also now available to easily write your Lambda functions. To learn more about AWS AppSync Events and channel namespace integrations, visit the launch blog post, the AWS AppSync documentation, and the Powertools for Lambda documentation (TypeScript, Python, .NET). You can get started with these new features through the AWS AppSync console.
With this launch, VPC Reachability Analyzer and VPC Network Access Analyzer are now available in Europe (Spain) Region.
VPC Reachability Analyzer allows you to diagnose network reachability between a source resource and a destination resource in your virtual private clouds (VPCs) by analyzing your network configurations.For example, Reachability Analyzer can help you identify a missing route table entry in your VPC route table that could be blocking network reachability between an EC2 instance in Account A that is not able to connect to another EC2 instance in Account B in your AWS Organization.
VPC Network Access Analyzer allows you to identify unintended network access to your resources on AWS. Using Network Access Analyzer, you can verify whether network access for your VPC resources meets your security and compliance guidelines. For example, you can create a scope to verify that the VPCs used by your Finance team are separate, distinct, and unreachable from the VPCs used by your Development team.
With this launch, VPC Reachability Analyzer and VPC Network Access Analyzer are now available in Europe (Spain) Region. VPC Reachability Analyzer allows you to diagnose network reachability between a source resource and a destination resource in your virtual private clouds (VPCs) by analyzing your network configurations.For example, Reachability Analyzer can help you identify a missing route table entry in your VPC route table that could be blocking network reachability between an EC2 instance in Account A that is not able to connect to another EC2 instance in Account B in your AWS Organization. VPC Network Access Analyzer allows you to identify unintended network access to your resources on AWS. Using Network Access Analyzer, you can verify whether network access for your VPC resources meets your security and compliance guidelines. For example, you can create a scope to verify that the VPCs used by your Finance team are separate, distinct, and unreachable from the VPCs used by your Development team. For more information on features, visit documentation for VPC Reachability Analyzer and VPC Network Access Analyzer. For pricing details, refer to the Network Analysis tab on the Amazon VPC Pricing Page.
Amazon SageMaker Lakehouse now supports attribute-based access control (ABAC), using AWS Identity and Access Management (IAM) principal and session tags to simplify data access, grant creation, and maintenance. With ABAC, you can manage permissions using dynamic business attributes associated with user identities.
Previously, SageMaker Lakehouse granted access to lakehouse databases and tables by directly assigning permissions to specific principals such as IAM users and IAM roles, a process that could quickly become unwieldy as the number of users grew. ABAC now allows administrators to grant permissions on a resource with conditions that specify user attribute keys and values. This means that any IAM principal or IAM role with matching principal or session tag keys and values will automatically have access to the resource making the experience more efficient. You can use ABAC though the AWS Lake Formation console to provide access to IAM users and IAM roles for both in-account and cross-account scenarios. For instance, rather than creating individual policies for each developer, administrators can now simply assign them an IAM tag with a key such as “team” and value «developers» and provide access to all developers with a single permission grant. As new developers join with the matching tag and value, no additional policy modifications are required.
This feature is available in all AWS Regions where SageMaker Lakehouse is available. To get started, read the launch blog and read ABAC documentation.
Amazon SageMaker Lakehouse now supports attribute-based access control (ABAC), using AWS Identity and Access Management (IAM) principal and session tags to simplify data access, grant creation, and maintenance. With ABAC, you can manage permissions using dynamic business attributes associated with user identities. Previously, SageMaker Lakehouse granted access to lakehouse databases and tables by directly assigning permissions to specific principals such as IAM users and IAM roles, a process that could quickly become unwieldy as the number of users grew. ABAC now allows administrators to grant permissions on a resource with conditions that specify user attribute keys and values. This means that any IAM principal or IAM role with matching principal or session tag keys and values will automatically have access to the resource making the experience more efficient. You can use ABAC though the AWS Lake Formation console to provide access to IAM users and IAM roles for both in-account and cross-account scenarios. For instance, rather than creating individual policies for each developer, administrators can now simply assign them an IAM tag with a key such as “team” and value «developers» and provide access to all developers with a single permission grant. As new developers join with the matching tag and value, no additional policy modifications are required. This feature is available in all AWS Regions where SageMaker Lakehouse is available. To get started, read the launch blog and read ABAC documentation.
AWS AppConfig now supports dual-stack endpoints, facilitating connectivity through Internet Protocol Version 6. The existing AWS AppConfig endpoints supporting IPv4 will remain available for backwards compatibility.
The continuous growth of the internet has created an urgent need for IPv6 adoption, as IPv4 address space reaches its limits. Through AWS AppConfig’s implementation of dual-stack endpoints, organizations can execute a strategic transition to IPv6 architecture on their own timeline. This approach enables companies to satisfy IPv6 regulatory standards while preserving IPv4 connectivity for systems that have not yet moved to IPv6 capabilities.
AWS AppConfig now supports dual-stack endpoints, facilitating connectivity through Internet Protocol Version 6. The existing AWS AppConfig endpoints supporting IPv4 will remain available for backwards compatibility. The continuous growth of the internet has created an urgent need for IPv6 adoption, as IPv4 address space reaches its limits. Through AWS AppConfig’s implementation of dual-stack endpoints, organizations can execute a strategic transition to IPv6 architecture on their own timeline. This approach enables companies to satisfy IPv6 regulatory standards while preserving IPv4 connectivity for systems that have not yet moved to IPv6 capabilities. IPv6 support for AWS AppConfig resources is available in all AWS Regions, including the AWS GovCloud (US) Regions. To get started, use the AWS AppConfig Getting Started Guide, or read more at Understanding IPv6 support for AWS AppConfig.
Por: Rani Borkar, vicepresidenta corporativa de sistemas de hardware e infraestructura de Azure.
Anunciamos la consecución de un hito importante en nuestro camino hacia cero residuos en 2030: hemos alcanzado una tasa de reutilización y reciclaje de servidores y componentes del 90,9% en 2024, lo que supera nuestro objetivo para 2025 del 90% anual antes de lo previsto.
Cero residuos para 2030 es una piedra angular de nuestra estrategia de sostenibilidad, junto con convertirnos en carbono negativo, agua positiva y proteger más tierra de la que utilizamos. Este hito reciente, impulsado por una cultura de innovación y colaboración interfuncional, refleja el creciente impulso para integrar prácticas de cero residuos y circularidad en toda la industria tecnológica.
Con el trabajo en conjunto con nuestros socios y proveedores de recuperación, avanzamos en la sostenibilidad de nuestra cadena de suministro en la nube y avanzamos hacia nuestro objetivo de cero residuos en tres áreas clave: (1) pilotar la extracción sostenible de minerales de tierras raras de unidades de disco duro a escala, (2) continuar la expansión de nuestros Centros Circulares en todo el mundo y (3) creación en conjunto de soluciones de embalaje reciclables para el transporte de hardware de centros de datos.
Innovar para crear un suministro de elementos de tierras raras reciclados con sede en EE. UU.
Hoy anunciamos una colaboración con Western Digital, Critical Materials Recycling y PedalPoint Recycling que demuestra cómo transformamos aproximadamente 50 mil libras de unidades de disco duro (HDD, por sus siglas en inglés) al final de su vida útil y otros materiales en materiales críticos de alto valor, para recuperar elementos de tierras raras (REE, por sus siglas en inglés) como el neodimio y metales preciosos como el oro y el cobre. Al permitir que el proceso de recuperación de REE se gestione a nivel nacional, el programa se diseñó para minimizar las emisiones del transporte y aumentar la resiliencia de la cadena de suministro de REE de los Estados Unidos al disminuir la dependencia de los materiales importados.
Cuando los discos duros se retiran del servicio, los componentes portadores de datos se desinfectan y trituran para garantizar la seguridad de los datos, mientras que otros componentes se separan para permitir el reciclaje y la recirculación de los materiales REE. Esta iniciativa abordó algunos de los desafíos técnicos persistentes con el reciclaje de REE: desarrollar métodos para lograr una alta tasa de recuperación de los materiales, encontrar una técnica de reciclaje que evite el uso de productos químicos agresivos y demostrar que el proceso de reciclaje de REE puede ser viable a nivel económico a largo plazo.
La innovadora disolución sin ácido de los discos duros triturados proporcionó una impresionante recuperación de alto rendimiento del 90% de materiales elementales y de tierras raras. Además, el proceso de reciclaje tiene una reducción estimada del 95% en las emisiones en comparación con las prácticas tradicionales de minería y procesamiento, según el análisis del ciclo de vida. Esta iniciativa, que estableció un nuevo estándar para la recuperación industrial de materiales críticos, fue una de las primeras demostraciones del reciclaje a gran escala en el país de metales y materiales esenciales.
Expansión de los Centros Circulares en todo el mundo
En toda la empresa, nuestros equipos trabajan para mejorar la eficiencia de los recursos y ampliar el valor de la vida útil de los materiales a través de las tres R: reducir, reutilizar y recuperar. Dentro de nuestros centros de datos globales, nuestros Centros Circulares de Microsoft son fundamentales para nuestro progreso, ya que nos permiten procesar y enrutar servidores y componentes de hardware fuera de servicio a sus próximas vidas útiles, como la reutilización interna, otras cadenas de suministro electrónico o academias que capacitan a los técnicos de los centros de datos.
Al rediseñar los sistemas para reducir los residuos, y luego reutilizar y recuperar materiales siempre que sea posible, ahorramos costos, para ganar eficiencia y descubrir nuevas oportunidades para los componentes de hardware e infraestructura. Por ejemplo, hemos reutilizado con éxito más de 3,2 millones de componentes a través de canales internos y externos en 2024, para reconocer un aumento del 30% o más en la recuperación de valor a través de nuestro programa Circular Center.
Desde que abrimos nuestro primer Centro Circular en Ámsterdam (Países Bajos) en 2020, hemos construido cinco instalaciones adicionales en Estados Unidos: Boydton, Virginia; Chicago, Illinois; y Quincy, Washington, así como en Dublín, Irlanda, y Singapur. Para continuar con la conexión de nuestra reutilización y reciclaje en todo el mundo, se planean nuevos Centros Circulares en Cardiff, Gales; Nueva Gales del Sur, Australia; y San Antonio, Texas.
A medida que avanzamos en los últimos cinco años, nos entusiasma seguir con la aceleración de las prácticas de circularidad en todo nuestro negocio. La prevención de residuos se mantiene como el núcleo de nuestra estrategia de residuo cero. Además, seguimos con la inversión en la expansión de los mercados de soluciones circulares y con la colaboración con organizaciones locales para apoyar la circularidad en las comunidades en las que operamos y trabajamos.
Creación conjunta de soluciones de empaquetado novedosas para hardware de centros de datos
Además de avanzar en la circularidad del hardware, también abordamos el desafío de empaquetar todo el hardware y los componentes que usamos en nuestros centros de datos. Con más de 150 fabricantes de equipos originales (OEM, por sus siglas en inglés) que suministran nuestros centros de datos, las soluciones deben garantizar el mismo nivel de protección y seguridad para servidores, racks y componentes que los métodos de empaquetado tradicionales.
Uno de los principales desafíos con el empaquetado para el hardware y los componentes de nuestros centros de datos es que suele tener varias capas, por ejemplo, el empaquetado para racks de servidores puede incluir una capa de madera, luego pegamento, espuma y luego más madera. Debido a esto, el empaque por lo general no era reciclable a través de la recogida en la acera. Durante los últimos 18 meses, nuestro equipo de logística en la nube ha trabajado con proveedores, proveedores de servicios logísticos y recicladores para tomar esos palés y separar las capas, para hacer que los materiales sean reciclables a través de colaboraciones locales.
Como resultado, el embalaje de más de 30 mil racks de servidores se procesó a través de nuestro programa global de reciclaje de envases, para desviar más de 2.500 toneladas métricas de residuos de los vertederos. En el futuro, estamos en proceso de exploración de la expansión de este programa de reciclaje a otros tipos de embalajes, como los que se utilizan para cables, repuestos y componentes de red.
Más allá del reciclaje, nuestros equipos buscan oportunidades para reutilizar materiales dentro de la cadena de valor para reducir la necesidad de adquirir algo nuevo y permitir un mayor desvío de residuos, ya sea para hardware, componentes o embalajes. Por ejemplo, trabajamos para reducir la espuma de polietileno expandido (EPE, por sus siglas en inglés) a base de plástico, difícil de reciclar, en los envases, sustituyéndola por alternativas de papel y pulpa más sostenibles.
Otra forma impactante de aumentar la circularidad en nuestra cadena de suministro es con innovaciones en el embalaje de nuestros racks de servidores. En la actualidad, probamos soluciones reutilizables que promueven la sostenibilidad y mejoran la eficiencia empresarial, al reducir los costos y proporcionar consistencia en la experiencia de desempaquetado para los equipos de centros de datos, al tiempo que mantenemos los racks de servidores seguros durante el transporte y la manipulación.
Exploren el trabajo de Microsoft para reducir el desperdicio en nuestros centros de datos
Para obtener más información sobre el trabajo de Microsoft para reducir el desperdicio en nuestros centros de datos, consulten datacenters.microsoft.com/sustainability.
Para los líderes empresariales interesados en desarrollar una estrategia circular para su organización, lean el documento técnico Cuatro pilares de un programa de hardware de centro de datos circular exitoso con una visión más profunda de cuatro aspectos esenciales del programa Circular Center de Microsoft.
