(Optional step) To watch for output from the service triggered by sudo systemctl, use journalctl -fu dockerĪll above commands are equivalent to execute dockerd command with the environment variables being overwritten.

Restart the docker daemon sudo systemctl restart docker.Flush the change with sudo systemctl daemon-reload.This file has to be placed directly in that directory, and may not be placed in any subdirectory.Ĭheck if the content is set up correctly with cat # cat /etc/systemd/system//nf nf can be any name, you can rename to anything if you have multiple configurations. The above command actually opens a file with the name /etc/systemd/system//nf. Add the following content to the opened file.Įnvironment='AWS_ACCESS_KEY_ID=my-aws-access-key'Įnvironment='AWS_SECRET_ACCESS_KEY=my-secret-access-key' Step 2: setup awslogs driver for docker daemon. Access key id, however, can be checked at any time.Īssume that the aws access key id and aws secret access key are my-aws-access-key and my-secret-access-key, respectively. You have to store the Secret Access Key because it will be shown only once in the AWS console when it is created. In the setting of the created user, navigate to Security Credentials to obtain Access key id and Secret Access Key.In Users, create a new user and add that user to the created group.In Groups, create a new group to include the created policy.In the end, the policy should be something like: Create a new Policy with the following credentials in the service CloudWatchLogs: DescribeLogStreams, GetLogEvents, CreateLogGroup, CreateLogStream, PutLogEvents. Open your AWS console and navigate to the IAM console.In this post, I will show how to configure docker to send logs from containers to AWS cloudwatch log.Īt the end of the tutorial, there will be several useful commands for debugging and testing.

Docker daemon logs centos