10/3/2024, 12:00:00 AM ~ 10/4/2024, 12:00:00 AM (UTC)

Recent Announcements

AWS IoT Core removes TLS ALPN requirement and adds custom authorizer capabilities

Today, AWS IoT Core announces three new capabilities for domain configurations. Devices no longer need to rely on Transport Layer Security (TLS) Application Layer Protocol Negotiation (ALPN) extension to determine authentication type and protocol. Furthermore, developers can add additional X.509 client certificates validation to custom authentication workflow. Previously, devices selected authentication type by connecting to a defined port and providing TLS ALPN with chosen protocol. The new capability to configure authentication type and protocol purely based on the TLS Server Name Indication (SNI) extension makes it simpler to connect devices to the cloud without requiring TLS ALPN. This enables developers to migrate existing device fleets to AWS IoT Core without firmware updates or Amazon-specific TLS ALPN strings. The authentication type and protocol combination will be assigned to an endpoint for all supported TCP ports of this custom domain.\n Building on the above-mentioned feature, AWS IoT Core added two additional authentication capabilities. Custom Authentication with X.509 Client Certificates allows customers to authenticate IoT devices using X.509 certificates and then add custom authentication logics as an additional layer of security check. Secondly, Custom Client Certificate Validation allows customers to validate X.509 client certificate based on a custom Lambda function. For example, developers can build custom certificate revocation checks, such as, Online Certificate Status Protocol and Certificate Revocation List, before allowing a client to connect. All three capabilities are available in all AWS regions where AWS IoT Core is present, except AWS GovCloud (US). Visit the developer guide to learn more about this feature.

AWS B2B Data Interchange announces support for generating outbound X12 EDI

AWS B2B Data Interchange now supports outbound EDI transformation, enabling you to generate X12 EDI documents from JSON or XML data inputs. This new capability adds to B2B Data Interchange’s existing support for transforming inbound EDI documents and automatically generating EDI acknowledgements. With the ability to transform and generate X12 EDI documents up to 150 MB, you can now automate your bidirectional EDI workflows at scale on AWS.\n The introduction of outbound EDI transformation establishes B2B Data Interchange as a comprehensive EDI service for conducting end-to-end transactions with your business partners. For example, healthcare payers can now process claims with claim payments, suppliers can confirm purchase orders with invoices, and logistics providers can respond to shipment requests with status notifications. B2B Data Interchange monitors specified prefixes in Amazon S3 to automatically process inbound and outbound EDI. Each outbound EDI document generated emits an Amazon EventBridge event which can be used to automatically send the documents to your business partners using AWS Transfer Family’s SFTP and AS2 capabilities, or any other EDI connectivity solution. Support for generating outbound X12 EDI is available in all AWS Regions where AWS B2B Data Interchange is available. To get started with building and running bidirectional, event-driven EDI workflows on B2B Data Interchange, take the self-paced workshop or deploy the CloudFormation template.

AWS Compute Optimizer now supports 80 new Amazon EC2 instance types

AWS Compute Optimizer now supports 80 additional Amazon Elastic Compute Cloud (Amazon EC2) instance types. The newly supported instance types include the latest generation compute optimized instances (c7i-flex, c6id, c8g), memory optimized instances (r8g, x8g), storage optimized instances (i4i), and GPU-based instances (g5, g5g, g6, gr6, p4d, p4de, p5). This expands the total EC2 instance types supported by Compute Optimizer to 779.\n By including support for the latest instance types that have improved price to performance ratios, Compute Optimizer helps customers identify additional savings opportunities and performance improvement opportunities. The newly supported c8g, r8g, and x8g EC2 instance types include the new AWS Graviton4 processors that offer 50% more cores, 160% more memory bandwidth, and up to 60% better performance than AWS Graviton2 processors. The C7i-flex instances powered by the 4th generation Intel Xeon Scalable custom processors (Sapphire Rapids) offer 5% better price/performance compared to c7i instances. For more information about the AWS Regions where Compute Optimizer is available, see AWS Region table. For more information about Compute Optimizer, visit our product page and documentation. You can start using AWS Compute Optimizer through the AWS Management Console, AWS CLI, and AWS SDK.

AWS Cloud WAN and AWS Network Manager are now available in additional AWS Regions

With this launch, AWS Cloud WAN and AWS Network Manager are now available in AWS Asia Pacific (Melbourne, Hyderabad), AWS Europe (Spain, Zurich), AWS Middle East (UAE) Region and AWS Canada West (Calgary) Regions. Additionally, AWS Cloud WAN is available in AWS Israel (Tel Aviv) Region.\n
With AWS Cloud WAN, you can use a central dashboard and network policies to create a global network that spans multiple locations and networks, allowing you to configure and manage different networks using the same technology. You can use your network policies to specify which of your Amazon Virtual Private Clouds, AWS Transit Gateways, and on-premises locations you want to connect to by using an AWS Site-to-Site VPN, AWS Direct Connect, or third-party software-defined WAN (SD-WAN) products. The Cloud WAN central dashboard, powered by AWS Network Manager, generates a complete view of the network to help you monitor network health, security, and performance. AWS Network Manager reduces the operational complexity of managing global networks across AWS and on-premises locations. It provides a single global view of your private network. You can visualize your global network in a topology diagram and monitor your network using CloudWatch Metrics and events for network topology changes, routing updates, and connection status updates. To learn more about AWS Cloud WAN, see the product detail page and documentation. To learn more about AWS Network Manager, see the documentation.

Amazon Location Service is now available in AWS Europe (Spain) Region

Today, we are announcing the availability of Amazon Location Service in the AWS Europe (Spain) Region. Amazon Location Service is a location-based service that helps developers easily and securely add maps, search places and geocodes, plan routes, and enable device tracking and geofencing capabilities into their applications. With Amazon Location Service, developers can start a new location project or migrate from existing mapping service workloads to benefit from cost reduction, privacy protection, and ease of integration with other AWS services.\n With this launch, Amazon Location Service is now available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), Europe (Ireland), Europe (Stockholm), Asia Pacific (Singapore), Asia Pacific (Sydney), and Asia Pacific (Tokyo), Asia Pacific (Mumbai), Canada (Central), Europe (London), South America (São Paulo), AWS GovCloud (US-West), and AWS Europe (Spain). To learn more, please see the Amazon Location Service Getting Started page.

Amazon Q Business is now HIPAA eligible

Amazon Q Business is now HIPAA (Health Insurance Portability and Accountability Act) eligible. Amazon Q Business is a generative AI–powered assistant that can answer questions, provide summaries, generate content, and securely complete tasks based on data and information in your enterprise systems.\n With the Amazon Q Business HIPAA certification, healthcare and life sciences organizations such as health insurance companies and healthcare providers, can now use Amazon Q Business to run sensitive workloads regulated under the U.S. Health Insurance Portability and Accountability Act (HIPAA). AWS maintains a standards-based risk management program to ensure that the HIPAA-eligible services specifically support HIPAA administrative, technical, and physical safeguards. Amazon Q Business is HIPAA compliant in all of the AWS Regions where Amazon Q Business is supported. See the AWS Regional Services List for the most up-to-date availability information. To learn more about HIPAA eligible services, visit the webpage. To get started with Amazon Q Business, visit the product page to learn more.

Amazon Aurora Serverless v2 now supports up to 256 ACUs

Amazon Aurora Serverless v2 now supports database capacity of up to 256 Aurora Capacity Units (ACUs). Aurora Serverless v2 measures capacity in ACUs where each ACU is a combination of approximately 2 gibibytes (GiB) of memory, corresponding CPU, and networking. You specify the capacity range and the database scales within this range to support your application’s needs.\n With higher maximum capacity, customers can now use Aurora Serverless for even more demanding workloads. Instead of scaling up to 128 ACUs (256 GiB), the database can now scale up to 256 ACUs (512 GiB). You can get started with higher capacity with a new cluster or your existing cluster with just a few clicks in the AWS Management console. For a new cluster, select the desired capacity for the maximum capacity setting. For existing clusters, select modify and update the maximum capacity setting. For existing incompatible instances that don’t allow capacity higher than 128 ACUs, add a new reader with the higher capacity to the existing cluster and failover to it. 256 ACUs is supported for Aurora PostgreSQL 13.13+, 14.10+, 15.5+, 16.1+, and Aurora MySQL 3.06+. Aurora Serverless is an on-demand, automatic scaling configuration for Amazon Aurora. It adjusts capacity in fine-grained increments to provide just the right amount of database resources for an application’s needs. For pricing details and Region availability, visit Amazon Aurora Pricing. To learn more, read the documentation, and get started by creating an Aurora Serverless v2 database using only a few steps in the AWS Management Console.

Auto Scaling in AWS Glue interactive sessions is now generally available

Auto Scaling in AWS Glue interactive sessions is now generally available. AWS Glue interactive sessions with Glue versions 3.0 or higher can now dynamically scale resources up and down based on the workload. With Auto Scaling, you no longer need to worry about over-provisioning resources for sessions, spend time optimizing the number of workers, or pay for idle workers.\n AWS Glue is a serverless data integration service that allows you to schedule and run data integration and extract, transform, and load (ETL) jobs or sessions without managing any computing infrastructure. AWS Glue allows users to configure the number of works and type of workers to utilize. AWS Glue Auto Scaling monitors each stage of the session run and turns workers off when they are idle or adds workers if additional parallel processing is possible. This simplifies the process of tuning resources and optimizing costs.

This feature is now available in all commercial AWS Regions, GovCloud (US-West), and China Regions where AWS Glue interactive sessions is available.

For more details, please refer to the Glue Auto Scaling blog post and visit our documentation.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Big Data Blog

Containers

Desktop and Application Streaming

AWS DevOps & Developer Productivity Blog

AWS for Industries

AWS Machine Learning Blog

AWS for M&E Blog

AWS Security Blog

Open Source Project

AWS CLI

Amplify for JavaScript

Amplify for iOS

Firecracker