Questions tagged with AWS Auto Scaling

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

When using Application Auto Scaling with AppStream Fleet is this assumption correct (see picture below)? ![Enter image description here](/media/postImages/original/IM2mXHSEdBTYefmn_AO-V3GQ) What I mean is: does the Instances in Idle and Disconnect Timeouts count as a Running Capacity and are included in CapacityUtilization within CloudWatch Alarms metrics? Is the assumption correct that cooldown and evaluation period would be picked up by CloudWatch alarm after the Timeouts have expired?
1
answers
0
votes
90
views
profile picture
Les
asked 5 months ago
I'm trying to tag an existing autoscaling group, using Python and Boto3. I can definitely describe the ASGs by name: ``` import boto3 asg_client = boto3.client("autoscaling") asg_name = "foo-bar20220502044025104700000001" response = asg_client.describe_auto_scaling_groups(AutoScalingGroupNames=[asg_name]) ``` The problem I have with the `create_or_update_tags()` and `delete_tags()` methods is that they don't seem to accept a list of ASG names. E.g. this doesn't work: ``` asg_client.create_or_update_tags( AutoScalingGroupNames=[asg_name], Tags=[my_tag] ) ``` To make it clear: - the ASG already exists, I am not creating it here - I do not want to make any other changes to the ASG - all I want is be able to tag an ASG if I know its name - I need to use boto3 from Python for this The tag-related methods appear to be different from all the other ASG client methods in that they do not accept an ASG name, or list of names, as a parameter.
1
answers
0
votes
209
views
asked 5 months ago
Hi, I'm having an issue with my target group, when an autoscaling happens the registered target is also removed since a new instance is created. How can I replace the new target with the new instance automatically? Thank you
2
answers
0
votes
62
views
asked 6 months ago
We are currently working on designing a resilient system that can handle storage failure. I would like to know if this is even possible to achieve from an infrastructure point. The system will be consist of ELB -> ALB -> EC2. The autoscaling group will have 2 pool, one warm and one active pool (both contain a max of 1 instance). In order to achieve high resiliency we are planning on creating a snapshot of active instances EBS volume every 3 minute. In warm autoscaling pool we will have a warm instance ready to go. We will run a lambda every 3 minutes that will pull the latest snapshot and attach to the warm pool instance. In that way if any time the active goes down, the warm instance can come up with latest snapshot data. In theory this looks doable but is there any technical issues that we might run into? Also, how much time it takes for a volume to be built from a 500GB snapshot? Other info: a) There is only ~5KB/sec of data written per second during business hours only. b) The EBS volume will have around 500GB of data Thanks
1
answers
0
votes
78
views
jg_dh
asked 6 months ago
Hi, We are using the command put-scheduled-action, to change the minimum capacity to 0 every day on specify hour. He accept to change, but the scheduled don´t remove the read replica, the cluster stay with 1 read replica. We try to change the state of the alarm that start the action, but on the history of the alarme it show that started the action, but the read replica was not removed. The goal is to remove all read replica after the commercial hour when not using, but if is using, he scale up when necessarie and on morning we will use de put-scheduled-action to came back the minimum to 1. There any way to make this work? Best Regards, tcanoas
1
answers
0
votes
54
views
tcanoas
asked 6 months ago
Hi, I've deployed a custom model container as Sagemaker Async Endpoint which works fine so far. It's callable and provides results as expected. I now want to apply a TargetTrackingScalingPolicy but some of the metrics specified [here](https://docs.aws.amazon.com/sagemaker/latest/dg/monitoring-cloudwatch.html#cloudwatch-metrics-endpoint-invocation) seem to be not reported, they're also not visible in CloudWatch, e.g Invocations and InvocationsPerInstance. On the other hand, metrics like ModelLatency, TotalProcessingTime and TimeInBacklog show reasonable values. I guess due to these values missing e.g. applying this policy config doesn't have any effect either: ``` TargetTrackingScalingPolicyConfiguration={ "TargetValue": 2.0, # The target value for the metric. - here the metric is - SageMakerVariantInvocationsPerInstance "CustomizedMetricSpecification": { "MetricName": "InvocationsPerInstance", "Namespace": "AWS/SageMaker", "Dimensions": [{"Name": "EndpointName", "Value": endpoint_name}], "Statistic": "Average", }, "ScaleInCooldown": 60, "ScaleOutCooldown": 60 }, ``` Thanks a lot for any advice!
0
answers
0
votes
34
views
asked 6 months ago
We are using AWS Aurora with automatic scaling of read replicas, which are launched with a generated name-tag with the prefix "application-autoscaling-" but no other tags. Is there a way we could overwrite the prefix and define additional tags (like the environment or application-id for which the cluster is used), as we can do for instances launched into EC2 auto-scaling groups? I can imagine doing this with some lambda function, but is there maybe an easier way? And if not, how are the costs for the autoscaled readers reported in the cost-replorer for example? Are they counted towards the readers I've created manually in the cluster?
0
answers
1
votes
32
views
MMoench
asked 6 months ago
Hello Everyone, We are getting "Uncaught RedisClusterException: Can't communicate with any node in the cluster in" this error. We are using Elastic Cache redis cluster with 2 node and cluster mode was enable PHP library ==>https://github.com/cheprasov/php-redis-client we are using this library. This error randomly occurs in our websites. At the time of error Elastic cache load was normal. Is there any way to trouble shoot this issue.
0
answers
0
votes
23
views
profile picture
asked 6 months ago
I try to create ASG but there is Instance purchase options and Allocation strategies sections missing. It's not there either during create, edit or review. I've some ASG created >1 month ago and it contains Instance purchase options and Allocation strategies sections. However when in this old ASG I try to edit Instance purchase options it goes to editor view with Instance purchase options and Allocation strategies missing. Also when I tried to create ASG similar to the one created >1 month ago it still doesn't have Instance purchase options and Allocation strategies sections. What's going on?
1
answers
0
votes
33
views
marr
asked 6 months ago
Hi everyone, thanks for your help After changing the type of instance of one of our elasticbeanstalk this one is block on the event "Created Auto Scaling launch configuration named: awseb-e-guthbfkdfe-stack-AWSEBAutoScalingLaunchConfiguration-xxxx" and the option to cancel is unavailable. what can I do to unblock this situation.
1
answers
0
votes
46
views
asked 6 months ago
I have allocated an elastic IP address to the auto-scaling group. after traffic increases, it creates another instance with a new IP address. the newly generated IP address is not assigned automatically to the elastic IP address.
2
answers
0
votes
85
views
Arshad
asked 6 months ago
Currently I am trying out a KDA + Flink setup and first thing that stops me a little bit is failover strategy. There is only one option for a failover: take savepoint -> destroy cluster -> start new cluster -> start job from savepoint, and this option ends up in few minutes downtime. I am aware that aws uses a bit different strategy for maintenance window where both clusters run at the same time and only job stop, start creates a downtime which is way shorter then the only available option. Does anyone know if this and when this second option will be available for cases like autoscale/ user maintenance/ etc.? And will it be compatible with custom autoscaling rules?
0
answers
0
votes
42
views
asked 7 months ago