8/15/2024, 12:00:00 AM ~ 8/16/2024, 12:00:00 AM (UTC)

Recent Announcements

Amazon VPC Lattice is now available in 7 additional Regions

Amazon VPC Lattice is now available in 7 additional AWS Regions: Africa (Cape Town), Europe (Milan), Europe (Paris), Asia Pacific (Mumbai), Asia Pacific (Seoul), South America (São Paulo), and US West (N. California).\n Amazon VPC Lattice is an application networking service that simplifies connecting, securing, and monitoring service-to-service communication. You can use Amazon VPC Lattice to facilitate cross-account and cross-VPC connectivity, as well as application layer load balancing for your workloads in a consistent way regardless of the underlying compute type – instances, containers, and serverless. With this launch, Amazon VPC Lattice is now generally available in 18 AWS regions. Please visit the AWS region table for more information on AWS regions and services. To learn more, visit the Amazon VPC Lattice homepage, Amazon VPC Lattice User Guide, Frequently Asked Questions, and browse the most recent VPC Lattice blog posts here.

Announcing AWS Support Official channel on AWS re:Post

Today, AWS announces the launch of the AWS Support Official channel on AWS re:Post. AWS customers now have access to curated content for operating at scale on AWS, authored by AWS Support and AWS Managed Services (AMS) experts. In this new channel, you can find technical solutions for complex problems, operational best practices, and insights into AWS Support and AMS offerings.\n AWS re:Post provides access to curated knowledge and a vibrant community. With this launch, you now have a dedicated channel in re:Post for specialized AWS Support and AMS knowledge to solve real-world problems, with detailed walkthroughs, deep dives, and industry-specific best practices. You’ll gain insight into using AWS services, troubleshooting at scale, and optimizing costs, and be the first to know about new features and offerings from AWS Support and AMS. AWS Support Official articles are authored by experts who work with many of the largest customers on AWS to solve issues, create sustainable architectures, and establish scalability to help you innovate and operate on AWS. The AWS Support Official channel is available globally on re:Post in English. To learn more, visit the AWS Support Official channel on re:Post. For more information on how AWS Support plans can help you accelerate business outcomes in the cloud on AWS, visit AWS Support.

Digital twin is now generally available for AWS Ground Station

Amazon Web Services (AWS) announces the general availability of the digital twin feature for AWS Ground Station, which provides virtualized ground station infrastructure that allows you to perform space-to-ground compatibility testing. AWS Ground Station is a fully managed service that lets you control satellite communications, process data, and scale your operations without having to worry about building or managing your own ground station infrastructure. With this new feature, you can now more quickly and easily integrate your satellite communication and scheduling workflows with AWS Ground Station.\n The digital twin feature allows you to verify compatibility between your mission planning software and AWS Ground Station’s scheduling service in a virtual environment. Now, you can begin integration and testing without needing to wait for spectrum licensing approvals, allowing you to be ready in time for the launch of your satellite. An AWS Ground Station digital twin emits the same Amazon EventBridge events and API responses that customers receive when using AWS Ground Station, allowing you to fine-tune configurations and scale your infrastructure reliably. The digital twin feature for AWS Ground Station provides virtualized antennas at each location where AWS Ground Station is available, including: US East (Ohio), US West (Oregon, Hawaii, Alaska), Europe (Ireland, Stockholm), Middle East (Bahrain), Africa (Cape Town), Asia Pacific (Dubbo, Seoul, Singapore) and South America (Punta Arenas). This new feature is available in all AWS Regions where AWS Ground Station is available. To get your mission off the ground even faster, see AWS Ground Station digital twin in the AWS Ground Station User Guide.

Announcing general availability of Amazon EC2 G6e instances

Today we are announcing the general availability of Amazon EC2 G6e instances powered by NVIDIA L40S Tensor Core GPUs. G6e instances can be used for a wide range of machine learning and spatial computing use cases. G6e instances deliver up to 2.5x better performance compared to G5 instances and up to 20% lower inference costs than P4d instances.\n Customers can use G6e instances to deploy large language models (LLMs) with up to 13B parameters and diffusion models for generating images, video, and audio. Additionally, the G6e instances will unlock customers’ ability to create larger, more immersive 3D simulations and digital twins for spatial computing workloads. G6e instances feature up to 8 NVIDIA L40S Tensor Core GPUs with 384 GB of total GPU memory (48 GB of memory per GPU) and third generation AMD EPYC processors. They also support up to 192 vCPUs, up to 400 Gbps of network bandwidth, up to 1.536 TB of system memory, and up to 7.6 TB of local NVMe SSD storage. Developers can run AI inference workloads on G6e instances using AWS Deep Learning AMIs, AWS Deep Learning Containers, or managed services such as Amazon Elastic Kubernetes Service (Amazon EKS) and AWS Batch, with Amazon SageMaker support coming soon.

Amazon EC2 G6e instances are available today in the AWS US East (N. Virginia and Ohio) and US West (Oregon) regions. Customers can purchase G6e instances as On-Demand Instances, Reserved Instances, Spot Instances, or as part of Savings Plans. To get started, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the G6e instance page.

AWS CodeBuild now supports using GitHub Apps to access source repositories

AWS CodeBuild now integrates with GitHub Apps as the authentication method to access your repositories. A GitHub App connection can be set as the default authentication method for all projects, or can be specified for an individual project source.\n With GitHub Apps, you can use short-lived tokens with fine-grained permissions, and have control over which repositories the app can access. In a CodeBuild project, GitHub App connections are established via AWS CodeConnections, where you can further limit the access to the connections by using IAM roles and resource policies. The new feature is available in all regions where AWS CodeBuild is supported except in China (Beijing), China (Ningxia). For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page. To get started, create a GitHub App connection and configure it in your CodeBuild project . To learn more about how CodeBuild connects to your repositories, see access your source provider in CodeBuild.

AWS Control Tower launches landing zone version selection

AWS Control Tower customers can now select from a set of versions when performing a landing zone update, reset, or upgrade operation. Starting with landing zone version 3.1 and above, customers can update or reset in-place their landing zone on their current version, or upgrade to a version of their choice. A landing zone is a well-architected, multi-account AWS environment based on security and compliance best practices. AWS Control Tower automates the setup of a new landing zone using best-practices blueprints for identity, federated access, logging, and account structure.\n With landing zone version selection, customers have more flexibility to plan for version upgrades while they evaluate potential changes to their environment. Customers need not choose between resetting drift to stay in compliance, updating their landing zone configurations, or upgrading to the latest landing zone version. If customers are running landing zone version 3.1 or above, they can choose to stay on the current version, or upgrade to a newer version, when they update or reset their landing zone configurations. For a full list of Regions where AWS Control Tower is available, see the AWS Region Table. To learn more, visit the AWS Control Tower homepage or see the AWS Control Tower User Guide.

AWS CodeBuild now supports multiple access tokens via AWS Secrets Manager

AWS CodeBuild now supports configuring multiple access tokens for each source provider. You can store your OAuth or personal access tokens in AWS Secrets Manager, and specify them in CodeBuild projects. This feature is available for your GitHub, GitHub Enterprise and Bitbucket source repositories.\n With multiple access tokens, you can use different tokens with scoped down permissions for each of your projects. Configuring tokens in Secrets Manager enables you to audit the token access using CloudTrail logs, and set IAM roles and resource policies to limit who can access these tokens. This feature is available in all regions where CodeBuild is offered. For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page. To get started, create a Secrets Manager secret with your access token and configure it in your CodeBuild project. To learn more about how CodeBuild connects to your repositories, see access your source provider in CodeBuild.

Amazon ECS provides the ability to restart containers without requiring a task relaunch

Amazon Elastic Container Services (Amazon ECS) now improves container resiliency by giving you the ability to define a flexible container restart policy for restarting individual containers locally, without requiring a full task relaunch. With local container restarts, Amazon ECS can recover your containers from unexpected failures within a few seconds, enhancing your overall task stability by avoiding unnecessary task relaunches.\n Amazon ECS now provides automated container restarts in-place to recover your containers from transient failures such as network disruption or cases where your containers stop unexpectedly. For containers for which you want to have some fault tolerance where a restart can clear an indeterminate condition, like data loggers, collectors or forwarders, you can create a policy to restart on error codes and recover much faster than you would if you were to relaunch the whole task, including any mission critical or customer facing applications. The new experience is now enabled in all AWS Regions. To learn more about how to set up your Amazon ECS container restart policy parameters, see the Amazon ECS Developer Guide.

AWS Blogs

AWS Japan Startup Blog (Japanese)

AWS Cloud Financial Management

AWS Cloud Operations & Migrations Blog

AWS Big Data Blog

AWS Developer Tools Blog

AWS for Industries

AWS Machine Learning Blog

AWS for M&E Blog

AWS Messaging & Targeting Blog

Networking & Content Delivery

Open Source Project

AWS CLI

AWS CDK

Amplify for JavaScript

Amazon Chime SDK React Components Library

Amazon EKS Anywhere