EC2 Auto Scaling announces warm pool support for Auto Scaling groups that have mixed instances policies

Starting today, you can add warm pools to Auto Scaling groups (ASGs) that have mixed instances policies. With warm pools, customers can improve the elasticity of their applications by creating a pool of pre-initialized EC2 instances that are ready to quickly serve application traffic. By combining warm pools with instance type flexibility, an ASG can rapidly scale out to its maximum size at any time, deploying applications across multiple instance types to enhance availability. Warm pools are particularly beneficial for applications with lengthy initialization processes, such as writing large amounts of data to disk, running complex custom scripts, or other time-consuming setup procedures that can take several minutes or longer to serve traffic. With this new release, the warm pool feature now works seamlessly with ASGs configured for multiple On-Demand instance types, whether specified through manual instance type lists or attribute-based instance type selection. The combination of instance type flexibility and warm pools provides a powerful solution that helps customers scale out efficiently while maximizing availability. The warm pool feature is available through the AWS Management Console, the AWS SDKs, and the AWS Command Line Interface (CLI). It is available in all public AWS Regions and AWS GovCloud (US) Regions. To learn more about warm pools, visit this AWS documentation.
Quelle: aws.amazon.com

AWS Config now supports 52 new resource types

AWS Config now supports 52 additional AWS resource types across key services including Amazon EC2, Amazon Bedrock, and Amazon SageMaker. 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::ApiGateway::DomainName
AWS::IAM::GroupPolicy

AWS::ApiGateway::Method
AWS::IAM::RolePolicy

AWS::ApiGateway::UsagePlan
AWS::IAM::UserPolicy

AWS::AppConfig::Extension
AWS::IoTCoreDeviceAdvisor::SuiteDefinition

AWS::Bedrock::ApplicationInferenceProfile
AWS::MediaPackageV2::Channel

AWS::Bedrock::Prompt
AWS::MediaPackageV2::ChannelGroup

AWS::BedrockAgentCore::BrowserCustom
AWS::MediaTailor::LiveSource

AWS::BedrockAgentCore::CodeInterpreterCustom        
AWS::MSK::ServerlessCluster

AWS::BedrockAgentCore::Runtime
AWS::PaymentCryptography::Alias

AWS::CloudFormation::LambdaHook
AWS::PaymentCryptography::Key

AWS::CloudFormation::StackSet
AWS::RolesAnywhere::CRL

AWS::Comprehend::Flywheel
AWS::RolesAnywhere::Profile

AWS::Config::AggregationAuthorization
AWS::S3::AccessGrant

AWS::DataSync::Agent
AWS::S3::AccessGrantsInstance

AWS::Deadline::Fleet
AWS::S3::AccessGrantsLocation

AWS::Deadline::QueueFleetAssociation
AWS::SageMaker::DataQualityJobDefinition

AWS::EC2::IPAMPoolCidr
AWS::SageMaker::MlflowTrackingServer

AWS::EC2::SubnetNetworkAclAssociation
AWS::SageMaker::ModelBiasJobDefinition

AWS::EC2::VPCGatewayAttachment
AWS::SageMaker::ModelExplainabilityJobDefinition

AWS::ECR::RepositoryCreationTemplate
AWS::SageMaker::ModelQualityJobDefinition

AWS::ElasticLoadBalancingV2::TargetGroup
AWS::SageMaker::MonitoringSchedule

AWS::EMR::Studio
AWS::SageMaker::StudioLifecycleConfig

AWS::EMRContainers::VirtualCluster
AWS::SecretsManager::RotationSchedule

AWS::EMRServerless::Application
AWS::SES::DedicatedIpPool

AWS::EntityResolution::MatchingWorkflow
AWS::SES::MailManagerTrafficPolicy

AWS::Glue::Registry
AWS::SSM::ResourceDataSync

To view the complete list of AWS Config supported resource types, see the supported resource types page.
Quelle: aws.amazon.com

Amazon CloudWatch Synthetics adds multi-browser support in AWS GovCloud Regions

Amazon CloudWatch Synthetics multi-browser support is now available in the AWS GovCloud (US-East, US-West) Regions. This expansion enables customers in these two regions to test and monitor their web applications using both Chrome and Firefox browsers. With this launch, you can run the same canary script across Chrome and Firefox when using Playwright-based canaries or Puppeteer-based canaries. CloudWatch Synthetics automatically collects browser-specific performance metrics, success rates, and visual monitoring results while maintaining an aggregate view of overall application health. This helps development and operations teams quickly identify and resolve browser compatibility issues that could affect application reliability. To learn more about configuring multi-browser canaries, see the canary docs in the Amazon CloudWatch Synthetics User Guide. 
Quelle: aws.amazon.com

Mountpoint for Amazon S3 and Mountpoint for Amazon S3 CSI driver add monitoring capability

You can now monitor Mountpoint operations in observability tools such as Amazon CloudWatch, Prometheus, and Grafana. With this launch, Mountpoint emits near real-time metrics such as request count or request latency using OpenTelemetry Protocol (OTLP), an open source data transmission protocol. This means you can use applications such as CloudWatch agent or the OpenTelemetry (OTel) collector to publish the metrics into observability tools and create dashboards for monitoring and troubleshooting. Previously, Mountpoint emitted operational data into log files, and you needed to create custom tools to parse the log files for insights. Now, when you mount your Amazon S3 bucket, you can configure Mountpoint to publish the metrics to an observability tool to proactively monitor issues that might impact your applications. For example, you can check if an application is unable to access S3 due to permission issues by analyzing the S3 request error metric that provides error types at an Amazon EC2 instance granularity. Follow the step-by-step instructions to set up the CloudWatch agent or the OTel collector and configure Mountpoint to publish metrics into an observability tool. For more information, visit the Mountpoint for Amazon S3 GitHub repository, Mountpoint product page, and Mountpoint for Amazon S3 CSI driver GitHub page.
Quelle: aws.amazon.com

Amazon CloudWatch Agent adds support for NVMe Local Volume Performance Statistics

Amazon CloudWatch agent now supports the collection of detailed performance metrics for NVMe local volumes on Amazon EC2 instances. These metrics give you insights into behavior and performance characteristics of your NVMe local storage. The CloudWatch agent can now be configured to collect and send detailed NVMe metrics to CloudWatch, providing deeper visibility into storage performance. The new metrics include comprehensive performance indicators such as queue depths, I/O sizes, and device utilization. These metrics are similar to the detailed performance statistics available for EBS volumes, providing a consistent monitoring experience across both storage types. You can create CloudWatch dashboards, set alarms, and analyze trends for your NVMe-based instance store volumes. Detailed performance statistics for Amazon EC2 instance store volumes via Amazon CloudWatch agent are available for all local NVMe volumes attached to Nitro-based EC2 instances in all AWS Commercial and AWS GovCloud (US) Regions. See the Amazon CloudWatch pricing page for CloudWatch pricing details. To get started with detailed performance statistics for Amazon EC2 instance store volumes in CloudWatch, see Collect Amazon EC2 instance store volume NVMe driver metrics in the Amazon CloudWatch User Guide. To learn more about detailed performance statistics for Amazon EC2 instance store volumes, see Amazon EC2 instance store volumes in the Amazon EC2 User Guide.
Quelle: aws.amazon.com

Amazon Cognito removes Machine-to-Machine app client price dimension

We’re excited to announce a simplified pricing model for Amazon Cognito’s machine-to-machine (M2M) authentication. Starting today we are removing the M2M app client pricing dimension, making it more cost-effective for customers to build and scale their M2M applications. Cognito supports applications that access API data with machine identities. Machine identities in user pools are clients that run on application servers and connect to remote APIs. Their operation happens without user interaction such as scheduled tasks, data streams, or asset updates. This change reduces the pricing of Cognito for customers using M2M authentication by removing the app client price dimension. Customers will continue to be charged based on the number of successful M2M token requests per month. Previously, customers were charged for each M2M app client registered, regardless of usage amount, and each successful token request made by the app client to access a resource. With this change, customers will only pay for their successful token requests, making it more cost-effective to build and scale M2M applications using Amazon Cognito. This pricing change is automatic and requires no action from customers. It is effective in all supported Amazon Cognito regions. To learn more about Amazon Cognito pricing, visit our pricing page. 
Quelle: aws.amazon.com

New SAP on AWS GROW Region Availability for SAP Cloud ERP

SAP Cloud ERP on AWS (GROW) is now available in the Europe (Frankfurt) region. As a complete offering of solutions, best practices, adoption acceleration services, community and learning, SAP Cloud ERP on AWS helps any size organization adopt cloud enterprise resource planning (ERP) with speed, predictability, and continuous innovation on the world’s most comprehensive and broadly adopted cloud. SAP Cloud ERP on AWS can be implemented in months instead of years compared to traditional on-premises ERP implementations. By implementing SAP Cloud ERP on AWS, you can simplify everyday work, grow your business, and secure your success. At the core of SAP Cloud ERP on AWS is SAP S/4HANA Cloud, Public edition a full-featured SaaS ERP suite built on the learnings of SAP’s 50+ years of industry best practices. SAP Cloud ERP on AWS allows your organization to gain end-to-end process visibility and control with integrated systems across HR, procurement, sales, finance, supply chain, and manufacturing. It also includes SAP Business AI-powered processes leveraging AWS to provide data-driven insights and recommendations. Customers can also innovate with generative AI using their SAP data through Amazon Bedrock models in the SAP generative AI hub. SAP Cloud ERP on AWS takes advantage of AWS Graviton processors, which offer up to 60% less energy than comparable cloud instances for the same performance. To learn more about deploying SAP Cloud ERP on AWS explore the SAP on AWS product page.   
Quelle: aws.amazon.com

Amazon Route 53 Resolver now supports AWS PrivateLink

Amazon Route 53 Resolver now supports AWS PrivateLink. Customers can now access and manage Route 53 Resolver and all the related features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Resolver and its features are accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing, can be handled via the Amazon private network.  Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. Route 53 Resolver also offers features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) that you can opt-into. You can use Resolver and its features with AWS PrivateLink in regions where Route 53 Resolver and all its associated features are available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Resolver and its features are available, see here. To learn more about Route 53 Resolver and its features, please refer to the service documentation.
Quelle: aws.amazon.com

Amazon GameLift Streams adds AWS Health notifications for aging resources

Amazon GameLift Streams is now integrated with AWS Health and will provide automated notifications about aging stream groups. Customers are sent regular reminders via AWS Health to re-create their stream groups starting as early as the 45th day to the 335th day from the stream group creation date. Stream groups older than 180 days are restricted from adding new applications and automatically expire after the 365th day. This feature strengthens our customer’s security posture by helping customers manage the lifecycle of stream groups and prevent the use of outdated resources that might be missing updates. While the customer focuses on their game development, the service helps maintain the health of their resources. AWS Health will send a reminder to the linked account on the 45th day and on the 150th day from the stream group creation day, informing customers that the stream group will be restricted from adding new applications after the 180-day. A last reminder to re-create the stream group will be sent on 335th day informing customers that the stream group will expire on the 365th day. This feature is available in all AWS Regions where Amazon GameLift Streams is offered at no additional cost. Maintenance warnings or the expiration date of a stream group can be viewed on the Stream group details page on the service console, or by using the ExpiresAt field in the GetStreamGroup API response. To learn more about managing your stream groups and configuring notifications, visit the Amazon GameLift documentation on Stream group lifecycle.
Quelle: aws.amazon.com

AWS Marketplace now offers pricing model flexibility and simplified deployment for AI agents and tools

AWS Marketplace now offers flexible pricing models, simplified authentication, and streamlined deployment for AI agents and tools. The new capabilities include contract-based and usage-based pricing for Amazon Bedrock AgentCore Runtime containers, and simplified OAuth credential management through Quick Launch for API-based AI agents and tools. Customers can also use supported remote MCP servers procured through AWS Marketplace as MCP targets on AgentCore Gateway, making it easier for them to connect to AI agents and tools from AWS Partners at scale. The improvements reduce deployment complexity while offering pricing models that better align with diverse customer needs. For Partners, the new capabilities for AI agents and tools streamline management and provide additional pricing options through AWS Marketplace. Partners can now manage all their AI agents and tools listings from one page in the AWS Marketplace Management Portal, reducing the complexity of managing multiple listings across different interfaces. With usage-based and contract-based pricing options for AgentCore Runtime compatible products, Partners have more flexibility to implement pricing strategies that align with their business models and customers’ needs. Customers can learn more in the buyer guide and start exploring AI agent solutions in AWS Marketplace on the solutions page. For partners interested in implementing the capabilities, visit the seller guide and complete the workshop.
Quelle: aws.amazon.com