# Elastic on Azure App Service / Google App Engine? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 22, 2017, 10:29pm UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984 "2017-08-22T22:29:29Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![N\_Vignesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/n_vignesh/32/21393_2.png) [@N\_Vignesh](https://discuss.elastic.co/u/N_Vignesh)\ **Post date:** [August 22, 2017, 10:29pm UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984/1 "2017-08-22T22:29:29Z")
I have been working on the ELK stack locally on my dev laptop for a while and now would like to build a real world application. I am looking at hosting my app on **Azure / Google App Engine** I was reading the Elastic [hardware requirement](https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html) at it mentions 64GB RAM being the sweet spot. However I am just planning to build a experimental app for my own academic interest. My question here is can I install a single elastic node on either Azure / Google App Engine and have the client also running on the same machine ? I am looking to store about 30,000-40,000 records and build a simple search UI to query the elastic indices. There are a tabular data which I have converted to json documents. Thanks ---
**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\ **Post date:** [August 23, 2017, 10:17am UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984/2 "2017-08-23T10:17:59Z")
You can install a single node Elasticsearch instance, no problem. If you need fault tolerance and high availability, you may consider running with a cluster of nodes, recommended minimum of 3 to avoid split brain scenarios. If you're looking to spin up a cluster on Azure, take a look at the Elastic ARM template offering available in both the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/elastic.elasticsearch) and deployable from the [Github repository](https://github.com/elastic/azure-marketplace). With the template, you can easily spin up a single node Elasticsearch cluster. ---
**Author:** ![N\_Vignesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/n_vignesh/32/21393_2.png) [@N\_Vignesh](https://discuss.elastic.co/u/N_Vignesh)\ **Post date:** [August 24, 2017, 10:15pm UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984/3 "2017-08-24T22:15:18Z")
thanks for the reply, I know this might be rudimentary but for my experimental can I have master and slave nodes on the same server ? ---
**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\ **Post date:** [August 24, 2017, 11:32pm UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984/4 "2017-08-24T23:32:20Z")
> [@N\_Vignesh](#): > > can I have master and slave nodes on the same server ? The Azure ARM template only deploys a single Elasticsearch node _per_ Virtual Machine, but a single node can have all the roles of master, data and ingest node. If you'd like to run multiple Elasticsearch nodes on a single machine, then using the ARM template as a starting point may be helpful. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 21, 2017, 11:32pm UTC](https://discuss.elastic.co/t/elastic-on-azure-app-service-google-app-engine/97984/5 "2017-09-21T23:32:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.