Error applying plan: Unable to assume the service linked role. Please verify that the ECS service linked role exists.

[ewilde]

Description

When running make on an entirely new installation you may get this error:

Error: Error applying plan:

2 error(s) occurred:

* module.ecs_provider.aws_ecs_service.main: 1 error(s) occurred:

* aws_ecs_service.main: InvalidParameterException: Unable to assume the service linked role. Please verify that the ECS service linked role exists.
	status code: 400, request id: d967b493-82f9-11e8-9d63-f5180ba0fbef "ecs-provider"
* module.nats.aws_ecs_service.main: 1 error(s) occurred:

* aws_ecs_service.main: InvalidParameterException: Unable to assume the service linked role. Please verify that the ECS service linked role exists.
	status code: 400, request id: dab962b7-82f9-11e8-8cc5-29d47e720a04 "nats"

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Cause

This looks like an eventual consistency error, the ecs service is not waiting for the newly created role to exist in the iam service, even though it is dependant on it.

[mandatoryprogrammer]

Not sure if it's helpful to your issue, but this is a bug in Terraform:
hashicorp/terraform-provider-aws#11417

Looks like a fix will get rolled out in version 2.44.0