Elastic Content Share

How to Upload Elastic Content

Learn how to upload Elastic content with clear descriptions, screenshots, versions, tags, and files ready for community review.

How to upload Elastic content

This upload guide explains how to share Elastic content with the community. You can submit dashboards, rules, pipelines, saved objects, Dev Tools scripts, workflows, and other examples that help Elastic users solve practical problems.

Before uploading, prepare the file, description, screenshot, source link, and version details. The better the context, the easier it is for another user to decide whether the download fits their environment.

What file formats are accepted?

Upload ZIP files whenever possible. A ZIP can contain Kibana saved-object NDJSON, Elasticsearch JSON, Logstash pipeline configs, Dev Tools scripts, Canvas workpads, Vega specs, README files, screenshots, and license notes. Direct JSON uploads are restricted for security reasons.

Why do good descriptions matter?

A useful description explains the problem, the expected input data, the target Elastic product, and the result the user should see. It should also mention limitations, manual review steps, and whether the content was tested with a specific Elastic version.

Step by step guide

  1. Apply for or log in with an approved content creator account.
  2. Open the upload page.
  3. Add a descriptive title, a short excerpt, a detailed body, categories, tags, and version information.
  4. Upload a ZIP file and insert the file URL so the download is attached correctly.
  5. Submit the content for review. Moderators check usability, copy quality, duplicate risk, and category fit.
Elastic content upload screen with Insert File URL button

Automatic deployment

Some downloads can be deployed automatically into Elastic Cloud. To support that workflow, export Kibana objects through Saved Objects and keep the exported filename unchanged. For Dev Tools scripts, create a file named devtools.script and test the commands in Kibana first.

Package the files in the root of the ZIP. You can include extra documentation, but the deploy flow expects importable files such as NDJSON and Dev Tools scripts to be easy to find.

Who reviews submissions?

Elastic Content Share reviewers check whether the content is safe to offer, useful to users, and documented clearly. Review can take a few days. If details are missing, the item may stay as a draft until it is ready.

Helpful links

Start with Creators Corner, then use Add Your Elastic Content. Review examples in Kibana dashboards, Watcher examples, and Logstash pipelines.