AWS Glue Data Catalog now supports external catalog’s vended credentials in Apache Iceberg REST catalog federation. You can now read external Iceberg tables from Amazon Athena, Amazon EMR, Amazon Redshift, and AWS Glue using coarse-grained table grants in your external Iceberg catalog.

Glue Data Catalog already federates to external Iceberg REST catalogs through an AWS IAM role that you configure with access to your Amazon S3 buckets. This enhancement in Glue Data Catalog provides another way to connect to an external Iceberg catalog and read only the tables that the external catalog authorizes. It uses temporary security credentials that are scoped to the Amazon S3 storage prefix and vended by your external Iceberg catalog. AWS Lake Formation manages access control when you query an external table using any AWS analytics engine, letting you restrict access further down to specific rows and columns and share external Iceberg tables across AWS accounts.

This feature is available through the AWS Lake Formation Management Console, AWS CLI, and the AWS Glue and Lake Formation SDKs. This feature is available in all commercial AWS Regions where Glue and Lake Formation are supported. To learn more, visit the documentation.

 

​AWS Glue Data Catalog now supports external catalog’s vended credentials in Apache Iceberg REST catalog federation. You can now read external Iceberg tables from Amazon Athena, Amazon EMR, Amazon Redshift, and AWS Glue using coarse-grained table grants in your external Iceberg catalog.
Glue Data Catalog already federates to external Iceberg REST catalogs through an AWS IAM role that you configure with access to your Amazon S3 buckets. This enhancement in Glue Data Catalog provides another way to connect to an external Iceberg catalog and read only the tables that the external catalog authorizes. It uses temporary security credentials that are scoped to the Amazon S3 storage prefix and vended by your external Iceberg catalog. AWS Lake Formation manages access control when you query an external table using any AWS analytics engine, letting you restrict access further down to specific rows and columns and share external Iceberg tables across AWS accounts.
This feature is available through the AWS Lake Formation Management Console, AWS CLI, and the AWS Glue and Lake Formation SDKs. This feature is available in all commercial AWS Regions where Glue and Lake Formation are supported. To learn more, visit the documentation.  

Amazon Simple Email Service (Amazon SES)  is now available in the Asia Pacific (New Zealand, Melbourne, Taipei, Thailand), Mexico (Central), EU (Spain). Customers can now use these new Regions to leverage Amazon SES to send emails and, if needed, to help manage data requirements.

Amazon SES is a scalable, cost-effective, and flexible cloud-based email service that allows digital marketers and application developers to send marketing, notification, and transactional emails from within any application. To learn more about Amazon SES, visit this page .

With this launch, Amazon SES is available in 35 AWS Regions globally: US East (N. Virginia, Ohio), US West (N. California, Oregon), AWS GovCloud (US-West, US-East), Asia Pacific (Osaka, Mumbai, Hyderabad, Sydney, Singapore, Seoul, Tokyo, Jakarta, Malaysia, New Zealand, Melbourne, Taipei, Thailand), Canada (Central, Calgary), EU (Ireland, Frankfurt, London, Paris, Stockholm, Milan, Zurich,Spain), Middle East (Bahrain, UAE), Israel (Tel Aviv), South America (Sao Paulo), Mexico (Central) and Africa (Cape Town).

For a complete list of all of the regional endpoints for Amazon SES, see  AWS Service Endpoints  in the AWS General Reference.

 

​Amazon Simple Email Service (Amazon SES)  is now available in the Asia Pacific (New Zealand, Melbourne, Taipei, Thailand), Mexico (Central), EU (Spain). Customers can now use these new Regions to leverage Amazon SES to send emails and, if needed, to help manage data requirements.
Amazon SES is a scalable, cost-effective, and flexible cloud-based email service that allows digital marketers and application developers to send marketing, notification, and transactional emails from within any application. To learn more about Amazon SES, visit this page .
With this launch, Amazon SES is available in 35 AWS Regions globally: US East (N. Virginia, Ohio), US West (N. California, Oregon), AWS GovCloud (US-West, US-East), Asia Pacific (Osaka, Mumbai, Hyderabad, Sydney, Singapore, Seoul, Tokyo, Jakarta, Malaysia, New Zealand, Melbourne, Taipei, Thailand), Canada (Central, Calgary), EU (Ireland, Frankfurt, London, Paris, Stockholm, Milan, Zurich,Spain), Middle East (Bahrain, UAE), Israel (Tel Aviv), South America (Sao Paulo), Mexico (Central) and Africa (Cape Town).
For a complete list of all of the regional endpoints for Amazon SES, see  AWS Service Endpoints  in the AWS General Reference.  

Starting today, you can add Amazon EC2 Capacity Blocks for ML and interruptible Capacity Reservations to Capacity Reservation Resource Groups in AWS GovCloud (US) Regions. Amazon EC2 offers different reservation offerings such as On-Demand Capacity Reservations (ODCRs), interruptible Capacity Reservations, and Capacity Blocks for ML. Previously, a Capacity Reservation Resource Group could only include ODCRs. Now you can add any type of Capacity Reservation to a Capacity Reservation Resource Group, making it easier to launch EC2 instances across your entire portfolio of reserved capacity.

To use this feature, create a Capacity Reservation Resource Group, add any Capacity Reservation to it, and then target the group in your launch request. When using EC2 Fleet and EC2 Auto Scaling groups, you can also specify your prioritization preferences across reservation types, and configure automatic fall back to EC2 On-Demand capacity when there is no capacity remaining across your reservations.

There are no additional charges for using this feature. With the addition of AWS GovCloud (US) Regions, this feature is now available in all AWS Regions where Capacity Blocks for ML and interruptible ODCRs are supported, excluding China Regions. To get started, see Capacity Reservation Resource Groups and the Capacity Reservations user guide.

 

​Starting today, you can add Amazon EC2 Capacity Blocks for ML and interruptible Capacity Reservations to Capacity Reservation Resource Groups in AWS GovCloud (US) Regions. Amazon EC2 offers different reservation offerings such as On-Demand Capacity Reservations (ODCRs), interruptible Capacity Reservations, and Capacity Blocks for ML. Previously, a Capacity Reservation Resource Group could only include ODCRs. Now you can add any type of Capacity Reservation to a Capacity Reservation Resource Group, making it easier to launch EC2 instances across your entire portfolio of reserved capacity.
To use this feature, create a Capacity Reservation Resource Group, add any Capacity Reservation to it, and then target the group in your launch request. When using EC2 Fleet and EC2 Auto Scaling groups, you can also specify your prioritization preferences across reservation types, and configure automatic fall back to EC2 On-Demand capacity when there is no capacity remaining across your reservations.
There are no additional charges for using this feature. With the addition of AWS GovCloud (US) Regions, this feature is now available in all AWS Regions where Capacity Blocks for ML and interruptible ODCRs are supported, excluding China Regions. To get started, see Capacity Reservation Resource Groups and the Capacity Reservations user guide.  

Today, AWS announces that AWS Security Hub now provides a Software Bill of Materials (SBOM) inventory, giving central security teams a continuously updated, organization-wide view of the software packages and applications installed on their compute resources.

Security Hub builds the inventory from the SBOMs that Amazon Inspector generates for Amazon EC2 instances, Amazon ECR container images, and AWS Lambda functions, with no additional configuration. The SBOM page lists each package with its version, type, and the number of resources where it is installed. You can filter and group the list by package attributes, account, and region. On the resource detail page, the Installed software tab lists every package on that resource, so you can judge its function and criticality while triaging any finding. You can also query the inventory through the Security Hub API.

The SBOM inventory is included with Security Hub Essentials at no additional cost. It requires no new enablement and populates automatically where Amazon Inspector is enabled. It is available in all AWS Regions where Security Hub is available. To learn more, see the AWS Security Hub User Guide and the AWS Security Hub product page.

 

​Today, AWS announces that AWS Security Hub now provides a Software Bill of Materials (SBOM) inventory, giving central security teams a continuously updated, organization-wide view of the software packages and applications installed on their compute resources.
Security Hub builds the inventory from the SBOMs that Amazon Inspector generates for Amazon EC2 instances, Amazon ECR container images, and AWS Lambda functions, with no additional configuration. The SBOM page lists each package with its version, type, and the number of resources where it is installed. You can filter and group the list by package attributes, account, and region. On the resource detail page, the Installed software tab lists every package on that resource, so you can judge its function and criticality while triaging any finding. You can also query the inventory through the Security Hub API.
The SBOM inventory is included with Security Hub Essentials at no additional cost. It requires no new enablement and populates automatically where Amazon Inspector is enabled. It is available in all AWS Regions where Security Hub is available. To learn more, see the AWS Security Hub User Guide and the AWS Security Hub product page.  

AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a). AWS Local Zones is a type of AWS infrastructure deployment that places AWS compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists today.

With this launch, you can create an AWS Network Load Balancer directly in the Phoenix Local Zone. Previously, if your targets ran in the Phoenix Local Zone, you had to place the load balancer in an Availability Zone in the parent Region, so connections and their traffic had to travel to the parent Region and back. This added latency and routed traffic outside the zone where your application runs. Now, connection routing stays local to your targets, delivering lower and more consistent latency to end users in the Phoenix metro area and keeping traffic within the Local Zone. This is especially valuable for latency-sensitive workloads such as real-time gaming, media streaming, and live financial applications serving users in the region.

To learn more about Network Load Balancer, visit the documentation. For more information on AWS Local Zones, visit the AWS Local Zones website. The Locations webpage lists the available and announced Local Zones. You can enable AWS Local Zones from the Local Zones tab in the AWS Global View console, or the ModifyAvailabilityZoneGroup API.

 

​AWS Network Load Balancer is now available in the Phoenix Local Zone (us-west-2-phx-2a). AWS Local Zones is a type of AWS infrastructure deployment that places AWS compute, storage, database, and other select services closer to large population, industry, and IT centers where no AWS Region exists today.
With this launch, you can create an AWS Network Load Balancer directly in the Phoenix Local Zone. Previously, if your targets ran in the Phoenix Local Zone, you had to place the load balancer in an Availability Zone in the parent Region, so connections and their traffic had to travel to the parent Region and back. This added latency and routed traffic outside the zone where your application runs. Now, connection routing stays local to your targets, delivering lower and more consistent latency to end users in the Phoenix metro area and keeping traffic within the Local Zone. This is especially valuable for latency-sensitive workloads such as real-time gaming, media streaming, and live financial applications serving users in the region.
To learn more about Network Load Balancer, visit the documentation. For more information on AWS Local Zones, visit the AWS Local Zones website. The Locations webpage lists the available and announced Local Zones. You can enable AWS Local Zones from the Local Zones tab in the AWS Global View console, or the ModifyAvailabilityZoneGroup API.  

Today, AWS announced a new AWS Interconnect – last mile metro in Northern Virginia, USA. Northern Virginia joins New York as the second metro where you can connect your data center, branch office, or colocation facility to AWS. 

AWS Interconnect – last mile gives you managed, private, resilient connections to AWS, so you don’t have to order cross-connects or configure routers. Every connection is provisioned by default across two physically diverse locations with four redundant links, providing maximum resilience out of the box and backed by a 99.99% availability SLA up to the Direct Connect port. Traffic between AWS and partner edge devices is encrypted with MACsec by default.

Lumen customers anywhere in the continental United States can order generally available connections through the Northern Virginia metro to reach all public AWS Regions (except those in China) and AWS Local Zones. AWS Interconnect – last mile is also available in preview through Megaport and Equinix in the Northern Virginia metro. You can create connections using the AWS Management Console, AWS CLI, or AWS Interconnect API. For pricing, see AWS Interconnect – last mile pricing.

 

​Today, AWS announced a new AWS Interconnect – last mile metro in Northern Virginia, USA. Northern Virginia joins New York as the second metro where you can connect your data center, branch office, or colocation facility to AWS. 
AWS Interconnect – last mile gives you managed, private, resilient connections to AWS, so you don’t have to order cross-connects or configure routers. Every connection is provisioned by default across two physically diverse locations with four redundant links, providing maximum resilience out of the box and backed by a 99.99% availability SLA up to the Direct Connect port. Traffic between AWS and partner edge devices is encrypted with MACsec by default.
Lumen customers anywhere in the continental United States can order generally available connections through the Northern Virginia metro to reach all public AWS Regions (except those in China) and AWS Local Zones. AWS Interconnect – last mile is also available in preview through Megaport and Equinix in the Northern Virginia metro. You can create connections using the AWS Management Console, AWS CLI, or AWS Interconnect API. For pricing, see AWS Interconnect – last mile pricing.  

Today, we are announcing the general availability of Web Answer on Amazon Bedrock AgentCore. Web Answer is a managed tool that returns a synthesized, grounded, cited answer to a natural-language question in a single call, so agent builders can attach it to an agent and get back a finished answer grounded in current web sources, without building and maintaining their own search, retrieve, synthesis, and citation pipeline. 

Web Answer builds on Web Search on Amazon Bedrock AgentCore, which launched in June, extending it from «find the web content» to «return the finished answer,» a capability customers have been asking for. With Web Answer, your agent sends a question and receives a synthesized cited answer in one tool call. Web Answer works like an agent; it plans its own searches, runs several in parallel, and decides when it has gathered enough evidence to answer. You stay in control of the boundaries, with domain include, deny lists and publish-date filters that scope where it looks. It attaches as a target on an AgentCore Gateway and is called over MCP, authenticated with IAM, with zero data egress. 

Web Answer is available in the US East (N. Virginia) Region, with per-tool call pricing. 

To learn more about Web Answer on Amazon Bedrock AgentCore, see Web Answer’s documentation page and Web Answer’s website. For Region availability, see the AWS Region table. 

 

​Today, we are announcing the general availability of Web Answer on Amazon Bedrock AgentCore. Web Answer is a managed tool that returns a synthesized, grounded, cited answer to a natural-language question in a single call, so agent builders can attach it to an agent and get back a finished answer grounded in current web sources, without building and maintaining their own search, retrieve, synthesis, and citation pipeline. 
Web Answer builds on Web Search on Amazon Bedrock AgentCore, which launched in June, extending it from «find the web content» to «return the finished answer,» a capability customers have been asking for. With Web Answer, your agent sends a question and receives a synthesized cited answer in one tool call. Web Answer works like an agent; it plans its own searches, runs several in parallel, and decides when it has gathered enough evidence to answer. You stay in control of the boundaries, with domain include, deny lists and publish-date filters that scope where it looks. It attaches as a target on an AgentCore Gateway and is called over MCP, authenticated with IAM, with zero data egress. 
Web Answer is available in the US East (N. Virginia) Region, with per-tool call pricing. 
To learn more about Web Answer on Amazon Bedrock AgentCore, see Web Answer’s documentation page and Web Answer’s website. For Region availability, see the AWS Region table.   

Volver a la Esencia: enfocarse en las decisiones que importan

La inteligencia artificial (IA) redefine la manera en que trabajamos, colaboramos y tomamos decisiones. En medio de esta transformación, la serie Volver a la Esencia reúne las reflexiones de líderes de distintos sectores sobre un desafío común: aprovechar el potencial de la IA sin perder de vista aquello que da sentido a nuestro trabajo. Porque, más allá de la tecnología, el futuro de las profesiones dependerá todavía de las personas, de su criterio y de su responsabilidad para organizar el trabajo.

El criterio sigue siendo humano

En esta segunda entrega, Gustavo Pérez Villar, Secretario de Tecnología Informática en la Suprema Corte de Justicia en Argentina, reflexiona sobre cómo la tecnología y la inteligencia artificial pueden ayudar a los profesionales a enfocarse en aquello que en verdad define su trabajo: las decisiones que requieren juicio, análisis y responsabilidad.

Desde su experiencia en el ámbito judicial, explica que gran parte de la actividad diaria de un juzgado está asociada a tareas operativas y administrativas que consumen tiempo y atención. Al delegar parte de estos procesos en herramientas tecnológicas e inteligencia artificial, los jueces pueden concentrarse en la labor que constituye la esencia de su función: analizar los conflictos, ponderar sus implicaciones y emitir resoluciones que impactan directamente en la vida de las personas.

Su reflexión trasciende el ámbito de la justicia. En cualquier profesión, la tecnología puede ayudar a simplificar procesos y reducir la carga operativa, pero las decisiones más importantes aun requieren de experiencia, discernimiento y una comprensión profunda de las consecuencias de cada acción.

Para Gustavo, volver a la esencia significa justo eso, recuperar el foco en aquello que genera valor y preservar una cualidad imprescindible para cualquier profesional: la curiosidad. Porque, en un entorno de cambio permanente, seguir aprendiendo es también una manera de mantener vigente el propósito de nuestro trabajo.

Etiquetas:

• Clientes
• IA
• Transformación Digital

Click here to load media

The post Volver a la Esencia: enfocarse en las decisiones que importan appeared first on Source LATAM.

 

​The post Volver a la Esencia: enfocarse en las decisiones que importan appeared first on Source LATAM.  

Today, AWS announces the general availability of bulk put items for Amazon DynamoDB, a fully managed feature that writes data from Amazon S3 into your existing DynamoDB tables. Many DynamoDB applications use data that other systems produce and store in Amazon S3. Writing this data into existing DynamoDB tables has typically meant building custom pipelines and managing table capacity. With bulk put items, developers and data engineers can write this data without impacting existing workloads or building a custom ingestion pipeline, in a cost-efficient way.

You point bulk put items at the S3 location of your input files, and DynamoDB handles the rest. Each item supports its own condition expression, so you can enforce insert-only or version-guarded writes. The Standard tier fits most workloads, and the Accelerated tier is for more time-sensitive workloads. Common use cases include daily refreshes, large catalog enrichments, backfills, and migrations.

Bulk put items with Standard tier is available in all commercial AWS Regions and the AWS GovCloud (US) Regions, to see the list where the Accelerated tier is available see the regional availability. To learn more, visit the Introducing bulk put items for Amazon DynamoDB blog and the Amazon DynamoDB Developer Guide.

 

​Today, AWS announces the general availability of bulk put items for Amazon DynamoDB, a fully managed feature that writes data from Amazon S3 into your existing DynamoDB tables. Many DynamoDB applications use data that other systems produce and store in Amazon S3. Writing this data into existing DynamoDB tables has typically meant building custom pipelines and managing table capacity. With bulk put items, developers and data engineers can write this data without impacting existing workloads or building a custom ingestion pipeline, in a cost-efficient way.
You point bulk put items at the S3 location of your input files, and DynamoDB handles the rest. Each item supports its own condition expression, so you can enforce insert-only or version-guarded writes. The Standard tier fits most workloads, and the Accelerated tier is for more time-sensitive workloads. Common use cases include daily refreshes, large catalog enrichments, backfills, and migrations.
Bulk put items with Standard tier is available in all commercial AWS Regions and the AWS GovCloud (US) Regions, to see the list where the Accelerated tier is available see the regional availability. To learn more, visit the Introducing bulk put items for Amazon DynamoDB blog and the Amazon DynamoDB Developer Guide.  

Amazon Managed Workflows for Apache Airflow (Amazon MWAA) now supports cost allocation tags. Tags you apply to an Amazon MWAA environment now propagate to the compute that runs it, including workers, schedulers, and web servers. You can then track Amazon MWAA spend by tag in AWS Cost Explorer and AWS Cost and Usage Reports.

With this launch, platform teams can show back or charge back Airflow costs to the team, project, or cost center that owns each environment. You can use cost allocation tags when you create a new environment or update an existing one. To get started, tag your environment using the Amazon MWAA console, AWS CLI, or Amazon MWAA API, then activate the tag key as a cost allocation tag in the AWS Billing and Cost Management console.

This feature is available in all AWS Regions where Amazon MWAA is available. For more information, see the AWS Region table. To learn more, visit Cost allocation tags in Amazon MWAA in the Amazon MWAA User Guide.

 

​Amazon Managed Workflows for Apache Airflow (Amazon MWAA) now supports cost allocation tags. Tags you apply to an Amazon MWAA environment now propagate to the compute that runs it, including workers, schedulers, and web servers. You can then track Amazon MWAA spend by tag in AWS Cost Explorer and AWS Cost and Usage Reports.
With this launch, platform teams can show back or charge back Airflow costs to the team, project, or cost center that owns each environment. You can use cost allocation tags when you create a new environment or update an existing one. To get started, tag your environment using the Amazon MWAA console, AWS CLI, or Amazon MWAA API, then activate the tag key as a cost allocation tag in the AWS Billing and Cost Management console.
This feature is available in all AWS Regions where Amazon MWAA is available. For more information, see the AWS Region table. To learn more, visit Cost allocation tags in Amazon MWAA in the Amazon MWAA User Guide.