title: AWS Elasticsearch exceeded limit of total fields in index
body: <p>I'm running <code>Elasticsearch</code> on <code>AWS</code>, and haven't quite understood how to properly address this issue.</p>
  
  <p>Right now I have the items stored on <code>DynamoDb</code> and use <code>dynamodb streams</code> to send the items to a lambda that then uses <a href="https://www.npmjs.com/package/dynamodb-stream-elasticsearch" rel="nofollow noreferrer">dynamodb-stream-elasticsearch</a> to send them to elasticsearch when they are created/updated.</p>
  
  <p>Some properties can be objects which have many nested properties which can themselves be objects, and when these new fields were added, is when I first started getting this error. Due to the nature of these items, these new properties will need to be searchable in the future.</p>
  
  <p>Initially the default index value had not been changed. After my first search on how to fix this I increased the limit to 5000 and now have had to increase it to 12000. The instance type is a t2.small.elasticsearch. The aws elasticsearch console is already reporting the instance health as yellow after I increased the index limit.</p>
  
  <p>Which is the best way to tackle this sort of situation? </p>
  
  <p>Does increasing the instance type fix it or is it a matter of breaking up the item and having multiple separate indexes? If the solution is the latter, is there a good tutorial/guide on how to do this with this set-up (aws dynamodb/elasticsearch)?</p>