Added fix for ECS service-linked role (AWSServiceRoleForECS) issue #509
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for the eventual-consistency issue with the ECS service-linked role
AWSServiceRoleForECS
. Terraform is currently unable to handle the eventually-consistent nature of the ECS service-linked role and so it fails when doingterraform apply
with ECS services. In order to address this we pre-emptively create the role before running anyterraform apply
operations.More info about this terraform bug can be found here:
hashicorp/terraform-provider-aws#11417
AWS eventual-consistency is an absolute bitch.