anchor.diff:  
   Log files produced my components (Apache, Tomcat...) managed by Beanstalk are already configured.
   The above config file is only for application specific log files.
  +This agent support multiline logs (like stacktraces, call trace...) provided they start with a whitespace (space, tab). 
  +It's not as powerful as Filebeat or Logstash.
   
   At this point, you'll be able to see logs aggregated from multiple Beanstalk instances in the Cloudwatch console.
   
  
positive.code: 
  To ship logs into Cloudwatch, an AWSLogs agent is provided.
  To archive logs into S3, a script is cron-ed along with logrotate.
  
  ## Beanstalk
  
  
negative.code: The more machines you have, the more important it's to centralize logs.
  In this article, I will describe what I discovered while trying to collect logs from applications deployed on Beanstalk and send them into Elasticsearch.
  
  Disclaimer: I am an AWS newbie. 
  
  ## The family picture
  
  