Found 15 possible answers.
|User||Answered At||Possible Answer|
Launching a new EC2 instance. Status Reason: Volume of size 8GB is smaller than snapshot 'snap-xxxxxxxxxxxxx', expect size >= 10GB. Launching EC2 instance failed.
- use the change of launchconfig event from cloudtrail, get it to trigger a lambda which doubles size of the associated ASG, waits for nodes to be healthy then scales back in. You need to set correct termination policy to ensure oldest instances are retired [May 4th, 2018 9:16 AM] ghardy: We are doing ASGs in Terraform, When we create a new launch config, we want the old instances using the old launch config to terminate, and spin up new instances with the new launch config, at the moment. I have to manually terminate the instances, then they get span up with the new one, anyone have any ideas how to automate this?
- launch config ?
- How old is it?
- hey, does terraform support launch templates yet?
- @jmsb doesn't user data just run on launch? your existing instances shouldn't be affected
- Does anyone have a sense of how much difference using a placement group makes? I’m stuck up against instance capacity limits in us-east-1a, trying to decide whether to launch new instances outside the group. Running a Cassandra cluster
- Heyo, autoscaling q: if I update a launch configuration, is there a way to automatically trigger my ASG to replace the instance using my new launch configuration, or do I just kill the instance manually and let the ASG fire up a new one? Looks like I forgot the cidr blocks section in my egress rules... Bloody security groups balls, my egress rule in the SG isn't showing up hm, did it manually, but now my target group seems to be hitting port 80 instead of the assigned ephemeral port of my container in ECS
- A bit late of a reply. We are using vanilla CF templates (built using troposphere). We create a template for the VPC (containing multi az pub/private subnets etc..) and then a template for the resources that go in the VPC. Then theres a template which launches both together (if needed) using nested stacks or we can launch each separately (so if the VPC already exists or is setup a different way we can launch into that VPC) A bit late of a reply. We are using vanilla CF templates (built using troposphere). We create a template for the VPC (containing multi az pub/private subnets etc..) and then a template for the resources that go in the VPC. Then theres a template which launches both together (if needed) using nested stacks or we can launch each separately (so if the VPC already exists or is setup a different way we can launch into that VPC) [August 23rd, 2017 2:18 PM] konrad: Setting up ECS with Terraform and slightly confused about the VPC setup. Looks like most configurations create the VPC, define a security group for it and assign the security group to the launch configuration. Is that how the ECS instances get launched into the VPC?
- has anyone experienced problem with k8s like when you roll out new deployment with new image tag version, new replicaset for it not created and pods with new image tag are not created?
- @coderanger thanks for your quick response. So basically that means building a new image and updating the launch config with it. In that case can I manually replace the ami id in some parameters file and update the stack? I plan to have a file that would hold all the parameters which get passed to the cf template.