anchor.diff:  user access to a particular project.
   ====
   
  -== Performing Elasticsearch maintenance operations
  +[[aggregate-logging-performing-elasticsearch-maintenance-operations]]
  +== Performing Elasticsearch Maintenance Operations
   
   As of the Deployer version
   ifdef::openshift-origin[]
  -1.2.0
  +1.2.0,
   endif::openshift-origin[]
   ifdef::openshift-enterprise[]
  -3.2.0
  +3.2.0,
   endif::openshift-enterprise[]
   an admin certificate, key, and CA that can be used to communicate with and perform
   administrative operations on Elasticsearch are provided within the
  
positive.code: ----
  ====
  
  If they are not available, please refer to
  xref:../install_config/upgrading/manual_upgrades.html#manual-upgrading-efk-logging-stack[Manual
  Upgrades] to ensure you are on the latest version first.
  
  Connect to an Elasticsearch pod that is in the cluster on which you are attempting
  to perform maintenance.
  
  To find a pod in a cluster use either:
  ====
  ----
  $ oc get pods -l component=es -o name | head -1
  
negative.code: from the secret to communicate with Elasticsearch per its 1.5
  link:https://www.elastic.co/guide/en/elasticsearch/reference/1.5/docs.html[Document APIs].
  
  Fluentd sends its logs to Elasticsearch using the index format "{project_name}.{project_uuid}.YYYY.MM.DD"
  where YYYY.MM.DD is the date of the log record.
  
  For example, to delete all logs for the `logging` project with uuid `3b3594fa-2ccd-11e6-acb7-0eb6b35eaee3`
  from June 15, 2016, we can run:
  
  ====
  ----
  $ curl --key /etc/elasticsearch/keys/admin-key --cert /etc/elasticsearch/keys/admin-cert \
  