10/24/2024, 12:00:00 AM ~ 10/25/2024, 12:00:00 AM (UTC)

Recent Announcements

Amazon RDS for Oracle now supports Oracle Application Express (APEX) Version 24.1

Amazon Relational Database Service (RDS) for Oracle now supports version 24.1 of Oracle Application Express (APEX) for 19c and 21c versions of Oracle Database. Using APEX, developers can build applications entirely within their web browser. To learn more about the latest features of APEX 24.1, please refer to Oracle’s documentation.\n For more details on supported APEX versions and how to add or modify APEX options for your RDS for Oracle database, please refer to the Amazon RDS for Oracle APEX Documentation. See Amazon RDS for Oracle Database Pricing for regional availability.

AWS Deadline Cloud now sends Job, Step, and Task related events

Today, AWS Deadline Cloud announces new event types delivered via Amazon EventBridge that allow you to trigger workflows as your jobs progress and complete. AWS Deadline Cloud is a fully managed service that simplifies render management for teams creating computer-generated 2D/3D graphics and visual effects for films, TV shows, commercials, games, and industrial design.\n The new events are sent when jobs, steps, and tasks change status, allowing you to build systems that react to job activity. For example, by invoking a Lambda function from these events, you can:

Publish a notification to Slack when a job fails

Automatically update a project tracking tool with job progress

Sync the outputs from a job to another location when jobs succeed

The new events are available in all AWS Regions where Deadline Cloud is available. For more information, please visit the Deadline Cloud product page and the Deadline Cloud User Guide.

Amazon Redshift Serverless is now available in the AWS GovCloud (US) Regions

Amazon Redshift Serverless, which allows you to run and scale analytics without having to provision and manage data warehouse clusters, is now generally available in the AWS GovCloud (US) Regions. With Amazon Redshift Serverless, all users, including data analysts, developers, and data scientists, can use Amazon Redshift to get insights from data in seconds. Amazon Redshift Serverless automatically provisions and intelligently scales data warehouse capacity to deliver high performance for all your analytics. You only pay for the compute used for the duration of the workloads on a per-second basis. You can benefit from this simplicity without making any changes to your existing analytics and business intelligence applications.\n With a few clicks in the AWS Management Console, you can get started with querying data using the Query Editor V2 or your tool of choice with Amazon Redshift Serverless. There is no need to choose node types, node count, workload management, scaling, and other manual configurations. You can create databases, schemas, and tables, and load your own data from Amazon S3, access data using Amazon Redshift data shares, or restore an existing Amazon Redshift provisioned cluster snapshot. With Amazon Redshift Serverless, you can directly query data in open formats, such as Apache Parquet, in Amazon S3 data lakes. Amazon Redshift Serverless provides unified billing for queries on any of these data sources, helping you efficiently monitor and manage costs. To get started, see the Amazon Redshift Serverless feature page, user documentation, and API Reference.

Amazon SES now provides TLS Version for Outgoing Messages within AutoTags

Today, Amazon Simple Email Service (SES) released a feature which gives customers visibility into the Transport Layer Security (TLS) version used in the messages sent through SES. Customers can track email sending at a granular level by publishing email sending events to various AWS services such as Amazon CloudWatch. Customers can also categorize their emails by using message tags defined in configuration sets. This feature adds a new auto-tag to the existing set of auto-tags that SES automatically applies, in addition to the message tags specified by customers.\n Previously, SES generated auto-tags such as “ses:source-tls-version” to identify TLS protocol version used by the caller to send the email. However, customers did not have a way to determine the TLS version used by SES to send the email. Now, SES includes the “ses:outgoing-tls-version” auto-tag, which contains the TLS protocol version that SES used to send the email. Customers can leverage this new auto-tag to better understand and monitor the TLS version used when SES sends emails to mailbox providers that do not support the latest versions of TLS. SES supports “ses:outgoing-tls-version” in all AWS regions where Amazon SES is offered. For more information, see the documentation for SES event publishing.

AWS Lambda now supports using a custom serializer with Java runtimes

AWS Lambda now supports replacing the default Java object serialization library with a customer-defined serializer. This feature is supported in all current Lambda managed runtimes and container base images for Java.\n The ability to replace the default Java serializer enables customers to adapt their Lambda functions to cases where the incoming event format is not compatible with the default Lambda serializer. For example, to map a JSON event object whose properties are not in camel case such as ‘vehicle-type’ to a standard camel-cased field in a Java object. This feature is available in all commercial AWS Regions where Lambda is supported, the AWS GovCloud (US) Regions, and the China Regions. For more information, and to get started, see the Lambda documentation.

AWS announces EFA update for scalability with AI/ML applications

AWS announces the launch of a new interface type that decouples the Elastic Fabric Adapter (EFA) from the Elastic Network Adapter (ENA). EFA provides high-bandwidth, low-latency networking crucial for scaling AI/ML workloads. The new interface, “EFA-only”, allows you to create a standalone EFA device on secondary interfaces. This allows you to scale your compute clusters to run AI/ML applications without straining your private IPv4 address space or encountering IP routing challenges associated with Linux.\n Previously, each EFA interface was coupled with an ENA device, which consumed an IP address. This could result in a scaling limit for growing AI/ML model training jobs. Linux could also introduce routing challenges when multiple interfaces with private IPs were used, such as packet drops because of source IP mismatch and host name mapping problems. EFA-only interfaces solve these challenges as the EFA device is not assigned an IP address because it uses the Scalable Reliable Datagram (SRD) protocol, which operates over MAC addresses. EFA-only interfaces can only be configured as a secondary interface, with the primary interface being either EFA coupled with ENA or just ENA, since ENA is required for TCP/IP VPC routing. EFA-only is available on all EFA supported instances in all AWS Regions, including the AWS GovCloud (US) Regions and the AWS China Regions. You can enable EFA at no additional cost to run your AI/ML workloads at scale. To learn more, see the EFA documentation.

Announcing pro forma budgets integration for AWS Billing Conductor

Starting today, AWS Billing Conductor (ABC) customers can monitor their pro forma spend and be alerted when exceeding their desired pro forma spending limit. AWS Partners can use the feature to enable their customers to create budgets based on their usage priced at pro forma rates, which reflect the customer’s specific pricing agreement.\n The primary account of a billing group can create budgets and budget forecast, for the entire billing group or for a subset of accounts in the billing group. Non-primary accounts in an ABC billing group can create and view proforma budgets for their own accounts. When accounts join a billing group, their existing budgets will start to capture pro forma billing data. When accounts leave a billing group, the budget will start to capture billable billing data.

This release is available in all commercial AWS Regions, excluding the Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD.

To learn more about this feature integration, visit the AWS Billing Conductor product page, or review the User Guide and API Reference.

YouTube

AWS Black Belt Online Seminar (Japanese)

AWS Blogs

AWS Japan Blog (Japanese)

AWS Cloud Operations Blog

AWS Big Data Blog

AWS Contact Center

AWS Database Blog

AWS for Industries

AWS Machine Learning Blog

AWS Messaging & Targeting Blog

AWS Security Blog

Open Source Project

AWS CLI

AWS CDK

Bottlerocket OS

Amazon EKS Anywhere