Amazon Lex now supports Confirmation and Alphanumeric slot types in Korean (ko-KR) locale. These built-in slot types help developers build more natural and efficient conversational experiences in Korean language applications.

The Confirmation slot type automatically resolves various Korean expressions into ‘Yes’, ‘No’, ‘Maybe’, and ‘Don’t know’ values, eliminating the need for custom slots with multiple synonyms. The Alphanumeric slot type enables capturing combinations of letters and numbers, with support for regular expressions to validate specific formats, making it easier to collect structured data like identification numbers or reference codes.

Korean support for these slot types is available in all AWS regions where Amazon Lex V2 operates.

To learn more about implementing these features, visit the Amazon Lex documentation for Custom Vocabulary and Alphanumerics.

 

​Amazon Lex now supports Confirmation and Alphanumeric slot types in Korean (ko-KR) locale. These built-in slot types help developers build more natural and efficient conversational experiences in Korean language applications. The Confirmation slot type automatically resolves various Korean expressions into ‘Yes’, ‘No’, ‘Maybe’, and ‘Don’t know’ values, eliminating the need for custom slots with multiple synonyms. The Alphanumeric slot type enables capturing combinations of letters and numbers, with support for regular expressions to validate specific formats, making it easier to collect structured data like identification numbers or reference codes. Korean support for these slot types is available in all AWS regions where Amazon Lex V2 operates. To learn more about implementing these features, visit the Amazon Lex documentation for Custom Vocabulary and Alphanumerics.  

AWS Secrets Manager now supports higher request rates for the core set of API operations: GetSecretValue and DescribeSecret. GetSecretValue now supports up to 10,000 requests per second and DescribeSecret supports 40,000 requests per second. The increased API limits are available at no additional cost and will automatically be applied to your AWS accounts. No further action required on your end.

Increased API limits for GetSecretValue and DescribeSecret are available in all regions where the service operates. For a list of regions where Secrets Manager is available, see the AWS Region table. To learn more about Secrets Manager API operations, visit our API reference.

 

​AWS Secrets Manager now supports higher request rates for the core set of API operations: GetSecretValue and DescribeSecret. GetSecretValue now supports up to 10,000 requests per second and DescribeSecret supports 40,000 requests per second. The increased API limits are available at no additional cost and will automatically be applied to your AWS accounts. No further action required on your end. Increased API limits for GetSecretValue and DescribeSecret are available in all regions where the service operates. For a list of regions where Secrets Manager is available, see the AWS Region table. To learn more about Secrets Manager API operations, visit our API reference.  

AWS CodeBuild now supports non-container builds on Linux x86, Arm, and Windows on-demand fleets. You can run build commands directly on the host operating system without containerization. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment.

With non-container builds, you can execute build commands that require direct access to the host system resources or have specific requirements that make containerization challenging. This feature is particularly useful for scenarios such as building device drivers, running system-level tests, or working with tools that require host machine access.

The non-container feature is available in all regions where CodeBuild is offered. For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page.

To learn more about non-container builds, please visit our documentation. To learn more about how to get started with CodeBuild, visit the AWS CodeBuild product page.
 

 

​AWS CodeBuild now supports non-container builds on Linux x86, Arm, and Windows on-demand fleets. You can run build commands directly on the host operating system without containerization. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment. With non-container builds, you can execute build commands that require direct access to the host system resources or have specific requirements that make containerization challenging. This feature is particularly useful for scenarios such as building device drivers, running system-level tests, or working with tools that require host machine access. The non-container feature is available in all regions where CodeBuild is offered. For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page. To learn more about non-container builds, please visit our documentation. To learn more about how to get started with CodeBuild, visit the AWS CodeBuild product page.    

AWS Lambda now supports Amazon CloudWatch Logs Live Tail in VS Code IDE through the AWS Toolkit for Visual Studio Code. Live Tail is an interactive log streaming and analytics capability which provides real-time visibility into logs, making it easier to develop and troubleshoot Lambda functions.

We previously announced support for Live Tail in the Lambda console, enabling developers to view and analyze Lambda logs in real time. Now, with Live Tail support in VS Code IDE, developers can monitor Lambda function logs in real time while staying within their development environment, eliminating the need to switch between multiple interfaces for coding and log analysis. This makes it easier for developers to quickly test and validate code or configuration changes in real time, accelerating the author-test-deploy cycle when building applications using Lambda. This integration also makes it easier to detect and debug failures and critical errors in Lambda function code, reducing the mean time to recovery (MTTR) when troubleshooting Lambda function errors.

Using Live Tail for Lambda in VS Code IDE is straightforward. After installing the latest version of the AWS Toolkit for Visual Studio Code, developers can access Live Tail through the AWS Explorer panel. Simply navigate to the desired Lambda function, right-click, and select «Tail Logs» to begin streaming logs in real time.

To learn more about using Live Tail for Lambda in VS Code IDE, visit the AWS Toolkit developer guide. To learn more about CloudWatch Logs Live Tail, visit CloudWatch Logs developer guide.
 

 

​AWS Lambda now supports Amazon CloudWatch Logs Live Tail in VS Code IDE through the AWS Toolkit for Visual Studio Code. Live Tail is an interactive log streaming and analytics capability which provides real-time visibility into logs, making it easier to develop and troubleshoot Lambda functions. We previously announced support for Live Tail in the Lambda console, enabling developers to view and analyze Lambda logs in real time. Now, with Live Tail support in VS Code IDE, developers can monitor Lambda function logs in real time while staying within their development environment, eliminating the need to switch between multiple interfaces for coding and log analysis. This makes it easier for developers to quickly test and validate code or configuration changes in real time, accelerating the author-test-deploy cycle when building applications using Lambda. This integration also makes it easier to detect and debug failures and critical errors in Lambda function code, reducing the mean time to recovery (MTTR) when troubleshooting Lambda function errors. Using Live Tail for Lambda in VS Code IDE is straightforward. After installing the latest version of the AWS Toolkit for Visual Studio Code, developers can access Live Tail through the AWS Explorer panel. Simply navigate to the desired Lambda function, right-click, and select «Tail Logs» to begin streaming logs in real time. To learn more about using Live Tail for Lambda in VS Code IDE, visit the AWS Toolkit developer guide. To learn more about CloudWatch Logs Live Tail, visit CloudWatch Logs developer guide.    

Amazon Neptune Database is now available in the Asia Pacific (Malaysia) Region on engine versions 1.1.0.0 and later. You can now create Neptune clusters using R6g, R6i, T4g, and T3 instance types in the AWS Asia Pacific (Malaysia) Region.

Amazon Neptune Database is a fast, reliable, and fully managed graph database as a service that makes it easy to build and run applications work with highly connected datasets. You can build applications using Apache TinkerPop Gremlin or openCypher on the Property Graph model, or using the SPARQL query language on W3C Resource Description Framework (RDF). Neptune also offers enterprise features such as high availability, automated backups, and network isolation to help customers quickly deploy applications to production.

To get started, you can create a new Neptune cluster using the AWS Management Console, AWS CLI, or a quickstart AWS CloudFormation template. For more information on pricing and region availability, refer to the Neptune pricing page and AWS Region Table.
 

 

​Amazon Neptune Database is now available in the Asia Pacific (Malaysia) Region on engine versions 1.1.0.0 and later. You can now create Neptune clusters using R6g, R6i, T4g, and T3 instance types in the AWS Asia Pacific (Malaysia) Region. Amazon Neptune Database is a fast, reliable, and fully managed graph database as a service that makes it easy to build and run applications work with highly connected datasets. You can build applications using Apache TinkerPop Gremlin or openCypher on the Property Graph model, or using the SPARQL query language on W3C Resource Description Framework (RDF). Neptune also offers enterprise features such as high availability, automated backups, and network isolation to help customers quickly deploy applications to production. To get started, you can create a new Neptune cluster using the AWS Management Console, AWS CLI, or a quickstart AWS CloudFormation template. For more information on pricing and region availability, refer to the Neptune pricing page and AWS Region Table.    

AWS Transfer Family has reduced the service side login latency from 1-2 seconds to under 500 milliseconds.

AWS Transfer Family offers fully managed support for the transfer of files over SFTP, AS2, FTPS, FTP, and web browser-based transfers directly into and out of AWS storage services. With this launch, you benefit from significantly reduced latency from the service to initiate the transfer over SFTP. This optimization offers substantial benefits, particularly for high-frequency, low-latency use cases with automated processes or applications requiring rapid file operations.

Reduced server-side login latency is immediately available at no additional cost for all new and existing Transfer Family SFTP servers in all AWS Regions where the service is available. To create an SFTP server, visit the Transfer Family User Guide.
 

 

​AWS Transfer Family has reduced the service side login latency from 1-2 seconds to under 500 milliseconds. AWS Transfer Family offers fully managed support for the transfer of files over SFTP, AS2, FTPS, FTP, and web browser-based transfers directly into and out of AWS storage services. With this launch, you benefit from significantly reduced latency from the service to initiate the transfer over SFTP. This optimization offers substantial benefits, particularly for high-frequency, low-latency use cases with automated processes or applications requiring rapid file operations. Reduced server-side login latency is immediately available at no additional cost for all new and existing Transfer Family SFTP servers in all AWS Regions where the service is available. To create an SFTP server, visit the Transfer Family User Guide.    

Etiquetas:

• IA
• Seguridad

The post Desbaratar una red global de ciberdelincuencia que abusa de la IA generativa appeared first on Source LATAM.

 

​The post Desbaratar una red global de ciberdelincuencia que abusa de la IA generativa appeared first on Source LATAM.  

Amazon API Gateway (APIGW) now supports all features of HTTP APIs as well as Mutual TLS and multi-level base path mappings on REST APIs in the following additional Regions: Middle East (UAE), Asia Pacific (Jakarta), Asia Pacific (Osaka), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), Europe (Spain), Israel (Tel Aviv), and Canada West (Calgary). AWS Web Application Firewall (WAF) for REST APIs is now available in two additional regions: Asia Pacific (Kuala Lumpur) and Canada West (Calgary).

HTTP APIs simplify API development for serverless applications with a simpler user interface that includes support for OAuth2.0 and automatic deployments. Mutual TLS enhances security by authenticating x509 certificate based identities at the APIGW. Multi-level base path mappings enable routing requests based on segments in custom domain paths, supporting path-based versioning and traffic redirection. Integration of AWS WAF offers APIs protections against common web exploits through configurable rules that allow, block, or monitor web requests.

To learn more, see API Gateway developer guide.

 

​Amazon API Gateway (APIGW) now supports all features of HTTP APIs as well as Mutual TLS and multi-level base path mappings on REST APIs in the following additional Regions: Middle East (UAE), Asia Pacific (Jakarta), Asia Pacific (Osaka), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich), Europe (Spain), Israel (Tel Aviv), and Canada West (Calgary). AWS Web Application Firewall (WAF) for REST APIs is now available in two additional regions: Asia Pacific (Kuala Lumpur) and Canada West (Calgary). HTTP APIs simplify API development for serverless applications with a simpler user interface that includes support for OAuth2.0 and automatic deployments. Mutual TLS enhances security by authenticating x509 certificate based identities at the APIGW. Multi-level base path mappings enable routing requests based on segments in custom domain paths, supporting path-based versioning and traffic redirection. Integration of AWS WAF offers APIs protections against common web exploits through configurable rules that allow, block, or monitor web requests. To learn more, see API Gateway developer guide.  

Amazon Cognito now allows customers to customize access tokens for M2M flows, enabling you to implement fine-grained authorization in your applications, APIs, and workloads. M2M authorization is commonly used for automated processes such as scheduled data synchronization tasks, event-driven workflows, microservices communication, or real-time data streaming between systems. In M2M authorization flows, an app client can represent a software system or service that can request access tokens to interact with resources, such as a reporting system or a data processing service. With this launch, customers can now customize their access tokens with custom claims (attributes about the app client) and scopes (level of access that an app client can request to a resource), making it easier to control and manage how their automated systems interact with each other.

Customers can now add custom attributes directly in access tokens, reducing the complexity of authorization logic needed in their application code. For example, customers can customize access tokens with claims that allow an app client for a reporting system to only read data while allowing an app client for a data processing service to both read and modify data. This allows customers to streamline authentication by embedding custom authorization attributes directly into access tokens during the token issuance process.

Access token customization for M2M authorization is available to Amazon Cognito customers using Essentials or Plus tiers in all AWS Regions where Cognito is available, except the AWS GovCloud (US) Regions. To learn more, refer to the developer guide.
 

 

​Amazon Cognito now allows customers to customize access tokens for M2M flows, enabling you to implement fine-grained authorization in your applications, APIs, and workloads. M2M authorization is commonly used for automated processes such as scheduled data synchronization tasks, event-driven workflows, microservices communication, or real-time data streaming between systems. In M2M authorization flows, an app client can represent a software system or service that can request access tokens to interact with resources, such as a reporting system or a data processing service. With this launch, customers can now customize their access tokens with custom claims (attributes about the app client) and scopes (level of access that an app client can request to a resource), making it easier to control and manage how their automated systems interact with each other. Customers can now add custom attributes directly in access tokens, reducing the complexity of authorization logic needed in their application code. For example, customers can customize access tokens with claims that allow an app client for a reporting system to only read data while allowing an app client for a data processing service to both read and modify data. This allows customers to streamline authentication by embedding custom authorization attributes directly into access tokens during the token issuance process. Access token customization for M2M authorization is available to Amazon Cognito customers using Essentials or Plus tiers in all AWS Regions where Cognito is available, except the AWS GovCloud (US) Regions. To learn more, refer to the developer guide.    

CloudWatch RUM, which provides real-time monitoring into web application performance by tracking user interactions, now supports resource based policies that simplify access for data ingestion to RUM. With resource-based policies, you can specify which Identity and Access Management (IAM) principals have access to ingest data to your RUM app monitors— effectively which clients can write data to RUM. This would also allow you to ingest data at higher volume and gives you greater control over data ingress in RUM.

Using resource based policies allows you to manage ingestion access to your app monitor without using Amazon Cognito to assume an IAM role, and AWS Security Token Service (STS) to obtain security credentials to write data to CloudWatch RUM. This is beneficial for high throughput use cases where a high volume of requests may be subject to Cognito’s quota limits leading to throttling and potentially failure in ingesting data to RUM. With a public resource policy, no such limits apply. Anyone can send data to CloudWatch RUM including unauthenticated users and clients. In addition, you can use AWS Global context keys to use these policies to block certain IPs or disable clients sending data to RUM. You can configure these policies on the AWS console or via code using AWS CloudFormation.

These enhancements are available in all regions where CloudWatch RUM is available at no additional cost to users.

See documentation to know more about the feature, or see user guide to learn how to configure resource based policies for CloudWatch RUM.
 

 

​CloudWatch RUM, which provides real-time monitoring into web application performance by tracking user interactions, now supports resource based policies that simplify access for data ingestion to RUM. With resource-based policies, you can specify which Identity and Access Management (IAM) principals have access to ingest data to your RUM app monitors— effectively which clients can write data to RUM. This would also allow you to ingest data at higher volume and gives you greater control over data ingress in RUM. Using resource based policies allows you to manage ingestion access to your app monitor without using Amazon Cognito to assume an IAM role, and AWS Security Token Service (STS) to obtain security credentials to write data to CloudWatch RUM. This is beneficial for high throughput use cases where a high volume of requests may be subject to Cognito’s quota limits leading to throttling and potentially failure in ingesting data to RUM. With a public resource policy, no such limits apply. Anyone can send data to CloudWatch RUM including unauthenticated users and clients. In addition, you can use AWS Global context keys to use these policies to block certain IPs or disable clients sending data to RUM. You can configure these policies on the AWS console or via code using AWS CloudFormation. These enhancements are available in all regions where CloudWatch RUM is available at no additional cost to users. See documentation to know more about the feature, or see user guide to learn how to configure resource based policies for CloudWatch RUM.