anchor.diff:          num_threads 8
         </match>
   
  -It uses the log group name of `kubernetes-logs` and the log stream name of `fluentd-cloudwatch`. If a different log group name is used in the previous command or a different log stream name is needed, then that needs to be configured in this configuration file.
  +It uses the default log group name of `kubernetes-logs` and the log stream name of `fluentd-cloudwatch`. 
  +
  +If you've followed the instructions in this chapter as is, then no change is required in this configuration file. However if a different log group name is used in the previous command or a different log stream name is needed, then that needs to be configured in this configuration file.
   
   === IAM configuration
   
  
positive.code:       --ebs-options EBSEnabled=true,VolumeType=standard,VolumeSize=100 \
        --access-policies '{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"AWS":["*"]},"Action":["es:*"],"Resource":"*"}]}'
  
  It takes a little while for the cluster to be created and arrive at an `active` state. The AWS Console should show the following status when the cluster is ready:
  
  image::logging-cloudwatch-es-cluster.png[]
  
  
negative.code: Create a CloudWatch log group:
  
      aws logs create-log-group --log-group-name kubernetes-logs
  
  == Deploy Fluentd
  
  