Encuesta revela que el 62% de las empresas en Puerto Rico cuenta con una estrategia formal de ciberseguridad

​The post Encuesta revela que el 62% de las empresas en Puerto Rico cuenta con una estrategia formal de ciberseguridad appeared first on Source LATAM.  

AWS Identity and Access Management (IAM) announces outbound identity federation, enabling customers to securely federate their AWS identities to external services using short-lived JSON Web Tokens (JWTs). This allows customers to securely authenticate their AWS workloads with third-party cloud providers, SaaS providers, and self-hosted applications without using long-term credentials or implementing complex workarounds.

Customers can now exchange their AWS IAM credentials for cryptographically signed, short-lived JSON Web Tokens (JWTs), providing a simple and secure mechanism for AWS workloads to access external services. These tokens contain rich context about the AWS workloads, enabling external services to implement fine-grained access control. Administrators can control access to token generation and enforce token properties (such as lifetime, audience and signing algorithms) using IAM policies and audit token usage using CloudTrail logs, allowing them to meet their organization’s security and compliance requirements.

This capability is available in all AWS commercial Regions, AWS GovCloud (US) Regions, and China Regions. To get started, visit the list of resources below:

• Read the AWS News Blog Post
• Visit IAM Documentation

​AWS Identity and Access Management (IAM) announces outbound identity federation, enabling customers to securely federate their AWS identities to external services using short-lived JSON Web Tokens (JWTs). This allows customers to securely authenticate their AWS workloads with third-party cloud providers, SaaS providers, and self-hosted applications without using long-term credentials or implementing complex workarounds. Customers can now exchange their AWS IAM credentials for cryptographically signed, short-lived JSON Web Tokens (JWTs), providing a simple and secure mechanism for AWS workloads to access external services. These tokens contain rich context about the AWS workloads, enabling external services to implement fine-grained access control. Administrators can control access to token generation and enforce token properties (such as lifetime, audience and signing algorithms) using IAM policies and audit token usage using CloudTrail logs, allowing them to meet their organization’s security and compliance requirements. This capability is available in all AWS commercial Regions, AWS GovCloud (US) Regions, and China Regions. To get started, visit the list of resources below:

Read the AWS News Blog Post
Visit IAM Documentation  

Amazon Connect outbound campaigns now offers campaign managers the ability to configure how long voice calls should ring—between a range of 15 and 60 seconds—before marking a call as “no answer” and moving to the next contact. Each contact also records when ringing began and ended for precise reporting and traceability.

When ring duration is static, businesses struggle to balance calling efficiency and customer reach. Calls that ring too briefly may miss customers who take longer to answer, while excessive ring times delay overall campaign pacing. This lack of control leads to inconsistent contact rates and reduced agent productivity.

With configurable ring time, campaign managers can tune dialing behavior to their audience for each campaign, use analytics to see exactly how long each call rang, and understand where connections were missed. This visibility helps identify patterns, refine calling strategies, and continuously improve campaign effectiveness.

With Amazon Connect outbound campaigns, companies pay-as-they-go for campaign processing and channel usage. This feature is available in AWS regions, including US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London).

To learn more about configuring ring time for campaigns, visit our webpage.

​Amazon Connect outbound campaigns now offers campaign managers the ability to configure how long voice calls should ring—between a range of 15 and 60 seconds—before marking a call as “no answer” and moving to the next contact. Each contact also records when ringing began and ended for precise reporting and traceability. When ring duration is static, businesses struggle to balance calling efficiency and customer reach. Calls that ring too briefly may miss customers who take longer to answer, while excessive ring times delay overall campaign pacing. This lack of control leads to inconsistent contact rates and reduced agent productivity. With configurable ring time, campaign managers can tune dialing behavior to their audience for each campaign, use analytics to see exactly how long each call rang, and understand where connections were missed. This visibility helps identify patterns, refine calling strategies, and continuously improve campaign effectiveness. With Amazon Connect outbound campaigns, companies pay-as-they-go for campaign processing and channel usage. This feature is available in AWS regions, including US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), and Europe (London). To learn more about configuring ring time for campaigns, visit our webpage.  

Amazon OpenSearch Serverless now supports backup and restore through the AWS Management Console. OpenSearch Serverless automatically backs up all collections and indexes in your account every hour and retains backups for 14 days. You can restore backups using either the API or the AWS Console. This feature is enabled by default and requires no configuration. For more information, see Working with snapshots in the Amazon OpenSearch Serverless Developer Guide.

Please refer to the AWS Regional Services List for more information about Amazon OpenSearch Service availability. To learn more about OpenSearch Serverless, see the documentation. 

​Amazon OpenSearch Serverless now supports backup and restore through the AWS Management Console. OpenSearch Serverless automatically backs up all collections and indexes in your account every hour and retains backups for 14 days. You can restore backups using either the API or the AWS Console. This feature is enabled by default and requires no configuration. For more information, see Working with snapshots in the Amazon OpenSearch Serverless Developer Guide. Please refer to the AWS Regional Services List for more information about Amazon OpenSearch Service availability. To learn more about OpenSearch Serverless, see the documentation.   

Amazon Connect now provides conversational analytics for end-customer self-service interactions across voice and digital channels, helping you better understand and improve your customers’ self-service experiences. This includes across PSTN/telephony, in-app and web-calling, web and mobile chat, SMS, WhatsApp Business messaging, and Apple Messages for Business.

With this launch, Connect now provides rich conversational analytics across both human-agent interactions and end-customer self-service interactions. You can now automatically analyze the quality of automated self-service interactions including customer sentiment, redact sensitive data, discover top contact drivers and themes, identify compliance risks, and proactively identify areas for improvement through easy-to-customize dashboards. Connect’s conversational analytics also enables you to use semantic matching rules to categorize interactions based on customer behavior, keywords, sentiment, or issue types, such as billing inquiries or agent escalation requests.

Amazon Connect is an AI-powered application that provides one seamless experience for your contact center customers, agents, and supervisors. To learn more about Amazon Connect and its conversational analytics capabilities, refer to the following resources:

• Amazon Connect website and pricing
• Conversational analytics in the Administrator Guide
• Supported languages and Regions

​Amazon Connect now provides conversational analytics for end-customer self-service interactions across voice and digital channels, helping you better understand and improve your customers’ self-service experiences. This includes across PSTN/telephony, in-app and web-calling, web and mobile chat, SMS, WhatsApp Business messaging, and Apple Messages for Business. With this launch, Connect now provides rich conversational analytics across both human-agent interactions and end-customer self-service interactions. You can now automatically analyze the quality of automated self-service interactions including customer sentiment, redact sensitive data, discover top contact drivers and themes, identify compliance risks, and proactively identify areas for improvement through easy-to-customize dashboards. Connect’s conversational analytics also enables you to use semantic matching rules to categorize interactions based on customer behavior, keywords, sentiment, or issue types, such as billing inquiries or agent escalation requests. Amazon Connect is an AI-powered application that provides one seamless experience for your contact center customers, agents, and supervisors. To learn more about Amazon Connect and its conversational analytics capabilities, refer to the following resources:

Amazon Connect website and pricing
Conversational analytics in the Administrator Guide
Supported languages and Regions  

Beginning today, customers can use Amazon Bedrock in the Africa (Cape Town), Canada West (Calgary), Mexico (Central), and Middle East (Bahrain) regions to easily build and scale generative AI applications using a variety of foundation models (FMs) as well as powerful tools to build generative AI applications.

Amazon Bedrock is a comprehensive and secure service for building generative AI applications and agents. Amazon Bedrock connects you to leading foundation models (FMs) and services to deploy and operate agents, enabling you to quickly move from experimentation to real-world deployment.

To get started, visit the Amazon Bedrock page and see the Amazon Bedrock documentation for more details.

​Beginning today, customers can use Amazon Bedrock in the Africa (Cape Town), Canada West (Calgary), Mexico (Central), and Middle East (Bahrain) regions to easily build and scale generative AI applications using a variety of foundation models (FMs) as well as powerful tools to build generative AI applications. Amazon Bedrock is a comprehensive and secure service for building generative AI applications and agents. Amazon Bedrock connects you to leading foundation models (FMs) and services to deploy and operate agents, enabling you to quickly move from experimentation to real-world deployment. To get started, visit the Amazon Bedrock page and see the Amazon Bedrock documentation for more details.  

Amazon Inspector can now be enabled, configured and managed across your organization using AWS Org policies. With this new capability, you can centrally configure and manage scan types—such as Amazon EC2 scanning, ECR scanning, Lambda standard and Code Scanning, and Code Security — across all the accounts in your organization, selected organizational units (OUs), or individual accounts. The new Inspector policy type within AWS Organization simplifies your service onboarding, management, and ensures consistent, organization-wide vulnerability scanning coverage.

This feature helps you maintain a uniform security baseline by automating Inspector enablement through a single AWS Organization policy. To get started, designate a delegated admin within Amazon Inspector, enable the “Inspector policies” policy type in the AWS Organizations console, and create a policy that specifies the desired scan types and Regions. Once attached to your organization root or OUs, Inspector will automatically be enabled for all the specified scan-types across covered accounts . When the Inspector policy is created and attached, all in-scope accounts automatically are aligned with your Organization-wide policy definition. New accounts that join the organization or are moved into an OU with an attached policy, inherit Inspector enablement automatically—reducing operational overhead and eliminating coverage gaps.

Amazon Inspector is a vulnerability management service that continuously scans AWS workloads including Amazon EC2 instances, container images, AWS Lambda functions, and code repositories for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization. The AWS Organizations Inspector policy for organization-wide enablement is available at no additional cost to Amazon Inspector customers in all AWS commercial, China, and AWS GovCloud (US) Regions where Amazon Inspector is available.

To learn more about Amazon Inspector policies within AWS Organization, visit:

• Getting started with Amazon Inspector
• Managing organization policies with AWS Organizations

​Amazon Inspector can now be enabled, configured and managed across your organization using AWS Org policies. With this new capability, you can centrally configure and manage scan types—such as Amazon EC2 scanning, ECR scanning, Lambda standard and Code Scanning, and Code Security — across all the accounts in your organization, selected organizational units (OUs), or individual accounts. The new Inspector policy type within AWS Organization simplifies your service onboarding, management, and ensures consistent, organization-wide vulnerability scanning coverage. This feature helps you maintain a uniform security baseline by automating Inspector enablement through a single AWS Organization policy. To get started, designate a delegated admin within Amazon Inspector, enable the “Inspector policies” policy type in the AWS Organizations console, and create a policy that specifies the desired scan types and Regions. Once attached to your organization root or OUs, Inspector will automatically be enabled for all the specified scan-types across covered accounts . When the Inspector policy is created and attached, all in-scope accounts automatically are aligned with your Organization-wide policy definition. New accounts that join the organization or are moved into an OU with an attached policy, inherit Inspector enablement automatically—reducing operational overhead and eliminating coverage gaps. Amazon Inspector is a vulnerability management service that continuously scans AWS workloads including Amazon EC2 instances, container images, AWS Lambda functions, and code repositories for software vulnerabilities, code vulnerabilities, and unintended network exposure across your entire AWS organization. The AWS Organizations Inspector policy for organization-wide enablement is available at no additional cost to Amazon Inspector customers in all AWS commercial, China, and AWS GovCloud (US) Regions where Amazon Inspector is available. To learn more about Amazon Inspector policies within AWS Organization, visit:

Getting started with Amazon Inspector
Managing organization policies with AWS Organizations  

AWS announced expanded capabilities in Amazon Bedrock Guardrails for code-related use cases, enabling customers to protect against harmful content in code while building generative AI applications. This new capability allows customers to leverage existing safeguards offered by Bedrock Guardrails including content filters, denied topics, and sensitive information filters to detect intent to inject malicious code, detect and prevent prompt leakages, and help protect against introducing personally identifiable information (PII) within code.

With expanded support for code-related use cases, Amazon Bedrock Guardrails now provides customers with safeguards against harmful content introduced within code elements, including comments, variable and function names, and string literals. Content filters (with standard tier) in Bedrock Guardrails now detect and filter such harmful content in code in the same way as text and image content protection. Additionally, Bedrock Guardrails offers enhanced protection with prompt leakage detection with standard tier, helping detect and prevent unintended disclosure of information from system prompts in model responses that could compromise intellectual property. Furthermore, denied topics (with standard tier) and sensitive information filters with Bedrock Guardrails now help safeguard against vulnerabilities using code within topics and help prevent inclusion of PII within code structures.

The expanded capabilities for code-related cases is available in all AWS Regions where Amazon Bedrock Guardrails is supported. Customers can access the service through the Amazon Bedrock console, as well as the supported APIs.

To learn more, read the launch blog, technical documentation, and the Bedrock Guardrails product page.

​AWS announced expanded capabilities in Amazon Bedrock Guardrails for code-related use cases, enabling customers to protect against harmful content in code while building generative AI applications. This new capability allows customers to leverage existing safeguards offered by Bedrock Guardrails including content filters, denied topics, and sensitive information filters to detect intent to inject malicious code, detect and prevent prompt leakages, and help protect against introducing personally identifiable information (PII) within code. With expanded support for code-related use cases, Amazon Bedrock Guardrails now provides customers with safeguards against harmful content introduced within code elements, including comments, variable and function names, and string literals. Content filters (with standard tier) in Bedrock Guardrails now detect and filter such harmful content in code in the same way as text and image content protection. Additionally, Bedrock Guardrails offers enhanced protection with prompt leakage detection with standard tier, helping detect and prevent unintended disclosure of information from system prompts in model responses that could compromise intellectual property. Furthermore, denied topics (with standard tier) and sensitive information filters with Bedrock Guardrails now help safeguard against vulnerabilities using code within topics and help prevent inclusion of PII within code structures. The expanded capabilities for code-related cases is available in all AWS Regions where Amazon Bedrock Guardrails is supported. Customers can access the service through the Amazon Bedrock console, as well as the supported APIs. To learn more, read the launch blog, technical documentation, and the Bedrock Guardrails product page.  

AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track cloud cost efficiency over time across your organization. This metric automatically calculates the percentage of your cloud spend that can be optimized by considering rightsizing, idle, and commitment recommendations, allowing you to establish consistent cost savings benchmarks, set performance goals, and track progress to maximize your return on cloud investments.

AWS Cost Optimization Hub provides you with a measure of your cost efficiency by dividing aggregated estimated monthly savings of your cost optimization opportunities by your optimizable spend. You can track this metric over time across your organization to understand and benchmark your cost efficiency. With daily refreshes, the metric provides daily insights into optimization progress, showing score improvements when you implement cost-saving recommendations and score decreases when inefficient resources are provisioned.

Cost efficiency is now available in AWS Cost Optimization Hub across all AWS Regions where AWS Cost Optimization Hub is supported. To get started with cost efficiency metric, please visit the user guide and blog. 

​AWS Cost Optimization Hub, a feature within the Billing and Cost Management Console, now supports a Cost Efficiency metric that helps you measure and track cloud cost efficiency over time across your organization. This metric automatically calculates the percentage of your cloud spend that can be optimized by considering rightsizing, idle, and commitment recommendations, allowing you to establish consistent cost savings benchmarks, set performance goals, and track progress to maximize your return on cloud investments. AWS Cost Optimization Hub provides you with a measure of your cost efficiency by dividing aggregated estimated monthly savings of your cost optimization opportunities by your optimizable spend. You can track this metric over time across your organization to understand and benchmark your cost efficiency. With daily refreshes, the metric provides daily insights into optimization progress, showing score improvements when you implement cost-saving recommendations and score decreases when inefficient resources are provisioned. Cost efficiency is now available in AWS Cost Optimization Hub across all AWS Regions where AWS Cost Optimization Hub is supported. To get started with cost efficiency metric, please visit the user guide and blog.   

AWS Channel Partners who are part of AWS Solution Provider or Distribution program can now resell AWS services using Billing Transfer. Billing Transfer enables Partners to assume financial responsibility for customer AWS Organizations while customers retain full control of their management accounts. Using Billing Transfer with AWS Partner Central channel management, Partners receive eligible program benefits applied to AWS bills delivered to their AWS Organization, while end customers view their costs at Partner-configured rates within their separate AWS Organization.

Billing Transfer helps all AWS Channel Partners simplify operations by centrally managing billing and payments across many customer AWS Organizations from a single partner management account. Partners can also now use new APIs for Partner Central to manage channel program reporting and incentive qualification from their own systems. End customers gain autonomy to independently manage their AWS Organizations while benefiting from Partner value-added services such as cost optimization and service management.

Billing Transfer is available to all AWS Channel Partners and their end customers operating in public AWS Regions, excluding the AWS GovCloud (US), China (Beijing), and China (Ningxia) Regions.

Channel Partners can get started today through AWS Partner Central channel management. To learn more, see the Channel management user guide in Partner Central documentation and read the AWS Blog.

​AWS Channel Partners who are part of AWS Solution Provider or Distribution program can now resell AWS services using Billing Transfer. Billing Transfer enables Partners to assume financial responsibility for customer AWS Organizations while customers retain full control of their management accounts. Using Billing Transfer with AWS Partner Central channel management, Partners receive eligible program benefits applied to AWS bills delivered to their AWS Organization, while end customers view their costs at Partner-configured rates within their separate AWS Organization. Billing Transfer helps all AWS Channel Partners simplify operations by centrally managing billing and payments across many customer AWS Organizations from a single partner management account. Partners can also now use new APIs for Partner Central to manage channel program reporting and incentive qualification from their own systems. End customers gain autonomy to independently manage their AWS Organizations while benefiting from Partner value-added services such as cost optimization and service management. Billing Transfer is available to all AWS Channel Partners and their end customers operating in public AWS Regions, excluding the AWS GovCloud (US), China (Beijing), and China (Ningxia) Regions. Channel Partners can get started today through AWS Partner Central channel management. To learn more, see the Channel management user guide in Partner Central documentation and read the AWS Blog.