12/23/2024, 12:00:00 AM ~ 12/24/2024, 12:00:00 AM (UTC)
Recent Announcements
AWS Neuron introduces support for Trainium2 and NxD Inference
Today, AWS announces the release of Neuron 2.21, introducing support for AWS Trainium2 chips and Amazon EC2 Trn2 instances, including the trn2.48xlarge instance type and Trn2 UltraServer. This release also adds support for PyTorch 2.5 and introduces NxD Inference and Neuron Profiler 2.0 (beta). NxD Inference, is a new PyTorch-based library integrated with vLLM, simplifies the deployment of large language and multi-modality models and enables PyTorch model onboarding with minimal code changes, and Neuron Profiler 2.0 (beta), is new profiler that enhances capabilities and usability, including support for distributed workloads.\n Neuron 2.21 also introduces Llama 3.1 405B model inference support using NxD Inference on a single trn2.48xlarge instance. The release updates Deep Learning Containers (DLCs) and Deep Learning AMIs (DLAMIs), and adds support for various model architectures, including Llama 3.2, Llama 3.3, and Mixture-of-Experts (MoE) models. New inference features include FP8 weight quantization and flash decoding for speculative decoding in Transformers NeuronX (TNx). Additionally, new training examples and features have been added, such as support for HuggingFace Llama 3/3.1 70B on Trn2 instances and DPO support for post-training model alignment. AWS Neuron SDK supports training and deploying models on Trn1, Trn2, and Inf2 instances, available in AWS Regions as On-Demand Instances, Reserved Instances, Spot Instances, or part of Savings Plan. For a full list of new features and enhancements in Neuron 2.21 and to get started with Neuron, see:
AWS Neuron
Trn2 Instances
Trn1 Instances
Inf2 Instances
AWS Systems Manager for SAP includes capabilities to now support registration of SAP NetWeaver ABAP-based applications, deployed in distributed and Highly Available (HA) topologies. This enhancement covers a wide range of applications, including S/4HANA and BW/4HANA, and extends support to additional application servers and web dispatcher components. With this launch, customers can automate start and stop operations for ABAP based SAP applications running on distributed and HA architectures. This new functionality simplifies the management of complex SAP landscapes, improves operational efficiency through automation, and provides enhanced support for high-availability configurations.\n AWS Systems Manager for SAP is an automation capability to manage and operate your SAP applications on AWS. It provides a seamless integration between AWS services and SAP applications running on AWS. Registering SAP applications to AWS Systems Manager for SAP allows automation such as enabling backup, start/stop for the applications and associated EC2 instances. In addition, as part of the SSM Application Manager console integration, customers can get details of the resources being consumed by the SAP applications such as EC2 instances, EBS volumes and the associated costs incurred at an application level. AWS Systems Manager for SAP is available in all commercial regions. To learn about the key features, check out the product documentation page. To learn why thousands of SAP customers trust AWS, visit the SAP on AWS page.
AWS announces notification actions in the AWS Console Mobile App for iOS
Today, Amazon Web Services (AWS) is announcing the general availability of notification actions in the AWS Console Mobile Application for iOS. Notification action buttons are displayed on the notification details screen when you receive a push notification from AWS User Notifications on your mobile device. AWS customers can take actions like view logs, start, stop, or reboot an EC2 instance on an event notification to shorten incident response diagnosis and resolution times.\n With notification actions, you can quickly run common DevOps tasks based on your IAM permissions using notification action buttons. Notification actions are displayed automatically on notifications based on the state of the AWS resource. Using notification actions for event notifications, you can restart an EC2 instance the moment you receive an EC2 instance terminated push notification on your mobile device or get more information about an event notification without needing to return to your computer. The Console Mobile App lets users view and manage a select set of resources to stay informed and connected with their AWS resources while on-the-go. Visit the product page for more information about the Console Mobile Application.
Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, now offers customers the option to collect metrics from an Amazon Elastic Kubernetes Service clusters using Internet Protocol version 6 (IPv6) in a dual stack VPC setup.\n The continued growth of the internet is exhausting available Internet Protocol version 4 (IPv4) addresses. IPv6 increases the number of available addresses by several orders of magnitude so customers will no longer need to manage overlapping address spaces in their VPCs. Customers can now use the managed service to collect IPv6 Prometheus metrics endpoints in Amazon Elastic Kubernetes Service clusters. To learn more on best practices for configuring IPv6 in your environment, visit the white paper on IPv6 in AWS. Support for IPv6 on Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is GA. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.
AWS CloudTrail now supports Internet Protocol Version 6 (IPv6)
AWS CloudTrail introduces dual stack support for the CloudTrail API endpoints, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when you privately access the CloudTrail API endpoint from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink.\n The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on CloudTrail endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6 To learn more on best practices for configuring IPv6 in your environment, visit the whitepaper on IPv6 in AWS. Support for IPv6 on AWS CloudTrail is available in all commercial regions and the AWS GovCloud (US) Regions.
Amazon MSK now extends support for Graviton3 based M7G instances in Europe (Paris) region
You can now create Amazon Managed Streaming for Apache Kafka (Amazon MSK) provisioned clusters running on AWS Graviton3-based M7g instances or upgrade your existing x-86 based based M5 or T3 instances and replace them with AWS Graviton3-based M7G instances with a single click of a button in the Europe (Paris) AWS Region.\n AWS Graviton3 processor based M7G instances on Amazon MSK provisioned clusters allows you to achieve up to 24% compute cost savings and up to 29% higher write and read throughput over comparable MSK clusters running on M5 instances. Additionally, these instances lower energy consumption by up to 60% than comparable instances, making your Kafka clusters more environmentally sustainable. Please refer to our blog for more information on the price/ performance improvements of M7g instances and the Amazon MSK pricing page for information on pricing. To get started, you can create new clusters using M7G instances or update your existing clusters to M7G brokers using the AWS Management Console, and read our developer guide for more information.
Amazon Lightsail API endpoints now support connectivity over Internet Protocol version 6 (IPv6)
Amazon Lightsail API endpoints now support the IPv6 protocol, allowing you to connect over IPv6. To use this new capability, point your applications to use Amazon Lightsail’s new dual-stack endpoints. When you make a request to a dual-stack endpoint, the endpoint URL resolves to an IPv6 or an IPv4 address, depending on the protocol used by your network and client.\n Public IPv4 addresses are being exhausted with the growth of the Internet. Earlier this year, Lightsail launched IPv6-only instance plans to support IPv6 adoption. With the introduction of dual-stack Lightsail API endpoints, you can now make requests to the Lightsail API from your Lightsail IPv6-only instances, or any IPv6 client. You can use this capability with the AWS Command Line Interface (CLI) and AWS SDKs in all AWS Regions supporting Lightsail. To learn more, please see AWS Service Endpoints documentation and Lightsail Service Endpoints documentation.
Amazon Bedrock Agents, Flows, and Knowledge Bases now supports Latency Optimized Models
Amazon Bedrock Agents, Flows, and Knowledge Bases now offers support for the recently announced, in-preview, latency-optimized models via the SDK. This enhancement brings faster response times and improved responsiveness to AI applications built with Amazon Bedrock Tooling. Currently, this optimization is available for Anthropic’s Claude 3.5 Haiku model and Meta’s Llama 3.1 405B and 70B models, delivering reduced latency compared to standard models without compromising accuracy.\n This update is particularly beneficial for customers developing latency-sensitive applications such as real-time customer service chatbots and interactive coding assistants. By leveraging purpose-built AI chips like AWS Trainium2 and advanced software optimizations in Amazon Bedrock, customers can now access more options to optimize their inference for specific use cases. Importantly, these capabilities can be integrated immediately into existing applications without additional setup or model fine-tuning, resulting in enhanced performance and faster response times. The latency-optimized inference support for Amazon Bedrock Agents, Flows, and Knowledge Bases is available in the US East (Ohio) Region via cross-region inference. Customers can access these new capabilities through the Amazon Bedrock SDK via a runtime configuration, enabling them to programmatically incorporate these optimized models into their workflows and applications. To learn more about Amazon Bedrock and its capabilities, including this new latency-optimized inference support, visit the Amazon Bedrock product page, pricing page, and documentation.
New Guides on AWS Partner Central
AWS has launched new Guides on AWS Partner Central providing detailed resources with step-by-step guidance on AWS Partner Network and Marketplace topics. The new guides provide introductory and advanced resources for every stage of your AWS journey, giving you the guidance you need to move up and across the AWS Partner Profitability Framework. In addition, guides provide enablement materials for Managed Service Provider, Solution Provider and ISV Accelerate Program, guidance on using AWS Co-sell Experience (ACE) and AWS Partner Funding Portal (APFP), and information on key topics, such as Generative AI and migration and modernization. These improvements provide Partners with structured, actionable information and quick access to resources, making it easier to navigate their AWS partnership.\n Partners can access guides in AWS Partner Central while completing assigned Tasks or by using Partner Assistant, the generative AI virtual assistant. From Task descriptions or Partner Assistant responses, partners can navigate directly to relevant guides for in-depth information and related resources. This integrated experience helps partners to find answers quickly, progress through their AWS Partner journey more efficiently and unlock benefits faster. Guides are available to all partners. To get started, log into AWS Partner Central, navigate to the “Resources” menu, and select “Guides”. Learn more about becoming an AWS Partner.
SES Mail Manager now supports full lifecycle logging
SES Mail Manager now offers end to end logging for ingress endpoints and rules engine actions. Customers have the ability to configure a wide range of monitoring options to the three standard logging destinations: CloudWatch, S3, and Firehose.\n Mail Manager by design interoperates with external systems on both incoming and outgoing email flows. Customers expect to use it to gain visibility on email volumes as well as to troubleshoot configuration problems at every step in the email delivery paths. These new logging features enable both ad hoc investigations and automated alarming via standard CloudWatch tooling, ensuring that the overall integrity of Mail Manager configurations can be tracked programmatically alongside other customer infrastructure. The logging features also help troubleshooting in the event of a configuration change on a connected system, reducing the support burden and enabling more customer self-service solutions. Mail Manager logging is available in every AWS Region where Mail Manager is launched. Customers can learn more about Mail Manager by clicking here.
Amazon Connect launches support for routing to a specific range of agent proficiencies
Amazon Connect now offers the ability to target a range of agent proficiency levels, such as from levels 1 to 3 for French. You can ensure each contact is matched to an agent with the right skill level to handle it, resulting in reduced contact transfers and lower handle times. You can assign simpler contacts to new hires while reserving your tenured agents for the difficult contacts that require their knowledge and expertise.\n This feature is available in all AWS regions where Amazon Connect is offered. To learn more about routing criteria, see the Amazon Connect Administrator Guide. To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website.
Amazon Connect offers the ability to exclude certain proficiencies during routing
Amazon Connect now offers the ability to exclude certain proficiencies from consideration when using routing criteria for routing. You can use this to exclude or reserve niche skills. For example, you can exclude dual-skilled Spanish and English speaking agents from English language contacts to reserve them for contacts in Spanish. You can include the dual-skilled agents when required by removing the exclusion condition.\n This feature is available in all AWS regions where Amazon Connect is offered. To learn more about routing criteria, see the Amazon Connect Administrator Guide. To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website.
AWS Blogs
AWS Japan Blog (Japanese)
- University ICT Promotion Council 2024 Annual Conference (AXIES 2024) Exhibition/Presentation Report
- Weekly Generative AI with AWS — Week 2024/12/16
- AWS Weekly — 2024/12/16
- Amazon Q Developer Agent for VMware workload transformation
- Threat modeling to assess security risk for generative AI workloads
AWS Japan Startup Blog (Japanese)
AWS Big Data Blog
AWS Database Blog
- Comparison of test_decoding and pglogical plugins in Amazon Aurora PostgreSQL for data migration using AWS DMS
- Enhance the reliability of airlines’ mission-critical baggage handling using Amazon DynamoDB
- Enhancing performance of Amazon RDS for Oracle with NVMe SSD hosted Smart Flash Cache and Temporary Tablespaces
AWS for Industries
AWS Machine Learning Blog
- Using transcription confidence scores to improve slot filling in Amazon Lex
- Improving Retrieval Augmented Generation accuracy with GraphRAG