anchor.diff:      RetentionInDays: 30
   ----
   This sets up the Cloudwatch log agent.
  -You can also install it on any EC2 instance with yum:
  +Provided you're using an image based on Amazon Linux, you can also install it on any EC2 instance with yum:
   
   [source,shell]
   ----
  
positive.code: 
  Log files produced my components (Apache, Tomcat...) managed by Beanstalk are already configured.
  The above config file is only for application specific log files.
  
  At this point, you'll be able to see logs aggregated from multiple Beanstalk instances in the Cloudwatch console.
  
  
negative.code: https://medium.com/wolox-driving-innovation/centralized-logging-in-microservices-using-aws-cloudwatch-elasticsearch-f5db7a57e553[This article] is worth reading.
  
  At this point, we can open Kibana and configure an index pattern named `cwl-*`.
  Cloudwatch log filter mimics Logstash and uses a field named `@timestamp` for timestamp
  
  ## Conclusion
  
  AWS provides all the building blocks to collect logs and monitor your whole infrastructure.
  It's not hard to collect logs and send them in Elasticsearch.
  But it's also far less powerful than the complete Elastic stack.
  
  