Community Plugin

gatsby-plugin-aws-elasticsearch

Version License

An experimental plugin for Gatsby to synchronise content between Gatsby and AWS Elasticsearch. You can write a GraphQL query to fetch the data, and parse it to a format which will be used for Elasticsearch.

Requirements

Node.js v10 or newer.
An AWS Elasticsearch instance, and API credentials for it.

Installation

First, install the package using npm or yarn.

yarn add -D gatsby-plugin-aws-elasticsearch

npm install --save-dev gatsby-plugin-aws-elasticsearch

Getting started

To use the plugin, add it to your gatsby-config.js:

export default {
  // ...
  plugins: [
    {
      resolve: 'gatsby-plugin-aws-elasticsearch',
      options: {
        // See below
      }
    }
  ]
}

Options

The following options are available:

enabled - Whether the plugin is enabled or not. Can be used to toggle the synchronisation. This defaults to false.
```
{
  enabled: !!process.env.ELASTIC_SYNC
}
```

query - A GraphQL query to fetch the data.

{
  query: `
    query {
      allMdx {
        nodes {
          frontmatter {
            title
          }
          excerpt
        }
      }
    }
  `
}

selector - A function which takes the raw GraphQL data and returns the nodes to process.
```
{
  selector: (data) => data.allMdx.nodes
}
```
toDocument - A function which takes a single node (from selector), and returns an object with the data to insert into Elasticsearch. The object must contain an id field, which is used as the ID for the document. Note that the data should be JSON serialisable.
```
{
  toDocument: (node) => ({
    id: node.slug,
    title: node.frontmatter.title,
    excerpt: node.excerpt
  })
}
```
endpoint - The HTTP endpoint of the Elasticsearch server. It should not have a trailing slash.
```
{
  endpoint: process.env.ELASTIC_AWS_ENDPOINT
}
```
index - The name of the index to insert the data into. If the index does not exist, it will be created.
```
{
  index: 'articles'
}
```
mapping - An object with the mapping info for the index. This will overwrite the current settings for the index. Please refer to the Elasticsearch docs for an overview of the options.
```
{
  mapping: {
    title: {
      type: 'keyword'
    },
    excerpt: {
      type: 'text'
    }
  }
}
```

accessKeyId - The AWS IAM access key ID.

{
  endpoint: process.env.ELASTIC_AWS_ACCESS_KEY_ID
}

secretAccessKey - The AWS IAM secret access key.

{
  endpoint: process.env.ELASTIC_AWS_SECRET_ACCESS_KEY
}