autoscaling

问题 I wanted to fetch the latest ami id for AWS Linux machine while creating an ec2 instance for an autoscaling architecture. I was trying the aws cli to get the images types, but it would print out a lot of information if I used the describe-images command. My requirement was to get only the image id, so that I could use it to create a launch configuration or launch an instance with the latest ami-id. 回答1: A little-known recent feature is the ability to Query for the latest Amazon Linux AMI IDs

问题 I recently started using ECS. I was able to deploy a container image in ECR and create task definition for my container with CPU/Memory limits. My use case is that each container will be a long running app (no webserver, no port mapping needed). The containers will be spawned on demand 1 at a time and deleted on demand 1 at a time. I am able to create a cluster with N server instances. But I'd like to be able for the server instances to automatically scale up/down. For example if there isn't

问题 I recently started using ECS. I was able to deploy a container image in ECR and create task definition for my container with CPU/Memory limits. My use case is that each container will be a long running app (no webserver, no port mapping needed). The containers will be spawned on demand 1 at a time and deleted on demand 1 at a time. I am able to create a cluster with N server instances. But I'd like to be able for the server instances to automatically scale up/down. For example if there isn't

问题 I'm running servers in a AWS auto scale group. The running servers are behind a load balancer. I'm using the ELB to mange the auto scaling groups healthchecks. When servers are been started and join the auto scale group they are currently immediately join to the load balancer. How much time (i.e. the healthcheck grace period) do I need to wait until I let them join to the load balancer? Should it be only after the servers are in a state of running? Should it be only after the servers passed

问题 I'm running servers in a AWS auto scale group. The running servers are behind a load balancer. I'm using the ELB to mange the auto scaling groups healthchecks. When servers are been started and join the auto scale group they are currently immediately join to the load balancer. How much time (i.e. the healthcheck grace period) do I need to wait until I let them join to the load balancer? Should it be only after the servers are in a state of running? Should it be only after the servers passed

问题 In order to reduce the time for provisioning, we've decided to keep up a dedicated EMR cluster with 5 instances (we expect to need about 5). In case we need more, we think we'll need to implement some sort of autoscaling. I'm not familiar at all with EMR- does it support autoscaling? I found this in the docs: http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-manage-resize.html Is that the correct place to look for autoscaling or am I misunderstanding what they mean by

问题 Could you suggest in which ways I can deploy code changes from SVN to all ec2 instances running behind Amazon load balancer in auto-scaling group? I also need to update code to latest version when a new ec2 instance launching automatically in auto-scaling group. I suppose to use 'user-data' to run 'svn up' on new machines. And probably I could use cron to run 'svn up' periodically on all machines. Could you suggest better solutions? 回答1: In my opinion, you shouldn't be updating code on the

问题 How to create variable number of EC2 instance resources in Cloudformation template, according to a template parameter? The EC2 API and management tools allow launching multiple instances of the same AMI, but I can't find how to do this using Cloudformation. 回答1: The AWS::EC2::Instance Resource doesn't support the MinCount / MaxCount parameters of the underlying RunInstances API, so it's not possible to create a variable number of EC2 instances by passing Parameters to a single copy of this

问题 If you have have an autoscaling group, how do you go about start/stopping the instances ( not launch/terminate) ? The default behaviour is only for launching and terminating instances, but since we also get cost savings for just stopping an instance, we would rather allow the instance to persist. For our purposes, we have a QA environment and we want to start/stop several autoscaling groups daily to save money when the development team leaves the office for evenings and weekends. So how to

问题 What does setting the automatic_scaling max_idle_instances to zero (0) do? automatic_scaling: max_idle_instances: 0 min_idle_instances: 0 Does it cause an active instance to shutdown immediately once it has finished processing it's current requests? 回答1: Technically you can't even set max_idle_instances it to 0 , you'll see this error at deployment time: Error 400: --- begin server output --- automatic_scaling.max_idle_instances (0), must be in the range [1,1000]. --- end server output ---