You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ResourceInitializationError: failed to validate logger args: create stream has been retried 1 times: failed to create Cloudwatch log stream: MissingEndpoint: 'Endpoint' configuration is required for this service : exit status 1
#74
Closed
Droshow opened this issue
Jun 4, 2022
· 3 comments
I think one last piece is missing for me to make this Pete's masterpiece to work.
I think Docker and Cloudwatch are not communicating well, but when I check TaskDefinition , it seems that containerDefinitions are set correctly. Something I might have missed during Terraform apply, or what might it be. When I check Cloudwatch log groups, indeed I do not see any streams, but isn't this started by aws logger?
Thank you
Hello Guys,
I think one last piece is missing for me to make this Pete's masterpiece to work.
I think Docker and Cloudwatch are not communicating well, but when I check TaskDefinition , it seems that containerDefinitions are set correctly. Something I might have missed during Terraform apply, or what might it be. When I check Cloudwatch log groups, indeed I do not see any streams, but isn't this started by aws logger?
Thank you
"ipcMode": null,
"executionRoleArn": "arn:aws:iam::961477247679:role/inexhaustible_WordpressTaskRole",
"containerDefinitions": [
{
"dnsSearchDomains": null,
"environmentFiles": null,
"logConfiguration": {
"logDriver": "awslogs",
"secretOptions": null,
"options": {
"awslogs-group": "/aws/ecs/inexhaustible-serverless-wordpress-container",
"awslogs-region": "http://inex.life.s3-website-us-east-1.amazonaws.com",
"awslogs-stream-prefix": "ecs"
}
},
The text was updated successfully, but these errors were encountered: