Amazon EventBridge Pipes now supports event delivery through AWS PrivateLink, allowing you to send events from an event source located in an Amazon Virtual Private Cloud (VPC) to a Pipes target without traversing the public internet. With today’s launch, you can use Pipes to poll from Amazon Managed Streaming for Apache Kafka (MSK), self-managed Kafka, and Amazon MQ sources residing in a private subnet without the need to deploy a NAT gateway, configure firewall rules, or set up proxy servers. Amazon EventBridge lets you use events to connect application components, making it easier to build scalable event-driven applications. EventBridge Pipes provides a simple, consistent, and cost-effective way to create point-to-point integrations between event producers and consumers. Pipes enables you to send data from one of 7 different event sources to any of the 20+ targets supported by the EventBridge Event Bus, including HTTPS endpoints through EventBridge API Destinations and event buses themselves. Today’s release of event delivery through AWS PrivateLink further reduces the amount of integration code you need to write and infrastructure you need to maintain when building event-driven applications. AWS PrivateLink support for EventBridge Pipes event delivery is available in all AWS Regions where EventBridge Pipes is available. To learn more about Amazon EventBridge Pipes, visit the EventBridge documentation.

Amazon OpenSearch Service now supports Amazon Route 53 alias records for defining custom domain endpoints. Alias records provide better flexibility when configuring routing to AWS resources. For more information about Route 53 alias records, please see documentation. Previously, customers had to create a CNAME type DNS record to point their custom DNS domain name to the search endpoint exposed by OpenSearch Service. With this launch, along with CNAME support, customers can create a Route 53 alias record of either IPv4 or IPv6 type for their preferred custom endpoint, and point it to their domain’s dual-stack search endpoint. In order to create a Route53 alias record, customers must first configure their Amazon OpenSearch Service domain to use the dual stack ip address type. Customers can setup Route 53 alias records using the Route 53 APIs. Amazon Route 53 alias support for Amazon OpenSearch Service domains is now available in all AWS regions except AWS GovCloud (US) Regions where Amazon OpenSearch service is available. To learn more about Amazon OpenSearch Service, please visit the product page.

Today, Amazon Timestream for LiveAnalytics announces Timestream Compute Unit (TCU), serverless compute capacity, for customers to predict and control query costs. With TCUs, you are charged for the duration of compute units (TCU) used by your queries, and there are no minimum bytes metered for queries. Amazon Timestream for LiveAnalytics is a serverless time-series database that automatically scales to ingest and analyze gigabytes of time-series data. With Timestream Compute Units, you can leverage the pay-per-use pricing with the ability to control the number of TCUs used by your queries, providing the ability to control query costs and adhere to budgets. As the compute units can execute queries concurrently, you can also cost-effectively scale your workload without any per query minimum bytes metered. To get started, use the management console, AWS SDK, or CLI to configure the maximum Timestream Compute Units for your account. New Timestream customers will use TCUs for query pricing. Existing customers can do a one-time opt-in (optional) to use TCUs for better cost controls and to remove per query minimum bytes metered. Timestream compute units will be the default query pricing and is available in all AWS regions the service operates. As Timestream for LiveAnalytics expands to existing AWS regions, the TCU query pricing will be the only option. To learn more about the Timestream Compute Units, see the developer guide. For pricing, visit Timestream pricing page.

Today, AWS announced the opening of a new AWS Direct Connect location within the CyrusOne Aurora data center in Aurora, Illinois. By connecting your network to AWS at the new Illinois location, you gain private, direct access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones. This is the third AWS Direct Connect site within Chicago Metropolitan area and the 43rd site in the United States.  The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet. The new Direct Connect location at CyrusOne Aurora offers dedicated 10 Gbps and 100 Gbps connections with MACsec encryption available. For more information on the over 140 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.

Today, AWS AppFabric announces support for three new data sources: Salesforce, Azure Monitor, and Google Analytics. Starting now, IT administrators and security analysts can use AppFabric to quickly integrate with 29 supported SaaS applications, aggregate enriched and normalized SaaS audit logs, and audit end-user access across their SaaS apps.  AWS AppFabric quickly connects SaaS applications with security tools like Barracuda XDR, Dynatrace, Logz.io, Netskope, NetWitness, Rapid7, and Splunk, or data lakes like Amazon Security Lake. With AppFabric, IT and security teams can more easily manage and secure SaaS applications by aggregating and normalizing log data into a central repository, and employees can soon complete everyday tasks faster using generative artificial intelligence (AI). With today’s announcement, IT and security analysts can improve their SaaS security posture across 29 SaaS applications without managing application specific API integrations. AWS AppFabric is generally available in the following AWS Regions: US East (N. Virginia), Asia Pacific (Tokyo), and Europe (Ireland). To learn more, visit AWS AppFabric.

Amazon RDS for MySQL now supports MySQL Innovation Release 8.3 in the Amazon RDS Database Preview Environment, allowing you to evaluate the latest Innovation Release on Amazon RDS for MySQL. You can deploy MySQL 8.3 in the Amazon RDS Database Preview Environment that has the benefits of a fully managed database, making it simpler to set up, operate, and monitor databases. MySQL 8.3 is the latest Innovation Release from the MySQL community. MySQL Innovation releases include bug fixes, security patches, as well as new features. MySQL Innovation releases are supported by the community until the next major & minor release, whereas MySQL Long Term Support (LTS) Releases, such as MySQL 8.0, are supported by the community for up to eight years. Please refer to the MySQL 8.3 release notes for more details about this release.  The Amazon RDS Database Preview Environment supports both Single-AZ and Multi-AZ deployments on the latest generation of instance classes. Amazon RDS Database Preview Environment database instances are retained for a maximum period of 60 days and are automatically deleted after the retention period. Amazon RDS database snapshots that are created in the preview environment can only be used to create or restore database instances within the preview environment.  Amazon RDS Database Preview Environment database instances are priced the same as production RDS instances created in the US East (Ohio) Region.

Amazon Redshift now supports Multi-AZ deployment for zero-ETL integration on RA3 clusters, enabling customers to run near real-time analytics on a highly available data warehouse. With a Multi-AZ deployment, your zero-ETL integration can automatically recover from any infrastructure or Availability Zone (AZ) failures ensuring your workloads remain uninterrupted. Amazon Redshift zero-ETL integration helps you derive holistic insights across many applications and break data silos in your organization, making it simpler to analyze data from different operational databases. A Multi-AZ deployment raises the Redshift Service Level Agreement (SLA) to 99.99% and delivers a highly available data warehouse. A zero-ETL integration with a Multi-AZ deployment on an Amazon Redshift cluster enables you to continue replicating the data without interruptions even in the face of unexpected events, ensuring that your near real-time insights are always accessible. To learn more and get started with zero-ETL integration, visit the getting started guides for Amazon Redshift. To learn more about Amazon Redshift Multi-AZ, see the Amazon Redshift Reliability page and Amazon Multi-AZ documentation page. 

Starting today, AWS WAF is available in the AWS Canada West (Calgary) Region. This is the second Region in Canada where AWS WAF is available, joining the AWS Canada (Central) Region, and giving customers more choice and flexibility. AWS WAF is a web application firewall that helps you protect your web application resources against common web exploits and bots that can affect availability, compromise security, or consume excessive resources. You can protect Amazon CloudFront distributions and Application Load Balancer in the AWS Canada West (Calgary) Region. Support for other AWS resource types, such as Amazon API Gateway REST APIs, is expected later. With AWS WAF, you can control access to your content. Based on conditions that you specify, such as the IP addresses that requests originate from or the values of query strings, your protected resource responds to requests either with the requested content, with an HTTP 403 status code (Forbidden), or with a custom response. To see the full list of regions where AWS WAF is currently available, visit the AWS Region Table. For more information about the service, visit the AWS WAF page.

Today, AWS Security Hub announces the release of the AWS Resource Tagging standard. The standard contains 85 new controls which can be used to identify if any of your AWS Resources are missing tag keys required by your organization. With the release of this standard, Security Hub now offers 386 security controls that automatically check the compliance of your AWS resources against pre-defined security principles and best practices. To quickly enable the new standard across your AWS environment, you should use central configuration. This will allow you to enable the standard in some or all of your organization accounts and across all of AWS Regions that are linked to Security Hub with a single action. Furthermore, you can use central configuration to centrally define the requiredTagKeys parameter that specifies the tag keys that the new controls check for. Alternatively, if you are not using central configuration, you may enable the standard and define the tags that the controls will check for on an account-by-account and Region-by-Region basis. To learn more about using central configuration, visit the AWS security blog. To get started with Security Hub, consult the following list of resources: Learn more about Security Hub capabilities and features, and the Regions in which they are available, in the AWS Security Hub user guide Subscribe to the Security Hub SNS topic to receive notifications about new Security Hub features and controls Try Security Hub at no cost for 30 days

Amazon Titan Text Embeddings V2, a new embeddings model in the Amazon Titan family of models, is now generally available in Amazon Bedrock. Using Titan Text Embeddings V2, customers can perform various natural language processing (NLP) tasks by representing text data as numerical vectors, known as embeddings. These embeddings capture the semantic and contextual relationships between words, phrases, or documents in a high-dimensional vector space. This model is optimized for Retrieval-Augmented Generations (RAG) use cases and is also well suited for a variety of other tasks such as information retrieval, question and answer chatbots, classification, and personalized recommendations. Amazon Text Embeddings V2 is a light weight, efficient model ideal for high accuracy retrieval tasks at different dimensions. The model supports flexible embeddings sizes (256, 512, 1,024) and prioritizes accuracy maintenance at smaller dimension sizes, helping to reduce storage costs without compromising on accuracy. When reducing from 1,024 to 512 dimensions, Titan Text Embeddings V2 retains approximately 99% retrieval accuracy, and when reducing from 1,024 to 256 dimensions, the model maintains 97% accuracy. Additionally, Titan Text Embeddings V2 includes multilingual support for 100+ languages in pre-training as well as unit vector normalization for improving accuracy of measuring vector similarity.  Amazon Titan Text Embeddings V2 is available in the US East (N. Virginia) and US West (Oregon) AWS Regions. To learn more, read the AWS News launch blog, Amazon Titan product page, and documentation. To get started with Titan Text Embeddings V2 in Amazon Bedrock, visit the Amazon Bedrock console.