-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IAM error when deploying LoadBalancedFargateService #1279
Labels
Comments
Totally should. This must be a new check (re:Invent?) because we have integration tests for this. Also, you're adding EC2 capacity to a cluster you're ending up running a Fargate service on. The capacity is not necessary there. Maybe we should have called it addEc2Capacity? (cc @SoManyHs ) |
rix0rrr
added
bug
This issue is a bug.
@aws-cdk/aws-ecs
Related to Amazon Elastic Container
labels
Dec 4, 2018
+1 |
I hit this on 0.18.1 and 0.19.0 |
rix0rrr
added a commit
that referenced
this issue
Dec 5, 2018
Make sure that tasks using the 'awslogs' Log Driver have the correct IAM permissions to actually write logs. Add grant() methods to IAM LogGroups to make this nicer to write. Fixes #1279.
9 tasks
rix0rrr
added a commit
that referenced
this issue
Dec 6, 2018
Make sure that tasks using the 'awslogs' Log Driver have the correct IAM permissions to actually write logs. Add grant() methods to IAM LogGroups to make this nicer to write. Fixes #1279.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given the following:
I get the following error on
cdk deploy
:This feels like something that should be setup as part of the default experience.
The text was updated successfully, but these errors were encountered: