AWS Config now supports 4 additional AWS resource types. This expansion provides greater coverage over your AWS environment, enabling you to more effectively discover, assess, audit, and remediate an even broader range of resources.
With this launch, if you have enabled recording for all resource types, then AWS Config will automatically track these new additions. The newly supported resource types are also available in Config rules and Config aggregators.
You can now use AWS Config to monitor the following newly supported resource types in all AWS Regions where the supported resources are available:
AWS::EC2::VPCBlockPublicAccessExclusion
AWS::EC2::VPCBlockPublicAccessOptions
AWS::S3Express::BucketPolicy
AWS::S3Express::DirectoryBucket
To view the complete list of AWS Config supported resource types, see supported resource types page.
AWS Config now supports 4 additional AWS resource types. This expansion provides greater coverage over your AWS environment, enabling you to more effectively discover, assess, audit, and remediate an even broader range of resources. With this launch, if you have enabled recording for all resource types, then AWS Config will automatically track these new additions. The newly supported resource types are also available in Config rules and Config aggregators.
You can now use AWS Config to monitor the following newly supported resource types in all AWS Regions where the supported resources are available:
AWS Marketplace now supports custom payment schedules for private offers, giving Channel Partners the ability to add margins on private offers with installment plans. Channel Partners can now adjust each scheduled payment individually, either through the AWS Marketplace Management Portal or the AWS Marketplace Catalog API.
Previously, Channel Partners could only apply a uniform percentage markup across all installments in a private offer. With this update, they can now adjust the payment amount for each installment in the schedule, providing greater flexibility in structuring deals and managing cash flow. Once the buyer accepts and pays their invoices, the Channel Partner and independent software vendor (ISV) will receive their appropriate payment as defined in the offer and resell agreement. This saves Channel Partners significant time and effort, eliminating the need to request margin updates from AWS.
Channel Partners can use this feature for all AWS Marketplace products using installment plans sold through Channel Partner private offers, across all supported currencies. This feature is available in all AWS Regions where AWS Marketplace is available.
AWS Marketplace now supports custom payment schedules for private offers, giving Channel Partners the ability to add margins on private offers with installment plans. Channel Partners can now adjust each scheduled payment individually, either through the AWS Marketplace Management Portal or the AWS Marketplace Catalog API. Previously, Channel Partners could only apply a uniform percentage markup across all installments in a private offer. With this update, they can now adjust the payment amount for each installment in the schedule, providing greater flexibility in structuring deals and managing cash flow. Once the buyer accepts and pays their invoices, the Channel Partner and independent software vendor (ISV) will receive their appropriate payment as defined in the offer and resell agreement. This saves Channel Partners significant time and effort, eliminating the need to request margin updates from AWS. Channel Partners can use this feature for all AWS Marketplace products using installment plans sold through Channel Partner private offers, across all supported currencies. This feature is available in all AWS Regions where AWS Marketplace is available. To learn more, visit the AWS Marketplace Seller Guide. To try the new capability, visit the AWS Marketplace Management Portal.
Amazon FSx now offers customers the option to use Internet Protocol version 6 (IPv6) while accessing the Amazon FSx Service APIs.
More and more customers are adopting IPv6 to mitigate IPv4 address exhaustion in their private networks or to satisfy government mandates such as such as the US Office of Management and Budget (OMB) M-21-07 memorandum. With this launch, customers can standardize their applications and workflows for managing their Amazon FSx resources on the new version of Internet Protocol by using the new dual-stack Amazon FSx Service endpoints.
IPv6 support for Amazon FSx Service APIs is available in all commercial, AWS GovCloud (US), and AWS China regions where Amazon FSx is available. To learn more, visit the Amazon FSx user guide.
Amazon FSx now offers customers the option to use Internet Protocol version 6 (IPv6) while accessing the Amazon FSx Service APIs. More and more customers are adopting IPv6 to mitigate IPv4 address exhaustion in their private networks or to satisfy government mandates such as such as the US Office of Management and Budget (OMB) M-21-07 memorandum. With this launch, customers can standardize their applications and workflows for managing their Amazon FSx resources on the new version of Internet Protocol by using the new dual-stack Amazon FSx Service endpoints. IPv6 support for Amazon FSx Service APIs is available in all commercial, AWS GovCloud (US), and AWS China regions where Amazon FSx is available. To learn more, visit the Amazon FSx user guide.
IA en acción: 3 escenarios para liberar todo el potencial de la IA
Si no basan la tecnología en sus datos de trabajo, dejan valor sobre la mesa.
Por Jared Spataro, CMO de IA en el Trabajo de Microsoft.
Al comenzar 2025, una resolución de Año Nuevo que escuché varias veces es que las personas quieren ser más inteligentes con la IA. Incluso si ya usan la IA en el trabajo todos los días, siempre hay más que aprender. Todavía tengo momentos de «sorpresa» todo el tiempo, en los que me doy cuenta de que el factor limitante de lo que puedo hacer con la IA no es la tecnología en sí, sino mi propia imaginación.
Con ese espíritu, me gustaría compartir algunos escenarios de Copilot que me parecen más útiles en el trabajo. El denominador común aquí es que la IA es mucho más poderosa cuando la conectan a sus propios datos de trabajo únicos (sus correos electrónicos, archivos, reuniones), por lo que sus respuestas se basan en la realidad de su negocio específico. Muchos usuarios de IA, incluso los más expertos, no aprovechan al máximo esa oportunidad. Y, sin embargo, esos son los escenarios de IA que desbloquean la mayor magia.
Escenario 1: Priorizar su correo electrónico
Puede ser difícil mantenerse al tanto del correo electrónico: nuestra investigación muestra que los usuarios que más usan Microsoft 365 reciben más de 250 correos electrónicos al día. Me identifico: mi bandeja de entrada a veces se siente como un lugar donde la gente tan solo acumula elementos en mi lista de tareas pendientes. Con Copilot, todas esas preguntas son mucho más fáciles de gestionar y priorizar.
Les doy un ejemplo. Regresé de las vacaciones con una montaña de mensajes. Para ponerme al día de manera rápida, utilicé la función «priorizar mi bandeja de entrada» de Copilot. Copilot analizó mi bandeja de entrada y colocó los mensajes más importantes en la parte superior, explicó por qué esos correos electrónicos eran críticos y me dio elementos de acción específicos en cada caso. Miren cómo funciona aquí.
Copilot no solo se fija en el remitente y la línea de asunto, sino que analiza todo el mensaje y toma una decisión informada sobre cómo priorizarlo para mí. Una nota de un colega con el asunto «¿Café y una rosquilla?» puede no parecer demasiado apremiante. Pero Copilot se daba cuenta de que el remitente quería discutir un gran acuerdo potencial para firmar al final de la semana, y me lo señalaba.
También pueden enseñarle a Copilot qué correos electrónicos son más importantes para ustedes (un cliente importante, por ejemplo, o su gerente). Le pido a Copilot que esté atento a los mensajes de mi jefe para asegurarme de que nunca me pierda nada esencial de él. Y si hay un problema urgente con el cliente del que tengo que estar al tanto, también puedo hacer que Copilot esté atento a esos correos electrónicos.
El resultado: si solo utilizan la IA para escribir correos electrónicos, y no para ayudarse a reducir la sobrecarga de correo electrónico, se pierden de algo importante.
Más prompts para ayudar a mantener su correo electrónico bajo control:
«Muéstrame los correos electrónicos más urgentes de hoy».
«Resume los correos electrónicos no leídos de los últimos 15 días, con especial atención a los de mis principales colaboradores y gerentes. Identifica los correos electrónicos más urgentes e importantes para leer primero».
«Resalta todos los correos electrónicos con elementos de acción o plazos en mi bandeja de entrada».
Escenario 2: Incorporar la inteligencia del lugar de trabajo en su prompt
Muchas personas con las que hablo todavía usan prompts genéricos («Escribe un correo electrónico de agradecimiento que diga X, Y y Z»). A veces, copian y pegan datos de otros archivos en su mensaje cuando quieren que Copilot haga referencia a ellos. Pero hay una mejor manera.
Para obtener respuestas relevantes y personalizadas, pueden remitir a Copilot a archivos de trabajo específicos para que pueda extraer el conocimiento y los datos de su empresa sin problemas. De esa manera, no perderán el tiempo en buscar información en documentos y pegándola en sus prompts.
Otro ejemplo: si reciben un documento de estrategia importante pero extenso y necesitan responder rápido con información, hagan que Copilot les dé una ventaja inicial al resumir el documento y resaltar las brechas y las señales de alerta. Solo tienen que citar el nombre del archivo en el mensaje y Copilot hará referencia a los datos de origen originales, sin necesidad de copiar y pegar.
Todos hemos escuchado historias de terror sobre empleados que conectan documentos confidenciales a herramientas de IA centradas en el consumidor y filtran de manera inadvertida información confidencial. Pero Copilot es seguro. Las solicitudes y los datos nunca se usan para entrenar modelos de lenguaje de gran tamaño. Y el cifrado sólido y la autenticación multifactor garantizan que solo los usuarios autorizados puedan acceder a sus documentos.
Escenario 3: Usar un agente de SharePoint
Cada día se cargan más de 2 mil millones de archivos en SharePoint. Mi equipo (como la mayoría de los equipos) tiene una cantidad abrumadora de archivos compartidos, y lleva mucho tiempo revisarlos todos para rastrear la información que necesito. En su lugar, utilizo agentes de IA de SharePoint para responder preguntas sobre el contenido de cualquier sitio o biblioteca de SharePoint al que tenga acceso.
Cada vez que tengo una reunión con un cliente, recibo un documento informativo que me brinda una descripción general de la cuenta, una agenda y los temas que se deben abordar durante la conversación. Todos estos documentos se guardan en un solo sitio de SharePoint, por lo que puedo usar un agente de SharePoint para ponerme al día antes de la reunión. Siempre me sorprendo cuando le pido «Prepáreme para mis reuniones con los clientes esta semana». El agente extrae información directo del sitio de SharePoint que consulto y sé que los resultados son precisos porque provienen directo de los archivos de origen originales.
Cualquier persona que tenga permisos de edición en un sitio de SharePoint puede crear agentes para tareas específicas y compartirlos con su equipo. Y crear estos agentes no podría ser más fácil, solo se necesitan unos pocos clics. Mírenlo en acción aquí.
Los agentes de SharePoint son útiles en todas las funciones. Digamos que se dedican a las finanzas. Pueden crear un agente personalizado con acceso a los informes financieros de los últimos cinco años y, a continuación, pedirle que les recomiende movimientos que ahorren costos. En TI, podrían crear un agente que pueda analizar los comentarios de los clientes para identificar tendencias y detectar oportunidades para productos futuros.
Piensen en los agentes de SharePoint como expertos en la materia virtual, que siempre están listos para desenterrar lo que necesitan (y, a veces, lo que no se dieron cuenta que necesitaban).
Escenarios empresariales comunes para agentes de SharePoint
Amplíen la experiencia individual y de equipo para ayudar a ahorrar tiempo y optimizar los procesos empresariales.
Resultado empresarial: Menor tiempo medio de resolución (ART) Cómo pueden ayudar los agentes: Obtengan respuestas precisas más rápido, basadas en documentos de implementación específicos
Resultado empresarial: Aumento de la tasa de conversión de ventas Cómo pueden ayudar los agentes: Proponer modelos de productos basados en criterios específicos, junto con alternativas recomendadas
Resultado empresarial: Menor tiempo del ciclo de análisis Cómo pueden ayudar los agentes: Obtengan recomendaciones de ahorro de costos mediante el análisis de años de informes financieros
Resultado empresarial: Disminución del tiempo de comercialización Cómo pueden ayudar los agentes: Proporcionar una opción para las actualizaciones de productos basada en la documentación más reciente del producto
Resultado empresarial: Reducción del tiempo de incorporación Cómo pueden ayudar los agentes: Optimicen el aprendizaje y el consumo de información con agentes de incorporación específicos de la función
Resultado empresarial: Mejora de la coherencia de los contratos y del tiempo de revisión Cómo pueden ayudar los agentes: Acceso a la experiencia en contratos, documentos similares y criterios específicos al revisar documentos
Resultado empresarial: Aumento de la puntuación de satisfacción del usuario Cómo pueden ayudar los agentes: Análisis de los comentarios de los clientes en busca de tendencias y oportunidades para informar la hoja de ruta del producto
En resumen
Si solo utilizan prompts genéricos o una IA que no está vinculada a los datos de su lugar de trabajo, se pierden las mayores ventajas de la tecnología. La IA es mucho más poderosa cuando tiene conocimiento sobre su rol, su equipo y su negocio. Eso es algo que deben tener en cuenta a medida que continúan sus exploraciones de IA en el próximo año.
Para obtener más información sobre la IA y el futuro del trabajo, suscríbanse a este boletín.
AWS CloudFormation introduces a new capability called stack refactoring that makes it easy to reorganize cloud resources across your CloudFormation stacks. Stack refactoring enables you to move resources from one stack to another, split monolithic stacks into smaller components, and rename the logical name of resources within a stack. This enables you to adapt your stacks to meet architectural patterns, operational needs, or business requirements.
As your workloads scale and requirements evolve, re-architecting resources into a new stack structure can become necessary. For example, you may need to split a monolithic stack for easier resource lifecycle management or rename resource logical IDs to align with new naming conventions. Previously, refactoring a stack required multiple manual steps, such as updating templates to retain targeted resources, removing them from current stacks, and then importing them into new stacks. Stack refactoring improves the speed and safety of this process. To refactor a stack, you first provide the CloudFormation templates that reflect the desired stack structure. Then, you generate a preview of the refactor operation, allowing you to confirm that the refactoring changes align with your requirements. If the planned changes meet your expectations, you can execute the refactor operation through an atomic workflow. This new capability enables seamless and continuous adaptation to evolving architectural patterns.
Stack refactor is available in all AWS Regions where CloudFormation is supported. To get started, update your CloudFormation templates to reflect the desired stack structure, then use the AWS CLI or SDK to perform the refactor operation. Visit our user guide to learn more about this feature.
AWS CloudFormation introduces a new capability called stack refactoring that makes it easy to reorganize cloud resources across your CloudFormation stacks. Stack refactoring enables you to move resources from one stack to another, split monolithic stacks into smaller components, and rename the logical name of resources within a stack. This enables you to adapt your stacks to meet architectural patterns, operational needs, or business requirements. As your workloads scale and requirements evolve, re-architecting resources into a new stack structure can become necessary. For example, you may need to split a monolithic stack for easier resource lifecycle management or rename resource logical IDs to align with new naming conventions. Previously, refactoring a stack required multiple manual steps, such as updating templates to retain targeted resources, removing them from current stacks, and then importing them into new stacks. Stack refactoring improves the speed and safety of this process. To refactor a stack, you first provide the CloudFormation templates that reflect the desired stack structure. Then, you generate a preview of the refactor operation, allowing you to confirm that the refactoring changes align with your requirements. If the planned changes meet your expectations, you can execute the refactor operation through an atomic workflow. This new capability enables seamless and continuous adaptation to evolving architectural patterns. Stack refactor is available in all AWS Regions where CloudFormation is supported. To get started, update your CloudFormation templates to reflect the desired stack structure, then use the AWS CLI or SDK to perform the refactor operation. Visit our user guide to learn more about this feature.
Amazon Personalize introduces dual stack support for the Personalize API endpoints, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when you privately access the Personalize API endpoint from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink.
The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on Personalize endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to help meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6.
Support for IPv6 on Amazon Personalize in all supported regions. To learn more on best practices for configuring IPv6, see the whitepaper on IPv6 in AWS.
Amazon Personalize introduces dual stack support for the Personalize API endpoints, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when you privately access the Personalize API endpoint from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink. The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on Personalize endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to help meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6. Support for IPv6 on Amazon Personalize in all supported regions. To learn more on best practices for configuring IPv6, see the whitepaper on IPv6 in AWS.
Amazon MSK has added support for Express brokers in all AWS Regions where Amazon MSK offers Graviton3 based M7g instances. You can now benefit from Amazon MSK Express brokers in ten additional AWS Regions: Asia Pacific (Mumbai), Europe (Paris), South America (Sao Paulo), Asia Pacific (Hyderabad), Asia Pacific (Seoul), Asia Pacific (Malaysia), Europe (London), Canada (Central), Europe (Spain), and Middle East (Bahrain).
Express brokers are a new broker type for Amazon MSK Provisioned designed to deliver up to 3x more throughput per broker, scale up to 20x faster, and reduce recovery time by 90% as compared to standard Apache Kafka brokers. Express brokers come pre-configured with Kafka best practices by default, support all Kafka APIs, and provide the same low-latency performance that Amazon MSK customers expect, so they can continue using existing client applications without any changes.
You can now create an MSK cluster with Express brokers in these AWS Regions from the Amazon MSK console. To learn more, check out this blog.
Amazon MSK has added support for Express brokers in all AWS Regions where Amazon MSK offers Graviton3 based M7g instances. You can now benefit from Amazon MSK Express brokers in ten additional AWS Regions: Asia Pacific (Mumbai), Europe (Paris), South America (Sao Paulo), Asia Pacific (Hyderabad), Asia Pacific (Seoul), Asia Pacific (Malaysia), Europe (London), Canada (Central), Europe (Spain), and Middle East (Bahrain). Express brokers are a new broker type for Amazon MSK Provisioned designed to deliver up to 3x more throughput per broker, scale up to 20x faster, and reduce recovery time by 90% as compared to standard Apache Kafka brokers. Express brokers come pre-configured with Kafka best practices by default, support all Kafka APIs, and provide the same low-latency performance that Amazon MSK customers expect, so they can continue using existing client applications without any changes. You can now create an MSK cluster with Express brokers in these AWS Regions from the Amazon MSK console. To learn more, check out this blog.
Cost Optimization Hub now supports idle EC2 Auto Scaling group recommendations and rightsizing recommendations for EC2 Auto Scaling groups with scaling policies and multiple instance types. It also allows you to easily filter and aggregate EC2 Auto Scaling group cost optimization opportunities separately from standalone EC2 instances, making it easier to identify EC2 Auto Scaling groups with the highest cost-saving opportunities.
With this launch, you can view, consolidate, and prioritize cost optimization opportunities for EC2 Auto Scaling groups across your organization’s member accounts and AWS Regions through a single dashboard. Cost Optimization Hub helps you quantify estimated savings from these recommendations, taking into account your specific discounts, such as Reserved Instances and Savings Plans, enabling you to easily compare and prioritize recommendations.
The new EC2 Auto Scaling group experience and recommendations are available in Cost Optimization Hub across all AWS Regions where Cost Optimization Hub and AWS Organizations are supported.
Cost Optimization Hub now supports idle EC2 Auto Scaling group recommendations and rightsizing recommendations for EC2 Auto Scaling groups with scaling policies and multiple instance types. It also allows you to easily filter and aggregate EC2 Auto Scaling group cost optimization opportunities separately from standalone EC2 instances, making it easier to identify EC2 Auto Scaling groups with the highest cost-saving opportunities.
With this launch, you can view, consolidate, and prioritize cost optimization opportunities for EC2 Auto Scaling groups across your organization’s member accounts and AWS Regions through a single dashboard. Cost Optimization Hub helps you quantify estimated savings from these recommendations, taking into account your specific discounts, such as Reserved Instances and Savings Plans, enabling you to easily compare and prioritize recommendations.
The new EC2 Auto Scaling group experience and recommendations are available in Cost Optimization Hub across all AWS Regions where Cost Optimization Hub and AWS Organizations are supported.
AWS WAF’s console dashboard now includes richer visualizations that give you insights into the top sources of traffic in the AWS GovCloud (US). With this feature, customers with CloudWatch logging destinations can view a new top insights section within the all traffic dashboard.
Customers previously used the all traffic dashboard, a default dashboard that populates visualizations based on CloudWatch metrics. As customers strive to continue gaining additional visibility into their traffic, they have requested richer visualizations based on logs in addition to visualizations based on CloudWatch metrics.
Starting today, customers with CloudWatch logging destinations will have access to this new top insights section within the all traffic dashboard, which includes richer visualizations based on terminating rules, client IPs, URI path, and more. These top insights will enable customers to better understand their security posture, quickly identify anomalies, and optimize their WAF configurations accordingly. For example, if a customer sees more than expected traffic from an suspicious IP address, they can take steps to create a IP-blocking rule to address this anomaly.
Standard CloudWatch pricing applies to metrics and logs queried through the dashboard. For more information about pricing, visit the AWS CloudWatch Pricing page. The feature is now available in the AWS GovCloud (US) for all origin types supported by WAF. For more information about the all traffic dashboard, visit the Developer Guide.
AWS WAF’s console dashboard now includes richer visualizations that give you insights into the top sources of traffic in the AWS GovCloud (US). With this feature, customers with CloudWatch logging destinations can view a new top insights section within the all traffic dashboard. Customers previously used the all traffic dashboard, a default dashboard that populates visualizations based on CloudWatch metrics. As customers strive to continue gaining additional visibility into their traffic, they have requested richer visualizations based on logs in addition to visualizations based on CloudWatch metrics. Starting today, customers with CloudWatch logging destinations will have access to this new top insights section within the all traffic dashboard, which includes richer visualizations based on terminating rules, client IPs, URI path, and more. These top insights will enable customers to better understand their security posture, quickly identify anomalies, and optimize their WAF configurations accordingly. For example, if a customer sees more than expected traffic from an suspicious IP address, they can take steps to create a IP-blocking rule to address this anomaly. Standard CloudWatch pricing applies to metrics and logs queried through the dashboard. For more information about pricing, visit the AWS CloudWatch Pricing page. The feature is now available in the AWS GovCloud (US) for all origin types supported by WAF. For more information about the all traffic dashboard, visit the Developer Guide.
AWS IAM Identity Center now provides improved error messages to simplify troubleshooting when syncing users and groups. You can also build automated monitoring and auditing for these errors using the AWS CloudTrail logs.
IAM Identity Center helps you securely connect your workforce identities and manage their access centrally across AWS accounts and applications. With improved error messaging, IAM Identity Center provides actionable information to troubleshoot provisioning issues as you sync your users and groups using SCIM or configurable AD sync. CloudTrail logs enable automated monitoring of synchronization processes and provide audit trails of provisioning issues.
AWS IAM Identity Center now provides improved error messages to simplify troubleshooting when syncing users and groups. You can also build automated monitoring and auditing for these errors using the AWS CloudTrail logs. IAM Identity Center helps you securely connect your workforce identities and manage their access centrally across AWS accounts and applications. With improved error messaging, IAM Identity Center provides actionable information to troubleshoot provisioning issues as you sync your users and groups using SCIM or configurable AD sync. CloudTrail logs enable automated monitoring of synchronization processes and provide audit trails of provisioning issues. IAM Identity Center is available at no additional cost in all AWS Regions where it is supported. To learn more, see the AWS IAM Identity Center User Guide.
