AWS Site-to-Site VPN, a fully managed service that allows you to create a secure connection between your data center or branch office and your AWS resources using IP Security (IPSec) tunnels, is adding three new capabilities for enhanced security and ease of configuration.

• AWS Secrets Manager Integration: With the AWS Secrets Manager integration, when customers store their pre-shared keys (PSKs) in Secrets Manager, VPN connection API responses will redact the PSK and instead display the Secrets Manager ARN (Amazon Resource Name), providing enhanced security.
• New API to track VPN algorithms: You can now easily track the currently negotiated internet key exchange (IKE) version, Diffie-Hellman (DH) groups, encryption algorithms, and integrity algorithms using the “GetActiveVpnTunnelStatus” API. This new API eliminates the need for you to enable Site-to-Site VPN logs to get this information, saving time and reducing operational overhead.
• Recommended Configuration: “GetVpnConnectionDeviceSampleConfiguration” API now includes “recommended” parameter to help you use the best-practices security configuration – IKE version 2, DH group 20, SHA-384 integrity algorithm, and AES-GCM-256 encryption algorithm – on your customer gateway devices, reducing configuration time and potential errors.

There is no additional charge for using these capabilities. These capabilities are available in all AWS commercial Regions where AWS Site-to-Site VPN is available, except Europe (Milan) Region. To learn more and get started, visit the AWS Site-to-Site VPN documentation.

​AWS Site-to-Site VPN, a fully managed service that allows you to create a secure connection between your data center or branch office and your AWS resources using IP Security (IPSec) tunnels, is adding three new capabilities for enhanced security and ease of configuration.

AWS Secrets Manager Integration: With the AWS Secrets Manager integration, when customers store their pre-shared keys (PSKs) in Secrets Manager, VPN connection API responses will redact the PSK and instead display the Secrets Manager ARN (Amazon Resource Name), providing enhanced security.
New API to track VPN algorithms: You can now easily track the currently negotiated internet key exchange (IKE) version, Diffie-Hellman (DH) groups, encryption algorithms, and integrity algorithms using the “GetActiveVpnTunnelStatus” API. This new API eliminates the need for you to enable Site-to-Site VPN logs to get this information, saving time and reducing operational overhead.
Recommended Configuration: “GetVpnConnectionDeviceSampleConfiguration” API now includes “recommended” parameter to help you use the best-practices security configuration – IKE version 2, DH group 20, SHA-384 integrity algorithm, and AES-GCM-256 encryption algorithm – on your customer gateway devices, reducing configuration time and potential errors.

There is no additional charge for using these capabilities. These capabilities are available in all AWS commercial Regions where AWS Site-to-Site VPN is available, except Europe (Milan) Region. To learn more and get started, visit the AWS Site-to-Site VPN documentation.  

Amazon Athena announces managed query results, a new feature that automatically stores, encrypts, and manages the lifecycle of query results for you at no additional cost. Managed query results streamlines analysis and administration workflows by providing temporary query results storage, removing the requirement for Amazon S3 buckets to store results and separate processes to clean up results that you no longer need. Now, Athena offers both service-managed, temporary result storage and customer-managed S3 storage options to meet different needs.

Whether you’re working on a team conducting interactive analysis across multiple workgroups or automating workgroup creation through code, managed query results allows you to run queries in fewer steps. For example, if you create a new workgroup for an analysis that you’ll perform, you can now choose to have Athena manage your result data for you. This allows you to run queries without first specifying the S3 result location, ensures results are encrypted, and avoids cost from storing query results after they’re no longer needed. When you use managed query results, you can continue to access query results through the same interfaces as you can when using an S3 bucket in your account.

To get started, use the AWS Management Console, AWS SDK, or CLI to configure your new or existing workgroups to use managed query results.

Managed query results is generally available in all regions where Athena is available, except GovCloud and China regions. To learn more, see Managed query results in the Athena User Guide.

​Amazon Athena announces managed query results, a new feature that automatically stores, encrypts, and manages the lifecycle of query results for you at no additional cost. Managed query results streamlines analysis and administration workflows by providing temporary query results storage, removing the requirement for Amazon S3 buckets to store results and separate processes to clean up results that you no longer need. Now, Athena offers both service-managed, temporary result storage and customer-managed S3 storage options to meet different needs. Whether you’re working on a team conducting interactive analysis across multiple workgroups or automating workgroup creation through code, managed query results allows you to run queries in fewer steps. For example, if you create a new workgroup for an analysis that you’ll perform, you can now choose to have Athena manage your result data for you. This allows you to run queries without first specifying the S3 result location, ensures results are encrypted, and avoids cost from storing query results after they’re no longer needed. When you use managed query results, you can continue to access query results through the same interfaces as you can when using an S3 bucket in your account. To get started, use the AWS Management Console, AWS SDK, or CLI to configure your new or existing workgroups to use managed query results. Managed query results is generally available in all regions where Athena is available, except GovCloud and China regions. To learn more, see Managed query results in the Athena User Guide.  

Amazon API Gateway now supports routing rules for REST APIs using custom domain names. This new capability enables you to dynamically route incoming requests based on HTTP header values, URL base paths, or a combination of both.

This flexibility enables various use cases, including A/B testing, API versioning, and dynamic backend selection. To use this feature, you define routing rules by assigning priorities, defining conditions (HTTP headers, URL paths, or both), and associating actions. API Gateway then evaluates these rules in priority order with lower numbers taking precedence. When a request meets all conditions in a rule, API Gateway routes it to the configured REST API ID and stage. By implementing routing logic directly within API Gateway, you can eliminate proxy layers and complex URL structures while maintaining granular routing control over your API traffic. This feature is supported on both public and private REST APIs and is compatible with existing API mappings.

Routing rules for custom domain names are available in all AWS Regions, including the AWS GovCloud (US) Regions. To learn more, please refer to the blogpost and the API Gateway documentation.
 

​Amazon API Gateway now supports routing rules for REST APIs using custom domain names. This new capability enables you to dynamically route incoming requests based on HTTP header values, URL base paths, or a combination of both. This flexibility enables various use cases, including A/B testing, API versioning, and dynamic backend selection. To use this feature, you define routing rules by assigning priorities, defining conditions (HTTP headers, URL paths, or both), and associating actions. API Gateway then evaluates these rules in priority order with lower numbers taking precedence. When a request meets all conditions in a rule, API Gateway routes it to the configured REST API ID and stage. By implementing routing logic directly within API Gateway, you can eliminate proxy layers and complex URL structures while maintaining granular routing control over your API traffic. This feature is supported on both public and private REST APIs and is compatible with existing API mappings. Routing rules for custom domain names are available in all AWS Regions, including the AWS GovCloud (US) Regions. To learn more, please refer to the blogpost and the API Gateway documentation.    

Today, AWS Backup announces the addition of notification support for backup indexes in AWS Backup. You can now subscribe to Amazon SNS notifications and Amazon EventBridge events for backup indexing, allowing you to proactively monitor the status of your backup indexes. You can now receive notifications when a backup index is created, deleted, or fails to create, enhancing your ability to monitor and track your backup operations.

To get started, you can subscribe to SNS notifications or create a rule in EventBridge. Once opted in, you will receive notifications on the status of your backup index, including when it is created, deleted or failed to create. This is valuable, as backup indexes are a pre-requisite to the search metadata of your backups and conduct file-level item restores.
Prepare for potential data loss events by knowing when your backup indexes are created as it expedites search and recovery granular data if needed.

AWS Backup support for notification backup indexes is available in all AWS Commercial and AWS GovCloud (US) Regions, where AWS Backup indexes, Amazon SNS, and Amazon EventBridge are supported are available. You can get started by using the User Notifications Console or CLI and Amazon EventBridge Console or CLI. For more information, visit our documentation.
 

​Today, AWS Backup announces the addition of notification support for backup indexes in AWS Backup. You can now subscribe to Amazon SNS notifications and Amazon EventBridge events for backup indexing, allowing you to proactively monitor the status of your backup indexes. You can now receive notifications when a backup index is created, deleted, or fails to create, enhancing your ability to monitor and track your backup operations. To get started, you can subscribe to SNS notifications or create a rule in EventBridge. Once opted in, you will receive notifications on the status of your backup index, including when it is created, deleted or failed to create. This is valuable, as backup indexes are a pre-requisite to the search metadata of your backups and conduct file-level item restores. Prepare for potential data loss events by knowing when your backup indexes are created as it expedites search and recovery granular data if needed. AWS Backup support for notification backup indexes is available in all AWS Commercial and AWS GovCloud (US) Regions, where AWS Backup indexes, Amazon SNS, and Amazon EventBridge are supported are available. You can get started by using the User Notifications Console or CLI and Amazon EventBridge Console or CLI. For more information, visit our documentation.    

Amazon Managed Service for Apache Flink now supports dual-stack endpoints for both IPv4 and IPv6 traffic. When you make a request to a dual-stack endpoint, the endpoint URL resolves to an IPv6 or an IPv4 address. You can access dual-stack endpoints using the SDK, a configuration file, or an environment variable.

The continued growth of the internet is exhausting available Internet Protocol version 4 (IPv4) addresses. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their VPCs. Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Create or update an Amazon Managed Service for Apache Flink application in the Amazon Managed Service for Apache Flink console.

This capability is available in all AWS regions where Amazon Managed Service for Apache Flink is currently available. For Amazon Managed Service for Apache Flink region availability, refer to the AWS Region Table. You can find out more about IPv6 on AWS here. For a full list of dual-stack endpoints, see the SDK Reference guide.
 

​Amazon Managed Service for Apache Flink now supports dual-stack endpoints for both IPv4 and IPv6 traffic. When you make a request to a dual-stack endpoint, the endpoint URL resolves to an IPv6 or an IPv4 address. You can access dual-stack endpoints using the SDK, a configuration file, or an environment variable. The continued growth of the internet is exhausting available Internet Protocol version 4 (IPv4) addresses. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their VPCs. Amazon Managed Service for Apache Flink makes it easier to transform and analyze streaming data in real time with Apache Flink. Apache Flink is an open source framework and engine for processing data streams. Create or update an Amazon Managed Service for Apache Flink application in the Amazon Managed Service for Apache Flink console. This capability is available in all AWS regions where Amazon Managed Service for Apache Flink is currently available. For Amazon Managed Service for Apache Flink region availability, refer to the AWS Region Table. You can find out more about IPv6 on AWS here. For a full list of dual-stack endpoints, see the SDK Reference guide.    

The post Impulsar a todos con agentes en Copilot Chat appeared first on Source LATAM.

​The post Impulsar a todos con agentes en Copilot Chat appeared first on Source LATAM.  

AWS Marketplace has expanded its global accessibility by introducing support for French, Spanish, Korean, and Japanese languages across both the website and AWS console. This enhancement allows customers to discover, evaluate, procure, and deploy solutions in their preferred language, reducing friction for global customers and enhancing their purchasing process.

For a localized experience, buyers select their preferred language out of 5 options in the language dropdown. The resulting language switch extends across the customer journey, allowing customers to browse the AWS Marketplace homepage, search for products, view details, and buy products and services in their chosen language. The localization covers SaaS products, AMI-based products, container-based products, and professional services.

For AWS Marketplace sellers, this launch expands their global reach. AWS Marketplace automatically translates product information into all supported languages, allowing the translated versions to become available to buyers with no additional seller effort. Sellers maintain control over their global presence and can opt out from this feature on a language or listing basis. Furthermore, sellers can now provide End User License Agreements (EULAs) in the primary language of the country for geo-fenced listings.

To get started, select your preferred language in the upper right corner of the website or console header. To learn more about AWS Marketplace’s language support, visit the AWS Marketplace Buyer Guide and Seller Guide.

​AWS Marketplace has expanded its global accessibility by introducing support for French, Spanish, Korean, and Japanese languages across both the website and AWS console. This enhancement allows customers to discover, evaluate, procure, and deploy solutions in their preferred language, reducing friction for global customers and enhancing their purchasing process. For a localized experience, buyers select their preferred language out of 5 options in the language dropdown. The resulting language switch extends across the customer journey, allowing customers to browse the AWS Marketplace homepage, search for products, view details, and buy products and services in their chosen language. The localization covers SaaS products, AMI-based products, container-based products, and professional services. For AWS Marketplace sellers, this launch expands their global reach. AWS Marketplace automatically translates product information into all supported languages, allowing the translated versions to become available to buyers with no additional seller effort. Sellers maintain control over their global presence and can opt out from this feature on a language or listing basis. Furthermore, sellers can now provide End User License Agreements (EULAs) in the primary language of the country for geo-fenced listings. To get started, select your preferred language in the upper right corner of the website or console header. To learn more about AWS Marketplace’s language support, visit the AWS Marketplace Buyer Guide and Seller Guide.  

Amazon FSx for NetApp ONTAP second-generation file systems are now available in additional AWS Regions: Asia Pacific (Mumbai), and Asia Pacific (Tokyo).

Amazon FSx makes it easier and more cost effective to launch, run, and scale feature-rich high-performance file systems in the cloud. Second-generation FSx for ONTAP file systems give you more performance scalability and flexibility over first-generation file systems by allowing you to create or expand file systems with up to 12 highly-available (HA) pairs of file servers, providing your workloads with up to 72 GBps of throughput and 1 PiB of provisioned SSD storage.

With this regional expansion, second-generation FSx for ONTAP file systems are available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Europe (Frankfurt, Ireland, Stockholm), and Asia Pacific (Mumbai, Singapore, Sydney, Tokyo). You can create second-generation Multi-AZ file systems with a single HA pair, and Single-AZ file systems with up to 12 HA pairs. To learn more, visit the FSx for ONTAP user guide.

​Amazon FSx for NetApp ONTAP second-generation file systems are now available in additional AWS Regions: Asia Pacific (Mumbai), and Asia Pacific (Tokyo). Amazon FSx makes it easier and more cost effective to launch, run, and scale feature-rich high-performance file systems in the cloud. Second-generation FSx for ONTAP file systems give you more performance scalability and flexibility over first-generation file systems by allowing you to create or expand file systems with up to 12 highly-available (HA) pairs of file servers, providing your workloads with up to 72 GBps of throughput and 1 PiB of provisioned SSD storage. With this regional expansion, second-generation FSx for ONTAP file systems are available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Europe (Frankfurt, Ireland, Stockholm), and Asia Pacific (Mumbai, Singapore, Sydney, Tokyo). You can create second-generation Multi-AZ file systems with a single HA pair, and Single-AZ file systems with up to 12 HA pairs. To learn more, visit the FSx for ONTAP user guide.  

AWS Private Certificate Authority (AWS Private CA) now supports Active Directory (AD) child domains through the Private CA Connector for AD. With this feature, customers get a consistent experience using AWS Private CA across parent and child AD domains. AD administrators can issue certificates to users, computers, and devices in a child domain independently of the parent domain and other child domains. This feature works with on-premises and self-hosted AD deployments that are connected to AWS through AWS Directory Service AD Connector.

Private CA Connector for AD allows you to replace your certificate authorities (CAs) with AWS Private CA, a highly-available, fully-managed cloud CA that secures private key material using hardware security modules (HSMs). Connector for AD supports auto-enrollment to ensure AD domain-joined users, computers, and devices get and maintain valid certificates automatically. In addition to Connector for AD, AWS Private CA provides connectors that enable integration with Kubernetes clusters and enterprise mobile device management (MDM) solutions.

AD child domain support is available in all regions where both AWS Private CA Connector for AD and AWS Directory Service are available. To learn more about using AWS Private CA with Active Directory child domains, visit the AWS Private CA User Guide.

​AWS Private Certificate Authority (AWS Private CA) now supports Active Directory (AD) child domains through the Private CA Connector for AD. With this feature, customers get a consistent experience using AWS Private CA across parent and child AD domains. AD administrators can issue certificates to users, computers, and devices in a child domain independently of the parent domain and other child domains. This feature works with on-premises and self-hosted AD deployments that are connected to AWS through AWS Directory Service AD Connector. Private CA Connector for AD allows you to replace your certificate authorities (CAs) with AWS Private CA, a highly-available, fully-managed cloud CA that secures private key material using hardware security modules (HSMs). Connector for AD supports auto-enrollment to ensure AD domain-joined users, computers, and devices get and maintain valid certificates automatically. In addition to Connector for AD, AWS Private CA provides connectors that enable integration with Kubernetes clusters and enterprise mobile device management (MDM) solutions. AD child domain support is available in all regions where both AWS Private CA Connector for AD and AWS Directory Service are available. To learn more about using AWS Private CA with Active Directory child domains, visit the AWS Private CA User Guide.  

Today, Amazon DataZone and Amazon SageMaker announced a new user interface (UI) capability allowing a DataZone domain to be upgraded and used directly in the next generation of Amazon SageMaker. This makes the investment customers put into developing Amazon DataZone transferable to Amazon SageMaker. All content created and curated through Amazon DataZone such as assets, metadata forms, glossaries, subscriptions, etc. are available to users through Amazon SageMaker Unified Studio after the upgrade.

As an Amazon DataZone administrator, you can choose which of your domains to upgrade to Amazon SageMaker via a UI driven experience. The upgraded domain lets you leverage your existing Amazon DataZone implementation in the new Amazon SageMaker environment and expand to new SQL analytics, data processing and AI uses cases. Additionally, after upgrading both Amazon DataZone and Amazon SageMaker portals remain accessible. This provides administrators flexibility with user rollout of Amazon SageMaker, while ensuring business continuity for users operating within Amazon DataZone. By upgrading to Amazon SageMaker, users can build on their investment from Amazon DataZone by utilizing Amazon SageMaker’s unified platform that serves as the central hub for all data, analytics, and AI needs.

The domain upgrade capability is available in all AWS Regions where Amazon DataZone and Amazon SageMaker is supported, including: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Seoul), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (Stockholm), Europe (London), South America (São Paulo), Mumbai (BOM), Stockholm (ARN), and Paris (CDG).

To learn more, visit Amazon DataZone and Amazon SageMaker then get started with the upgrade domain documentation.

​Today, Amazon DataZone and Amazon SageMaker announced a new user interface (UI) capability allowing a DataZone domain to be upgraded and used directly in the next generation of Amazon SageMaker. This makes the investment customers put into developing Amazon DataZone transferable to Amazon SageMaker. All content created and curated through Amazon DataZone such as assets, metadata forms, glossaries, subscriptions, etc. are available to users through Amazon SageMaker Unified Studio after the upgrade. As an Amazon DataZone administrator, you can choose which of your domains to upgrade to Amazon SageMaker via a UI driven experience. The upgraded domain lets you leverage your existing Amazon DataZone implementation in the new Amazon SageMaker environment and expand to new SQL analytics, data processing and AI uses cases. Additionally, after upgrading both Amazon DataZone and Amazon SageMaker portals remain accessible. This provides administrators flexibility with user rollout of Amazon SageMaker, while ensuring business continuity for users operating within Amazon DataZone. By upgrading to Amazon SageMaker, users can build on their investment from Amazon DataZone by utilizing Amazon SageMaker’s unified platform that serves as the central hub for all data, analytics, and AI needs. The domain upgrade capability is available in all AWS Regions where Amazon DataZone and Amazon SageMaker is supported, including: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Seoul), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (Stockholm), Europe (London), South America (São Paulo), Mumbai (BOM), Stockholm (ARN), and Paris (CDG). To learn more, visit Amazon DataZone and Amazon SageMaker then get started with the upgrade domain documentation.