AWS Updates - 2026-01-06
AWS What's New
AWS Marketplace Seller Reporting now provides collections visibility
- Link: https://aws.amazon.com/about-aws/whats-new/2026/01/aws-marketplace-seller-reporting-collections/
- Published: 2026-01-06
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
Amazon ECS now supports tmpfs mounts on AWS Fargate and ECS Managed Instances
- Link: https://aws.amazon.com/about-aws/whats-new/2026/01/amazon-ecs-tmpfs-mounts-aws-fargate-managed-instances
- Published: 2026-01-06
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.
Amazon MQ now supports HTTP based authentication for RabbitMQ brokers
- Link: https://aws.amazon.com/about-aws/whats-new/2026/01/amazon-mq-http-based-rabbitmq-brokers/
- Published: 2026-01-06
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.
AWS Config now supports 21 new resource types
- Link: https://aws.amazon.com/about-aws/whats-new/2026/01/aws-config-new-resource-types
- Published: 2026-01-06
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 |