New answers tagged

0

Turns out I needed an ECS service, not an EC2 service, in my aws_iam_role. I'd tried this before, but didn't specify sufficient in the aws_iam_role_policy . It's very much like this issue on the AWS forums. resource "aws_iam_role" "beatthemarket" { name = "beatthemarket" assume_role_policy = <<EOF { "Version": "2012-10-17", "Statement": [ ...


0

Panagiotis Moustafellos in the #devopsengineers slack channel actually helped me fix this issue. Turns out that the beatthemarket_service container does not exist. (Confusingly) It's the beatthemarkettask definition name. So I just replaced resource "aws_ecs_service" "beatthemarket_service" { name = "beatthemarket-service" cluster = ...


1

The default username for the CentOS 7 cloud image is centos. There is no password; instead you log in with the ssh key you provided at instance creation. You can then sudo and do whatever you like.



Top 50 recent answers are included