Amazon DocumentDB (with MongoDB compatibility) is Now Available in the Asia Pacific (Jakarta) Region

Amazon DocumentDB (with MongoDB compatibility) is now available in the Asia Pacific (Jakarta) region adding to the list of available regions where you can use Amazon DocumentDB. Amazon DocumentDB is a fully managed, native JSON database that makes it simple and cost-effective to operate critical document workloads at virtually any scale without managing infrastructure. Amazon DocumentDB is designed to give you the scalability and durability you need when operating mission-critical MongoDB workloads. Storage scales automatically up to 128TiB without any impact to your application. In addition, Amazon DocumentDB natively integrates with AWS Database Migration Service(DMS), Amazon CloudWatch, AWS CloudTrail, AWS Lambda, AWS Backup and more. Amazon DocumentDB supports millions of requests per second and can be scaled out to 15 low latency read replicas in minutes with no application downtime. To learn more about Amazon DocumentDB, please visit the Amazon DocumentDB product page and pricing page. You can create a Amazon DocumentDB cluster from the AWS Management console, AWS Command Line Interface (CLI), or SDK.
Quelle: aws.amazon.com

Announcing Apache Airflow 2.11 Support in Amazon Managed Workflows for Apache Airflow

You can now create Apache Airflow version 2.11 environments on Amazon Managed Workflows for Apache Airflow (MWAA). Apache Airflow 2.11 introduces several changes to help you prepare for upgrading to Apache Airflow 3.  Amazon MWAA is a managed orchestration service for Apache Airflow that makes it easier to set up and operate end-to-end data pipelines in the cloud. Apache Airflow 2.11 introduces several notable enhancements, such as new trigger-based scheduling for delta intervals, consistent reporting of metrics in milliseconds and other changes that will make it easy to migrate to Apache Airflow 3. In addition, MWAA now provides support for Python 3.12 that you can leverage in your workflows. You can launch a new Apache Airflow 2.11 environment on Amazon MWAA with just a few clicks in the AWS Management Console in all currently supported Amazon MWAA regions. To learn more about Apache Airflow 2.11 visit the Amazon MWAA documentation, and the Apache Airflow 2.11 change log in the Apache Airflow documentation. Apache, Apache Airflow, and Airflow are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.
Quelle: aws.amazon.com

AWS simplifies Client VPN onboarding with Quickstart setup

Today, AWS announces a simplified onboarding experience for AWS Client VPN, introducing a new Quickstart setup method that streamlines the process of creating and configuring Client VPN endpoints. AWS Client VPN allows you to securely connect remote users to AWS resources and on-premises networks. The new Quickstart setup, reduces the number of steps required to set up an Client VPN endpoint. You can now easily set up Client VPN endpoints with pre-defined default configurations, requiring only three key inputs: IPv4 CIDR, server certificate ARN, and subnet selection. For example, development teams in large organizations who use Client VPN for remote access to their VPC resources for quick testing can now create endpoints quickly with the new simplified setup process. The Quickstart method is available alongside the existing Standard Setup option, giving you the flexibility to choose the approach that best fits your deployment needs. Additionally, when you create a VPC, the Client VPN Quickstart workflow is automatically suggested as a follow up step. Once endpoint creation is complete, you can immediately download the client configuration file to connect using your VPN client. You can later modify and enhance your endpoint configuration using the Client VPN standard console or API as your usage patterns evolve. This enhancement is available at no additional cost in all AWS Regions where AWS Client VPN is generally available. To learn more about Client VPN:

Visit the AWS Client VPN product page
Read the AWS Client VPN documentation

Quelle: aws.amazon.com

Amazon EC2 C8i and C8i-flex instances are now available in additional AWS regions

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C8i and C8i-flex instances are available in the Asia Pacific (Mumbai), Asia Pacific (Seoul), and Asia Pacific (Tokyo) regions. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. These C8i and C8i-flex instances offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% higher performance than C7i and C7i-flex instances, with even higher gains for specific workloads. The C8i and C8i-flex are up to 60% faster for NGINX web applications, up to 40% faster for AI deep learning recommendation models, and 35% faster for Memcached stores compared to C7i and C7i-flex. C8i-flex are the easiest way to get price performance benefits for a majority of compute intensive workloads like web and application servers, databases, caches, Apache Kafka, Elasticsearch, and enterprise applications. They offer the most common sizes, from large to 16xlarge, and are a great first choice for applications that don’t fully utilize all compute resources. C8i instances are a great choice for all memory-intensive workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. C8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications. To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information about the new C8i and C8i-flex instances visit the AWS News blog.
Quelle: aws.amazon.com

Amazon EC2 I7ie instances now available in additional AWS regions

AWS is announcing starting today, Amazon EC2 I7ie instances are now available in AWS Asia Pacific (Mumbai), Canada West (Calgary) and Europe (Paris) regions. Designed for large storage I/O intensive workloads, I7ie instances are powered by 5th Gen Intel Xeon Processors with an all-core turbo frequency of 3.2 GHz, offering up to 40% better compute performance and 20% better price performance over existing I3en instances. I7ie instances offer up to 120TB local NVMe storage density for storage optimized instances and offer up to twice as many vCPUs and memory compared to prior generation instances. Powered by 3rd generation AWS Nitro SSDs, I7ie instances deliver up to 65% better real-time storage performance, up to 50% lower storage I/O latency, and 65% lower storage I/O latency variability compared to I3en instances. I7ie are high density storage optimized instances, ideal for workloads requiring fast local storage with high random read/write performance at very low latency consistency to access large data sets. These instances are available in 9 different virtual sizes and deliver up to 100Gbps of network bandwidth and 60Gbps of bandwidth for Amazon Elastic Block Store (EBS). To learn more, visit the I7ie instances page.
Quelle: aws.amazon.com

Amazon MQ now supports HTTP based authentication for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ brokers to perform authentication (determining who can log in) and authorization (determining what permissions they have) by making requests to an HTTP server. This plugin can be configured on brokers running RabbitMQ 4.2 and above on Amazon MQ by making changes to the associated configuration file. To start using HTTP based authentication and authorization on Amazon MQ, simply select RabbitMQ 4.2 when creating a new broker using the m7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then edit the associated configuration file. To learn more about the plugin, see the Amazon MQ release notes and the Amazon MQ developer guide. This plugin is available in all regions where Amazon MQ RabbitMQ 4 instances are available today. 
Quelle: aws.amazon.com

AWS Marketplace Seller Reporting now provides collections visibility

Today, AWS announces collection visibility in AWS Marketplace Seller Reporting, which adds up-to-date payment collection status to the Billed Revenue Dashboard and Billing Event Data Feed. This enhancement enables sellers to distinguish between invoiced, collected, and disbursed amounts, eliminating the visibility gap between invoice creation and disbursement. With this feature, sellers can make informed business decisions and reduce unnecessary follow-ups with customers about payment status. Collection visibility particularly benefits sellers using monthly disbursement who previously waited up to 30 days to understand payment collection status. All AWS Marketplace sellers can now improve payment forecasting accuracy and detect collection issues earlier. This enhanced visibility streamlines seller operations and improves customer relationships by providing clarity on payment status. Collection visibility is available in all AWS Regions where AWS Seller Reporting is available. The feature launches on January 6th, 2026 for all AWS sellers. To access collection visibility, log into the AWS Marketplace Management Portal and navigate to Insights → Finance Operations
Quelle: aws.amazon.com

AWS Config now supports 21 new resource types

AWS Config now supports 21 additional AWS resource types across key services including Amazon EC2, Amazon SageMaker, and Amazon S3 Tables. This expansion provides greater coverage over your AWS environment, enabling you to more effectively discover, assess, audit, and remediate an even broader range of resources. With this launch, if you have enabled recording for all resource types, then AWS Config will automatically track these new additions. The newly supported resource types are also available in Config rules and Config aggregators. You can now use AWS Config to monitor the following newly supported resource types in all AWS Regions where the supported resources are available: Resource Types:

AWS::AppStream::AppBlockBuilder
AWS::IoT::ThingGroup

AWS::B2BI::Capability
AWS::IoTSiteWise::Asset

AWS::CleanRoomsML::TrainingDataset
AWS::Location::APIKey

AWS::CloudFront::KeyValueStore
AWS::MediaPackageV2::OriginEndpoint

AWS::Connect::SecurityProfile
AWS::PCAConnectorAD::Connector

AWS::Deadline::Monitor
AWS::Route53::DNSSEC

AWS::EC2::SubnetCidrBlock
AWS::S3Tables::TableBucketPolicy

AWS::ECR::ReplicationConfiguration
AWS::SageMaker::UserProfile

AWS::GameLift::Build
AWS::SecretsManager::ResourcePolicy

AWS::GuardDuty::MalwareProtectionPlan      
AWS::SSMContacts::Contact

AWS::ImageBuilder::LifecyclePolicy
 

Quelle: aws.amazon.com

Amazon ECS now supports tmpfs mounts on AWS Fargate and ECS Managed Instances

Amazon Elastic Container Service (Amazon ECS) now supports tmpfs mounts for Linux tasks running on AWS Fargate and Amazon ECS Managed Instances, extending beyond the EC2 launch type. With tmpfs, you can now create memory‑backed file systems for your containerized workloads without writing this data to task storage. tmpfs mounts provide a temporary file system that is backed by memory and exposed inside the container at a path you choose. This is ideal for performance‑sensitive workloads that need fast access to scratch files, caches, or temporary working sets, and for security‑sensitive data such as short‑lived secrets or credentials, because the data does not persist after the task stops. tmpfs also lets you keep the container root file system read‑only using the readonlyRootFilesystem setting while still allowing applications to write to specific in‑memory directories. To get started, update your task definition so that the container definitions include a linuxParameters block with one or more tmpfs entries. For each tmpfs mount, specify the containerPath, size, and optional mountOptions. You can register or update task definitions using the Amazon ECS console, AWS CLI, AWS CloudFormation, or AWS CDK. This feature is available in all AWS Regions where Amazon ECS, AWS Fargate, and Amazon ECS Managed Instances are supported. To learn more, see the LinuxParameters and Tmpfs sections in the Amazon ECS API Reference and the Amazon ECS Developer Guide.
Quelle: aws.amazon.com

AWS Resource Explorer is now available in AWS Asia Pacific (New Zealand) Region.

Today, AWS Resource Explorer has expanded the availability of resource search and discovery to the Asia Pacific (New Zealand) Region. With AWS Resource Explorer you can search for and discover your AWS resources across AWS Regions and accounts in your organization, either using the AWS Resource Explorer console, the AWS Command Line Interface (AWS CLI), the AWS SDKs, or the unified search bar from wherever you are in the AWS Management Console. For more information about the Regions where AWS Resource Explorer is available, see the AWS Region table. To turn on AWS Resource Explorer, visit the AWS Resource Explorer console. Read about getting started in our AWS Resource Explorer documentation, or explore the AWS Resource Explorer product page.
Quelle: aws.amazon.com