Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

Error applying terraform #32

Closed
Binternet opened this issue May 14, 2018 · 0 comments
Closed

Error applying terraform #32

Binternet opened this issue May 14, 2018 · 0 comments

Comments

@Binternet
Copy link
Contributor

Binternet commented May 14, 2018

Error: Error applying plan:

1 error(s) occurred:

* aws_autoscaling_group.elasticsearch: 1 error(s) occurred:

* aws_autoscaling_group.elasticsearch: "pelias-dev-elasticsearch": Waiting up to 10m0s: Need at least 5 healthy instances in ASG, have 0. Most recent activity: {
  ActivityId: "04058d79-c252-871b-9670-97626ce6d90a",
  AutoScalingGroupName: "pelias-dev-elasticsearch",
  Cause: "At 2018-05-14T11:36:59Z a user request created an AutoScalingGroup changing the desired capacity from 0 to 5.  At 2018-05-14T11:37:05Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 5.",
  Description: "Launching a new EC2 instance.  Status Reason: Access denied when attempting to assume role arn:aws:iam::XXXXXXX:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling. Validating load balancer configuration failed.",
  Details: "{\"Subnet ID\":\"subnet-f1bcb5ab\",\"Availability Zone\":\"us-east-1a\"}",
  EndTime: 2018-05-14 11:37:06 +0000 UTC,
  Progress: 100,
  StartTime: 2018-05-14 11:37:06.465 +0000 UTC,
  StatusCode: "Failed",
  StatusMessage: "Access denied when attempting to assume role arn:aws:iam::XXXXXXX:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling. Validating load balancer configuration failed."
}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant