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

Recent Announcements

Amazon AppStream 2.0 users can now save their user preferences between streaming sessions

Amazon AppStream 2.0 now enables end users to save their client preferences when streaming through a web browser or AppStream 2.0 client application for Windows. These preferences will be applied automatically when the user connects again using the same client, helping to provide consistent experience across sessions.\n Users can now customize and save AppStream 2.0 client preferences across sessions when accessing from the same client. These preferences include audio (microphone), video (webcam), regional settings, and streaming mode, and macOS keyboard mappings. Previously, users had to manually re-adjust these settings during each session. By persisting personalized settings across sessions, AppStream 2.0 helps provide a more consistent and efficient user experience. The functionality is available in AppStream 2.0 Windows client version 1.1.1403 and later, as well as in all supported web browsers. To download and install the latest client, visit Amazon AppStream 2.0 Downloads.

Amazon EC2 instances support bandwidth configurations for VPC and EBS

AWS announces the general availability of Instance Bandwidth Configurations (IBC) for 8th generation, Graviton based instances. With IBC, customers can adjust the VPC and EBS service bandwidth, by up to 25%, on their EC2 instances. When increasing the bandwidth for one of the service, say VPC, the available bandwidth for the other service, EBS, is reduced. IBC does not increase your instances burst bandwidth, packets per second, or IOPS capabilities.\n With IBC, AWS is providing customers greater flexibility with the allocation of their bandwidth resources to better optimize their workloads. Before today, EC2 instances were predefined with static bandwidth specifications, but now customers have more control over their resources. For storage and data analytics workloads, customers can use IBC to increase their VPC bandwidth allocation for improved performance replicating data or reading and writing data from services like Amazon Simple Storage Service (S3). For database workloads backing up data to EBS, customers can use IBC to increase their bandwidth allocation to improve querying and logging performance. IBC is available starting with C8g, M8g, R8g, and X8g platforms. It is available in all AWS commercial regions and it comes at no additional cost. To get started and learn more, please see our EC2 user guide.

AWS Elemental MediaConnect Gateway now supports source-specific multicast

AWS Elemental MediaConnect Gateway now supports source-specific multicast (SSM). This new feature allows you to specify both a multicast group address and an optional source IP address when creating or updating MediaConnect Gateway bridge sources, offering greater flexibility, security, and efficiency in your workflows.\n SSM support enhances control by allowing you to pull content from specific senders and filter unwanted traffic. It enables more efficient bandwidth use as network switches replicate data only when needed. Additionally, SSM improves security as content is only received from trusted sources via specified IP addresses. To learn more about enabling SSM for MediaConnect Gateway, visit the AWS Elemental MediaConnect Gateway documentation page. AWS Elemental MediaConnect is a reliable, secure, and flexible transport service for live video that enables broadcasters and content owners to build live video workflows and securely share live content with partners and customers. MediaConnect helps customers transport high-value live video streams into, through, and out of the AWS Cloud. MediaConnect can function as a standalone service or as part of a larger video workflow with other AWS Elemental Media Services, a family of services that form the foundation of cloud-based workflows to transport, transcode, package, and deliver video. Visit the AWS Region Table for a full list of AWS Regions where MediaConnect is available. To learn more about MediaConnect, please visit here.

AWS Resource Explorer supports 59 new resource types

AWS Resource Explorer now supports 59 more resource types across all AWS commercial Regions from services including Amazon Elastic Kubernetes Service (Amazon EKS), Amazon Kendra, AWS Identity and Access Management (IAM) Access Analyzer, and Amazon SageMaker.\n With this release, customers can now search for the following resource types in AWS Resource Explorer:  

access-analyzer:analyzer

airflow:environment

amplify:apps/branches

amplify:apps/domains

appflow:flow

appmesh:mesh

appmesh:mesh/virtualNode

appmesh:mesh/virtualService

apprunner:service

appstream:image-builder

auditmanager:assessment

backup:backup-vault

codeguru-reviewer:association

connect:instance

connect:instance/transfer-destination

connect:instance/agent

databrew:schedule

datasync:location

datasync:task

dms:endpoint

dms:rep

dms:task

ecs:capacity-provider

eks:cluster

finspace:environment

gamelift:build

gamelift:gamesessionqueue

gamelift:matchmakingconfiguration

gamelift:matchmakingruleset

glue:mlTransform

groundstation:config

guardduty:detector/filter

guardduty:detector/ipset

guardduty:detector/threatintelset

healthlake:datastore/fhir

iotsitewise:dashboard

iotwireless:ServiceProfile

ivs:recording-configuration

kendra:index

memorydb:acl

memorydb:subnetgroup

network-firewall:firewall

networkmanager:attachment

mobiletargeting:apps/campaigns

mobiletargeting:apps/segments

proton:environment-account-connection

quicksight:dataset

quicksight:datasource

quicksight:template

ram:resource-share

route53resolver:resolver-query-log-config

sagemaker:domain

sagemaker:endpoint

sagemaker:feature-group

sagemaker:image

sagemaker:pipeline

signer:signing-profiles

transfer:workflow

workspaces:workspace

To view a complete list of all supported types, see the supported resource types page.

AWS Cloud Map now supports Service Level Attributes

AWS Cloud Map now supports service-level attributes, enabling you to store and access information directly at the service level. With AWS Cloud Map, you can define custom names for your application resources, such as Amazon Elastic Container Services (Amazon ECS) tasks, Amazon Elastic Compute Cloud (Amazon EC2) instances, Amazon DynamoDB tables, or other cloud resources. You can then use these custom names to discover the location of cloud resources from your applications using AWS SDK and authenticated API queries. With service-level attributes, your applications can store and retrieve important service-level information, such as traffic weights during deployments, through a simple API call to AWS Cloud Map. AWS Cloud Map service is a logical group of instances, enabling you to find and connect to resources.\n With AWS Cloud Map support for service-level attributes, you can now register key value attributes directly at service level, which were previously stored at the instance level or retrieved through ad-hoc channels like static config files. This feature allows you to discover resources using service-level attributes for various use cases, such as complex traffic routing, setting timeout and retry values, and coordination between services and external integrations. This capability helps you avoid duplicating service level information across instances, simplifying retrieval, updates, and deletion without requiring changes to individual instances. To learn more, please refer to the AWS Cloud Map documentation. To see all of the Regions where AWS Cloud Map is available, see the AWS Region table.

AWS announces new AWS Direct Connect location in Osaka, Japan

Today, AWS announced the opening of a new AWS Direct Connect location within the Telehouse OS2 data center in Osaka, Japan. By connecting your network to AWS at the new Osaka location, you gain private, direct access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones. This is the second AWS Direct Connect site within the Osaka Metropolitan area and the fifth site in Japan.\n The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet. The new Direct Connect location at Telehouse OS2 offers dedicated 1G, 10 Gbps and 100 Gbps connections with MACsec encryption available. For more information on the over 145 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.

Amazon DynamoDB announces support for FIPS 140-3 interface VPC and Streams endpoints

Amazon DynamoDB is a serverless, NoSQL, fully managed database with single-digit millisecond performance at any scale. The Federal Information Processing Standard (FIPS) Publication 140-3 is a US and Canadian government standard that specifies the security requirements for cryptographic modules that protect sensitive information. Today, we are announcing the general availability of FIPS 140-3 interface endpoint support for DynamoDB and FIPS 140-3 public endpoint support for DynamoDB Streams.\n You can use AWS PrivateLink with DynamoDB for regulated workloads that require a secure connection using a FIPS 140-3 validated cryptographic module. FIPS-compliant endpoints help companies contracting with the federal government meet the FIPS security requirement to encrypt sensitive data in supported Regions. The new capability is available in AWS Regions in the United States and Canada, and the AWS GovCloud (US) Regions. Learn more about AWS FIPS 140-3 at FIPS 140-3 Compliance.

Amazon Redshift supports auto and incremental refresh of Materialized Views for zero-ETL integrations

Today, Amazon Redshift announced the support for automatically and incrementally refreshable materialized views (MVs) on tables in a zero-ETL integration. This new feature eliminates the need for full refreshes, which previously required re-executing underlying select statements and rewriting all data in the MV.\n With this launch, you can leverage the power of zero-ETL integrations with automatically and incrementally refreshable MVs, enabling more efficient data updates and faster query responses. This feature automatically keeps MVs up-to-date as the underlying data changes, eliminating the need for manual refresh operations or complex ETL processes. Organizations handling high-volume, dynamic datasets can now access near real-time insights while significantly reducing their operational workload. To learn more and get started with zero-ETL integration, visit the getting started guides for Amazon Redshift. To learn more about refreshing a materialized view, visit the documentation.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Database Blog

AWS for Industries

AWS Machine Learning Blog

AWS for M&E Blog

AWS Messaging & Targeting Blog

AWS Security Blog

Open Source Project

AWS CLI

AWS CDK

Amplify for JavaScript

Amplify UI

Amazon EKS Anywhere