- Le plus récent
- Le plus de votes
- La plupart des commentaires
Well I resolved this issue with support's help. For anyone facing this issue, the fix was pretty simple (isn't it always!?). For anyone else having this issue here is what the resolution was in my case. I created a task definition in ECS using a .json file and specified the logDriver = awslogs. Pretty standard and well documented. In my use case the task and the network configuration from the lambda had to be overriden to pass in different parameters. The subnets that I was specifying in the lambda had themselves had public IP enabled BUT from the lambda I was not specifying that this should be the case, hence the task was being called but was failing. The task needed to specify AssignPublicIp property in the network config and set it to true, for the task to do anything meaningful. Once I made this change, everything worked like a champ.
Yes, actually out of frustration I have given it AdministratorAccess. Still no dice
Does the ECS Task have the correct IAM Permissions to create/put log groups and streams to cloudwatch?
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 5 ans
- AWS OFFICIELA mis à jour il y a 5 ans
Assuming your using AWS Log Driver?
https://docs.aws.amazon.com/AmazonECS/latest/userguide/using_awslogs.html