EC2 Auto Scaling now offers a synchronous API to launch instances inside an Auto Scaling group

Today, EC2 Auto Scaling is launching a new API, LaunchInstances, which gives customers more control and flexibility over how EC2 Auto Scaling provisions ins...

#AWS #AmazonEc2AutoScaling #AwsGovcloudUs

EC2 Auto Scaling now offers a synchronous API to launch instances inside an Auto Scaling group Today, EC2 Auto Scaling is launching a new API, LaunchInstances, which gives customers more control and flexibility over how EC2 Auto Scaling provisions instances while providing instant feedback on capacity availability. Customers use EC2 Auto Scaling for automated fleet management. With scaling policies, EC2 Auto Scaling can automatically add instances when demand spikes and remove them when traffic drops, ensuring customers' applications always have the right amount of compute. EC2 Auto Scaling also offers the ability to monitor and replace unhealthy instances. In certain use cases, customers may want to specify exactly where EC2 Auto Scaling should launch additional instances and need immediate feedback on capacity availability. The new LaunchInstances API allows customers to precisely control where instances are launched by specifying an override for any Availability Zone and/or subnet in an Auto Scaling group, while providing immediate feedback on capacity availability. This synchronous operation gives customers real-time insight into scaling operations, enabling them to quickly implement alternative strategies if needed. For additional flexibility, the API includes optional asynchronous retries to help reach the desired capacity. This feature is now available in all AWS Regions and AWS GovCloud (US) Regions, at no additional cost beyond standard EC2 and EBS usage. To get started, visit the AWS Command Line Interface (CLI) and the AWS SDKs. To learn more about this feature, visit the AWS documentation.

🆕 EC2 Auto Scaling's new synchronous LaunchInstances API offers precise instance launch control in groups, providing immediate feedback on capacity and optional retries, available in all AWS Regions at no extra cost.

#AWS #AmazonEc2AutoScaling #AwsGovcloudUs

Amazon EC2 Auto Scaling now supports root volume replacement through instance refresh

Today, Amazon EC2 Auto Scaling announced a new strategy, ReplaceRootVolume, within instance refresh. This feature allows customers to update the root volume of an EC2 instance with...

#AWS #AmazonEc2AutoScaling

EC2 Auto Scaling introduces instance lifecycle policy

Today, EC2 Auto Scaling announces a new feature called instance lifecycle policy. Customers can now configure a way to retain their instances when their termination lifecycle hooks fail or timeout, pro...

#AWS #AmazonEc2 #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports root volume replacement through instance refresh Today, Amazon EC2 Auto Scaling announced a new strategy, ReplaceRootVolume, within instance refresh. This feature allows customers to update the root volume of an EC2 instance without stopping or terminating the instance, while preserving other associated instance resources. The capability reduces operational complexity, simplifies software patching, and streamlines recovery from corrupted root volumes. Customers use instance refresh to update the instances in their Auto Scaling groups (ASGs). This feature can be useful when customers want to migrate their instances to new instance types to take advantage of the latest improvements and optimizations. Traditionally, this process involved terminating older instances and launching new ones in a controlled manner. The new ReplaceRootVolume strategy transforms how customers manage instance lifecycles and software updates in their ASGs by enabling EC2 Auto Scaling service to replace the root Amazon EBS volume for running instances without stopping them. Organizations can now implement OS-level updates and security patches more efficiently without worrying about capacity management. This is especially valuable for workloads that use specialized instance types like Mac or GPU instances. Customers with stateful applications can now refresh their fleets with more confidence that their instances data, metadata, and attachments (such as network interfaces and elastic IPs) will be preserved with the new ReplaceRootVolume strategy. This feature is now available in US East (N. Virginia), US West (Oregon), Europe (Ireland), and Asia Pacific (Singapore), at no additional cost beyond standard EC2 and EBS usage. To get started, refer to our technical documentation.

🆕 Amazon EC2 Auto Scaling now supports ReplaceRootVolume in instance refresh, allowing root volume updates without stopping instances, simplifying patching and recovery, available at no extra cost in select regions.

#AWS #AmazonEc2AutoScaling

EC2 Auto Scaling introduces instance lifecycle policy Today, EC2 Auto Scaling announces a new feature called instance lifecycle policy. Customers can now configure a way to retain their instances when their termination lifecycle hooks fail or timeout, providing greater confidence in managing instances for graceful shutdown. You can add lifecycle hooks to an Auto Scaling group (ASG) to perform custom actions when an instance enters a wait state. You can choose a target service (e.g., Amazon EventBridge or AWS Lambda) to perform these actions depending on your preferred development approach. Customers use ASG lifecycle hooks to save application state, properly close database connections, back up important data from local storage, delete sensitive data/credentials, or deregister from service discovery before instance termination. Previously, both default results—continue and abandon—led to ASG terminating instances when the lifecycle hook timeout elapsed or if an unexpected failure occurred. With the new instance lifecycle policy, you can now configure retention-triggers to keep your instances in a retained state for manual intervention until you're ready to terminate them again. This policy provides greater confidence in graceful instance termination and is especially helpful for stateful applications running on ASG. This feature is now available in US East (N. Virginia), US West (Oregon), Europe (Ireland), and Asia Pacific (Singapore). To get started, visit the EC2 Auto Scaling console or refer to our technical documentation.

🆕 EC2 Auto Scaling now offers instance lifecycle policy to retain instances during failed termination hooks, ensuring graceful shutdown for stateful apps. Available in select regions; visit EC2 Auto Scaling console for details.

#AWS #AmazonEc2 #AmazonEc2AutoScaling

EC2 Auto Scaling now offers a synchronous API to launch instances inside an Auto Scaling group

Today, EC2 Auto Scaling is launching a new API, LaunchInstances, which gives customers more control and flexibility over how EC2 Auto Scaling provisions instances while pr...

#AWS #AmazonEc2AutoScaling

EC2 Auto Scaling now offers a synchronous API to launch instances inside an Auto Scaling group Today, EC2 Auto Scaling is launching a new API, LaunchInstances, which gives customers more control and flexibility over how EC2 Auto Scaling provisions instances while providing instant feedback on capacity availability. Customers use EC2 Auto Scaling for automated fleet management. With scaling policies, EC2 Auto Scaling can automatically add instances when demand spikes and remove them when traffic drops, ensuring customers' applications always have the right amount of compute. EC2 Auto Scaling also offers the ability to monitor and replace unhealthy instances. In certain use cases, customers may want to specify exactly where EC2 Auto Scaling should launch additional instances and need immediate feedback on capacity availability. The new LaunchInstances API allows customers to precisely control where instances are launched by specifying an override for any Availability Zone and/or subnet in an Auto Scaling group, while providing immediate feedback on capacity availability. This synchronous operation gives customers real-time insight into scaling operations, enabling them to quickly implement alternative strategies if needed. For additional flexibility, the API includes optional asynchronous retries to help reach the desired capacity. This feature is now available in US East (N. Virginia), US West (Oregon), Europe (Ireland), and Asia Pacific (Singapore), at no additional cost beyond standard EC2 and EBS usage. To get started, visit the AWS Command Line Interface (CLI) and the AWS SDKs. To learn more about this feature, visit the AWS documentation.

🆕 EC2 Auto Scaling now offers a synchronous API to launch instances with immediate feedback on capacity, enabling precise control over instance placement and scaling strategies, available at no extra cost in select regions.

#AWS #AmazonEc2AutoScaling

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 docs.aws.amazon.com/autoscaling/ec2/userguid...

#AWS #AwsGovcloudUs #AmazonEc2AutoScaling

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.

🆕 AWS EC2 Auto Scaling's warm pools now support mixed instances policies, offering pre-initialized instances for quick traffic response, flexible instance types, and optimal availability and scalability. Available globally.

#AWS #AwsGovcloudUs #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports predictive scaling in six more regions

Customers can now enable predictive scaling for their Auto Scaling groups (ASGs) in six more regions: Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Israel (Tel Aviv), Canada West (Calg...

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports predictive scaling in six more regions Customers can now enable predictive scaling for their Auto Scaling groups (ASGs) in six more regions: Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Israel (Tel Aviv), Canada West (Calgary), Europe (Spain), and Europe (Zurich). Predictive Scaling can proactively scale out your ASGs to be ready for upcoming demand. This allows you to avoid the need to over-provision capacity, resulting in lower EC2 cost, while ensuring your application’s responsiveness. To see the list of all supported AWS public regions and AWS GovCloud (US) regions, click here. Predictive Scaling is appropriate for applications that experience recurring patterns of steep demand changes, such as early morning spikes when business resumes. It learns from the past patterns and launches instances in advance of predicted demand, giving instances time to warm up. Predictive scaling enhances existing Auto Scaling policies, such as Target Tracking or Simple Scaling, so that your applications scale based on both real-time metrics and historic patterns. You can preview how Predictive Scaling works with your ASG by using the “Forecast Only” mode. Predictive Scaling is available as a scaling policy type through AWS Command Line Interface (CLI), EC2 Auto Scaling Management Console, AWS CloudFormation and AWS SDKs. To learn more, visit the Predictive Scaling page in the EC2 Auto Scaling documentation.

🆕 Amazon EC2 Auto Scaling adds predictive scaling to six new regions: Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Israel (Tel Aviv), Canada West (Calgary), Europe (Spain), and Europe (Zurich), to proactively manage demand, cut costs, and boost responsiveness.

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports Internet Protocol Version 6 (IPv6) Amazon EC2 Auto Scaling (ASG) now supports Internet Protocol Version 6 (IPv6), enabling dual-stack configuration (IPv4 and IPv6) connectivity for your Auto Scaling groups. IPv6 enables an expanded address space, enabling you to scale your application on AWS beyond the typical constraints of the number of IPv4 addresses in your VPC. With IPv6, you can assign easy to manage contiguous IP ranges to micro-services and can get virtually unlimited scale for your applications. Moreover, with support for both IPv4 and IPv6, you can gradually transition applications from IPv4 to IPv6, enabling safer migration. IPv6 support is available in all commercial AWS regions (except New Zealand) and GovCloud regions where ASG is available. To learn more about configuring your network to use IPv6 endpoints, see the documentation.

🆕 Amazon EC2 Auto Scaling now supports IPv6, enabling dual-stack connectivity and virtually unlimited scale for applications, with gradual IPv4 to IPv6 transition. Available in all commercial regions except New Zealand and GovCloud.

#AWS #AwsGovcloudUs #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling expands AWS PrivateLink support to FIPS endpoints

Starting today, Amazon EC2 Auto Scaling (ASG) supports Federal Information Processing Standard (FIPS) 140-3 validated VPC endpoints. With this launch, you can use AWS PrivateLink with ASG for ...

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling expands AWS PrivateLink support to FIPS endpoints Starting today, Amazon EC2 Auto Scaling (ASG) supports Federal Information Processing Standard (FIPS) 140-3 validated VPC endpoints. With this launch, you can use AWS PrivateLink with ASG for regulated workloads that require secure connections using FIPS 140-3 validated cryptographic modules. FIPS-compliant endpoints help organizations contracting with the U.S. federal government meet FIPS security requirements for encrypting sensitive data in supported regions. To create a VPC endpoint that connects to an ASG endpoint, see Setting up a VPC endpoint for Amazon EC2 Auto Scaling. This capability is available in the following regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), and Canada West (Calgary). For more information about FIPS 140-3 at AWS, visit FIPS 140-3 Compliance. To learn more about Amazon EC2 Auto Scaling, visit the ASG product page.

🆕 Amazon EC2 Auto Scaling now supports FIPS 140-3 validated VPC endpoints via AWS PrivateLink, enabling secure connections for regulated workloads in selected regions.

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports forced cancellation of instance refreshes

Amazon EC2 Auto Scaling now enables customers to force cancel instance refreshes immediately, without waiting for in-progress instance launches or terminations to complete. This enhanceme...

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling now supports forced cancellation of instance refreshes Amazon EC2 Auto Scaling now enables customers to force cancel instance refreshes immediately, without waiting for in-progress instance launches or terminations to complete. This enhancement provides greater control over Auto Scaling group (ASG) updates, especially during emergency situations such as when needing to rapidly roll forward to a new application deployment when the current deployment is causing service disruptions. Customers can now quickly abort ongoing deployments and immediately start new instance refreshes when needed. Instance refreshes are used to update instances within an ASG, typically when configuration changes require instance replacement. To use this feature, set the WaitForTransitioningInstances to false when calling the CancelInstanceRefresh API. This enables faster cancellation of the instance refresh, bypassing the wait for any pending instance activities such as instance lifecycle hooks. This feature is available in all AWS regions, including AWS GovCloud (US) Regions. To get started, please visit Amazon EC2 Auto Scaling user guide.

🆕 Amazon EC2 Auto Scaling now lets you force cancel instance refreshes instantly, skipping pending actions for faster emergency control. Use WaitForTransitioningInstances=false in CancelInstanceRefresh API. Available globally, including AWS GovCloud (US).

#AWS #AmazonEc2AutoScaling

AWS Compute Optimizer now identifies idle EC2 Auto Scaling groups with GPU instances

AWS Compute Optimizer now detects idle EC2 Auto Scaling groups using G and P instance types, enabling you to identify additional savings opportunities in your A...

#AWS #AwsComputeOptimizer #AmazonEc2AutoScaling

AWS Compute Optimizer now identifies idle EC2 Auto Scaling groups with GPU instances AWS Compute Optimizer now detects idle EC2 Auto Scaling groups using G and P instance types, enabling you to identify additional savings opportunities in your AWS spend. As AI development accelerates, organizations are creating more Auto Scaling groups with G and P instance types for training and inference workloads. Once you enable the NVIDIA CloudWatch agent, Compute Optimizer analyzes utilization data and identifies groups that have completed jobs and remained idle during your specified lookback period, making it easier to identify and prevent waste on these high-cost instance types. This new feature is available in all AWS Regions where AWS Compute Optimizer is available except for the AWS GovCloud (US) and the China Regions. The new recommendations will also be available in Cost Optimization Hub. For more information about Compute Optimizer, visit our product page and documentation. You can start using AWS Compute Optimizer through the AWS Management Console, AWS Services CLI, or AWS SDK.

🆕 AWS Compute Optimizer now identifies idle EC2 Auto Scaling groups with GPU instances, helping you save on high-cost G and P instances by detecting unused groups. Available in most regions except AWS GovCloud (US) and China.

#AWS #AwsComputeOptimizer #AmazonEc2AutoScaling

Cost Optimization Hub supports more EC2 Auto Scaling group recommendations

Cost Optimization Hub now supports idle EC2 Auto Scaling group recommendations and rightsizing recommendations for EC2 Auto Scaling groups with scaling policies and ...

#AWS #AmazonEc2AutoScaling #CloudFinancialManagement

Cost Optimization Hub supports more EC2 Auto Scaling group recommendations Cost Optimization Hub now supports idle EC2 Auto Scaling group recommendations and rightsizing recommendations for EC2 Auto Scaling groups with scaling policies and multiple instance types. It also allows you to easily filter and aggregate EC2 Auto Scaling group cost optimization opportunities separately from standalone EC2 instances, making it easier to identify EC2 Auto Scaling groups with the highest cost-saving opportunities. With this launch, you can view, consolidate, and prioritize cost optimization opportunities for EC2 Auto Scaling groups across your organization’s member accounts and AWS Regions through a single dashboard. Cost Optimization Hub helps you quantify estimated savings from these recommendations, taking into account your specific discounts, such as Reserved Instances and Savings Plans, enabling you to easily compare and prioritize recommendations. The new EC2 Auto Scaling group experience and recommendations are available in Cost Optimization Hub across all AWS Regions where Cost Optimization Hub and AWS Organizations are supported.

🆕 Cost Optimization Hub supports more EC2 Auto Scaling group recommendations

#AWS #AmazonEc2AutoScaling #CloudFinancialManagement

Amazon EC2 Auto Scaling introduces highly responsive scaling policies

Today, we are launching two new capabilities to EC2 Auto Scaling (ASG) that improve the responsiveness of Target Tracking scaling policies. Target Tracking now automatically adapts to the unique u...

#AWS #AmazonEc2AutoScaling

Amazon EC2 Auto Scaling introduces highly responsive scaling policies Today, we are launching two new capabilities to EC2 Auto Scaling (ASG) that improve the responsiveness of Target Tracking scaling policies. Target Tracking now automatically adapts to the unique usage patterns of your individual applications, and can be configured to monitor high-resolution CloudWatch metrics to make more timely scaling decisions. With this release, you can enhance your application performance, and also maintain high utilization for your EC2 resources to save costs. Scaling based on sub-minute CloudWatch metrics enables customers, with applications that have volatile demand patterns, like client-serving APIs, live streaming services, ecommerce websites, or on-demand data processing, reduce the time to detect and respond to changing demand. In addition, Target Tracking policies now self-tune their responsiveness, using historical usage data to determine the optimal balance between cost and performance for each application that saves customers’ time and effort. Both these new features are available in select commercial regions, and Target Tracking policies will begin self-tuning once they have completed analyzing your application’s usage patterns. You can use Amazon Management Console, CLI, SDKs, and CloudFormation to update your Target Tracking configurations. Refer EC2 Auto Scaling user guide to learn more.

🆕 Amazon EC2 Auto Scaling introduces highly responsive scaling policies

#AWS #AmazonEc2AutoScaling

Amazon EC2 introduces provisioning control to launch instances on On-Demand Capacity

Amazon EC2 introduces a new capability that makes it easy for customers to target instance launches on their docs.aws.amazon.com/AWSEC2/latest/UserGuide/...

#AWS #AmazonEc2AutoScaling

Amazon EC2 introduces provisioning control to launch instances on On-Demand Capacity Amazon EC2 introduces a new capability that makes it easy for customers to target instance launches on their On-Demand Capacity Reservations (ODCRs). On-Demand Capacity Reservations help you reserve compute capacity for your workloads in a specific Availability Zone for any duration. This new feature allows you to better utilize your On-Demand Capacity Reservations by ensuring that launches from the RunInstances EC2 API and EC2 Auto Scaling groups will only be fulfilled by your targeted or open Capacity Reservations. To get started, customers simply specify they if want to only launch on ODCR capacity on either their RunInstances EC2 API, Launch Templates, or Auto-Scaling Groups (ASGs). This capability is now available in all AWS Regions, except China regions. To get started, please refer to the documentation for use with RunInstances API and ASG.

🆕 Amazon EC2 introduces provisioning control to launch instances on On-Demand Capacity

#AWS #AmazonEc2AutoScaling

Amazon EC2 added New CPU-Performance Attribute for Instance Type Selection

Starting today, EC2 Auto Scaling and EC2 Fleet customers can express their EC2 instances’ CPU-performance requirements as part of the Attribute-Based Instance Type Selection (ABIS) configur...

#AWS #AmazonEc2AutoScaling

Amazon EC2 added New CPU-Performance Attribute for Instance Type Selection Starting today, EC2 Auto Scaling and EC2 Fleet customers can express their EC2 instances’ CPU-performance requirements as part of the Attribute-Based Instance Type Selection (ABIS) configuration. With ABIS, customers can already choose a list of instances types by defining a set of desired resource requirements, such as the number of vCPU cores and memory per instance. Now, in addition to the quantitative resource requirements, customers can also identify an instance family that ABIS will use as a baseline to automatically select instance types that offer similar or better CPU performance, enabling customers to further optimize their instance-type selection. ABIS is a powerful tool for customers looking to leverage instance type diversification to meet their capacity requirements. For example, customers who use Spot Instances to launch into limited EC2 spare capacity for a discounted price, access multiple instance types to successfully fulfill their larger capacity needs and experience fewer interruptions. With this release, for example, customers can use ABIS in a launch request for instances that can be in the C, M, and R instance classes, with a minimum of 4 vCPUs, and provide CPU performance in line with the C6i instance family, or better. The feature is available in all AWS commercial and the AWS GovCloud (US) Regions. You can use Amazon Management Console, CLI, SDKs, and CloudFormation to update your instance requirements. To get started, refer the user guide for EC2 Auto Scaling and EC2 Fleet.

🆕 Amazon EC2 added New CPU-Performance Attribute for Instance Type Selection

#AWS #AmazonEc2AutoScaling

EC2 Auto Scaling now supports Amazon Application Recovery Controller zonal shift and zonal autoshift

EC2 Auto Scaling now supports Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift to help you quickly recover an impaired app...

#AWS #AwsGovcloudUs #AmazonEc2AutoScaling

Amazon Application Recovery Controller zonal shift and zonal autoshift extend support for EC2 Auto Scaling

Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift have expanded their capabilities and now support EC2 Auto Scaling. ...

#AWS #AmazonEc2AutoScaling #AwsGovcloudUs

EC2 Auto Scaling now supports Amazon Application Recovery Controller zonal shift and zonal autoshift EC2 Auto Scaling now supports Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift to help you quickly recover an impaired application from failures in an Availability Zone (AZ). Starting today, you can shift the launches of EC2 instances in an Auto Scaling Group (ASG) away from an impaired AZ to quickly recover your unhealthy application in another AZ, reducing the duration and severity of impact due to events such as power outages and hardware, or software failures. This new integration also brings support for ARC zonal autoshift, which automatically starts a zonal shift for enabled ASGs when AWS identifies a potential failure affecting an AZ. You can initiate a zonal shift for an ASG from the Amazon EC2 Auto Scaling or Application Recovery Controller console. You can also use the AWS SDK to start a zonal shift and programmatically shift the instances in your ASG away from an AZ, and shift it back once the affected AZ is healthy. There is no additional charge for using zonal shift. Zonal shift is now available in all AWS Regions. To get started, read the launch blog, or refer to the documentation.

🆕 EC2 Auto Scaling now supports Amazon Application Recovery Controller zonal shift and zonal autoshift

#AWS #AwsGovcloudUs #AmazonEc2AutoScaling