Once you have a repository set up on S3, we need to ensure that actual snapshots are taken periodically. What this means is that we need a scheduled job that triggers the command to take a snapshot at regular intervals. The interval could be 15 minutes, 30 minutes, one hour, and so on, depending on the sensitivity of your data. We will see how to establish the snapshot/restore process for your cluster in depth later in this chapter.

These are some of the considerations that you have to address while running Elasticsearch in production on AWS or other clouds. 

So far, we have covered how to get your production up and running on a managed cloud or self-hosted environment. If you opted to self-host, you will need to set up a backup and restore process so that you don't lose your data. The next section is only applicable if you are self-hosting your Elasticsearch cluster.