10/11/2024, 12:00:00 AM ~ 10/14/2024, 12:00:00 AM (UTC)

Recent Announcements

Bring your conversations to WhatsApp with AWS End User Messaging Social

AWS announces End User Messaging Social, enabling developers to message their end users on WhatsApp, the world’s most popular messaging app with over 2.7 billion users. With this release, developers can create rich messaging experiences on WhatsApp with multimedia content and interactive features. They can now use WhatsApp alongside End User Messaging SMS and Push notifications as part of their messaging strategy, ensuring they can communicate to their end users through the channels they prefer most.\n To get started, developers can create a new WhatsApp Business Account (WABA) using our self-guided onboarding or link an existing WABA to End User Messaging, all within the AWS management console. This means developers can start messaging with WhatsApp in minutes. End User Messaging Social simplifies message sending and receiving with AWS security, support, and management capabilities. AWS End User Messaging Social is available in the following regions: US East (N. Virginia), US West (Oregon), US East (Ohio), Europe (London), Europe (Ireland), Asia Pacific (Singapore), and Asia Pacific (Mumbai). To learn more and get started, please refer to the help documentation or visit the AWS End User Messaging website.

Amazon Redshift announces generally availability for data sharing with data lake tables

Amazon Redshift’s Data Sharing of data lake tables is now generally available, offering a secure and convenient way to share live data lake tables across different Amazon Redshift warehouses. Data Sharing of data lake tables in the AWS Glue Data Catalog provides live access to the data, ensuring that you always see the most up-to-date and consistent information as it is updated in the data lake.\n Today you can use Amazon Redshift to query your data lake but you cannot leverage the power of Redshift or Lake Formation managed data sharing with external schemas referencing your data lake tables. You have redundant effort to setup your data lake tables for each Redshift warehouse which increases your administration overhead. Now with Redshift and Lake Formation managed Data Sharing of data lake tables, you can right size the data sharing consumer compute while maintaining seamless access to the data lake tables without needing to recreate any table or view definitions. You can use SQL or the Redshift console to securely share data at various levels, including, tables and views. Data Sharing of data lake tables in the AWS Glue Data Catalog is available in all regions where Redshift Serverless and Provisioned RA3 node types are available. Learn more about Data Sharing capability in Redshift feature page, refer to Redshift documentation and refer to the Lake Formation documentation.

AWS Backup is now available in AWS Asia Pacific (Malaysia)

Today, we are announcing the availability of AWS Backup in the Asia Pacific (Malaysia) Region. AWS Backup is a fully-managed, policy-driven service that allows you to centrally automate data protection across multiple AWS services spanning compute, storage, and databases. Using AWS Backup, you can centrally create and manage backups of your application data, protect your data from inadvertent or malicious actions with immutable recovery points and vaults, and restore your data in the event of a data loss incident.\n You can get started with AWS Backup using the AWS Backup console, SDKs, or CLI by creating a data protection policy and then assigning AWS resources to it using tags or Resource IDs. For more information on the features available in the Asia Pacific (Malaysia) Region, visit the AWS Backup product page and documentation. To learn about the Regional availability of AWS Backup, see the AWS Regional Services List.

AWS Resource Explorer introduces new API to list resource inventory

AWS Resource Explorer customers can now list all AWS resources indexed by Resource Explorer across Services, AWS Regions, and AWS accounts.\n Customers use Resource Explorer to search for supported AWS resources using keywords and search operators to return up to 1,000 relevancy-ranked results. Starting today, customers can use the same familiar search operators to list and paginate through all matching results with Resource Explorer’s new ListResources API. The ListResources API is available in the AWS SDKs and CLI. To learn more about this capability, please visit our documentation. This feature is available in all AWS Commercial Regions.

AWS Elemental MediaPackage now available in Middle East (UAE) and Asia Pacific (Hyderabad) regions

AWS Elemental MediaPackage is now available in the Middle East (UAE) and Asia Pacific (Hyderabad) regions, enabling users to configure and operate MediaPackage using the console or API endpoints in these regions.\n AWS Elemental MediaPackage is a video origination and just-in-time packaging service that allows video distributors to securely and reliably deliver live streaming or on-demand content at scale. From a single video input, MediaPackage creates video streams formatted to play on connected TVs, mobile phones, computers, tablets, and game consoles. It makes it easy to implement popular video features commonly found on DVRs, such as start-over, pause, and rewind. The service can also protect your content using Digital Rights Management (DRM) technologies. MediaPackage functions independently or as part of AWS Elemental Media Services, a family of services that form the foundation of cloud-based video workflows and offer the capabilities you need to create, package, and deliver video. Visit the AWS Region Table for a full list of AWS Regions where MediaPackage is available.

Amazon Connect Contact Lens dashboards now support additional customization capabilities

Amazon Connect Contact Lens dashboards now include the ability to color code metric performance, customize service level thresholds, and switch metrics within widgets. With these dashboards, you can view and compare real-time and historical aggregated performance, trends, and insights using custom-defined time periods (e.g., week over week), summary charts, time-series chart, etc. You can further customize the dashboards by changing the metrics you want to monitor, as well as color code metric performance based on custom defined thresholds. For example, you can automatically show service level as red if it dips below 70%, yellow if its between 70-90%, and green if its greater than 90% to give a quick visual indicator on how service level is performing.\n This feature is available in all commercial AWS regions where Amazon Connect is offered. To learn more about dashboards, see the Amazon Connect Administrator Guide. To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website.

Cross-zone enabled Network Load Balancer now supports zonal shift and zonal autoshift

AWS Network Load Balancer (NLB) now supports Amazon Application Recovery Controller’s zonal shift and zonal autoshift features on load balancers that are enabled across zones. Zonal shift allows you to quickly shift traffic away from an impaired Availability Zone (AZ) and recover from events such as bad application deployment and gray failures. Zonal autoshift safely and automatically shifts your traffic away from an AZ when AWS identifies potential impact to it.\n Enabling cross-zone on NLBs is a popular configuration for customers that require an even distribution of traffic across application targets in multiple AZs. With this launch, customers can shift traffic away from an AZ in the event of a failure just like they are able to for cross-zone disabled load balancers. When zonal shift or autoshift is triggered, the NLB will block all traffic to targets in the AZ that is impacted. You can configure this feature in two steps: First, enable configuration to allow zonal shift to act on your load balancer(s) using the NLB console or API. Second, trigger zonal shift or enable zonal autoshift for the chosen NLBs via Amazon Application Recovery Controller console or API. Zonal shift and zonal autoshift support on NLB is available in all commercial AWS Regions, including the AWS GovCloud (US) Regions. To learn more, please refer to the NLB zonal shift documentation.

Amazon CloudFront launches support for JA4 fingerprinting

Amazon CloudFront now supports JA4 fingerprinting of incoming requests, enabling customers to allow known clients or block requests from malicious clients. The JA4 fingerprint is passed via the Cloudfront-viewer-ja4-fingerprint header. You can inspect the JA4 fingerprints using custom logic on your application web servers or using CloudFront Functions or Lambda@Edge.\n A JA4 TLS client fingerprint contains a 38-character long fingerprint of the TLS Client Hello which is used to initiate a secure connection from clients. The fingerprint can be used to build a database of known good and bad actors to apply when inspecting HTTP requests. You can add the Cloudfront-viewer-ja4-fingerprint header to an origin request policy and attach the policy to your CloudFront distributions. You can then inspect the header value on your application web servers or in your Lambda@Edge and CloudFront Functions to compare the header value against a list of known malware fingerprints to block malicious clients. You can also compare the header value against a list of expected fingerprints to allow only requests bearing the expected fingerprints. Cloudfront-viewer-ja4-fingerprint headers are available for immediate use in all CloudFront edge locations. You can enable JA4 fingerprint headers in the CloudFront Console or using the AWS SDK. There are no additional fees to use JA4 fingerprint headers. For more information, see the CloudFront Developer Guide.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Architecture Blog

AWS Big Data Blog

AWS Database Blog

Desktop and Application Streaming

AWS for Industries

AWS Machine Learning Blog

Open Source Project

AWS CLI

AWS CDK

AWS Load Balancer Controller