# Unable to start elastic search on Ubuntu AWS EC2 Instance **URL:** \ **Category:** Elasticsearch\ **Created:** [March 23, 2023, 11:40am UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343 "2023-03-23T11:40:37Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Vivek\_Burman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_burman/32/118310_2.png) [@Vivek\_Burman](https://discuss.elastic.co/u/Vivek_Burman)\ **Post date:** [March 23, 2023, 11:40am UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/1 "2023-03-23T11:40:37Z")
Hi, so following the [link](https://www.elastic.co/guide/en/elasticsearch/reference/current/targz.html#install-linux) getting the following error. ![MicrosoftTeams-image](https://us1.discourse-cdn.com/elastic/original/3X/3/6/36806519db7485f3e31ff3a51acc23d91338cac5.png) Here's my elasticsearch.yml config ```auto # ======================== Elasticsearch Configuration ========================= # # NOTE: Elasticsearch comes with reasonable defaults for most settings. # Before you set out to tweak and tune the configuration, make sure you # understand what are you trying to accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please consult the documentation for further information on configuration options: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # #cluster.name: my-application # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # #node.name: node-1 # # Add custom attributes to the node: # #node.attr.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # #path.data: /path/to/data # # Path to log files: # #path.logs: /path/to/logs # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # By default Elasticsearch is only accessible on localhost. Set a different # address here to expose this node on the network: # #network.host: 192.168.0.1 # # By default Elasticsearch listens for HTTP traffic on the first free port it # finds starting at 9200. Set a specific HTTP port here: # # http.port: 9200 # # For more information, consult the network module documentation. # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when this node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # #discovery.seed_hosts: ["host1", "host2"] # discovery.seed_hosts: [] # Bootstrap the cluster using an initial set of master-eligible nodes: # #cluster.initial_master_nodes: ["node-1", "node-2"] # # For more information, consult the discovery and cluster formation module documentation. # # --------------------------------- Readiness ---------------------------------- # # Enable an unauthenticated TCP readiness endpoint on localhost # #readiness.port: 9399 # # ---------------------------------- Various ----------------------------------- # # Allow wildcard deletion of indices: # #action.destructive_requires_name: false #----------------------- BEGIN SECURITY AUTO CONFIGURATION ----------------------- # # The following settings, TLS certificates, and keys have been automatically # generated to configure Elasticsearch security features on 23-03-2023 10:36:35 # # -------------------------------------------------------------------------------- # Enable security features xpack.security.enabled: true xpack.security.enrollment.enabled: true # Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents xpack.security.http.ssl: enabled: false keystore.path: certs/http.p12 # Enable encryption and mutual authentication between cluster nodes xpack.security.transport.ssl: enabled: false verification_mode: certificate keystore.path: certs/transport.p12 truststore.path: certs/transport.p12 # Create a new cluster with the current node only # Additional nodes can still join the cluster later cluster.initial_master_nodes: ["ip-172-31-30-6"] # Allow HTTP API connections from anywhere # Connections are encrypted and require user authentication http.host: 0.0.0.0 # Allow other nodes to join the cluster from anywhere # Connections are encrypted and mutually authenticated #transport.host: 0.0.0.0 #----------------------- END SECURITY AUTO CONFIGURATION ------------------------- ``` Note: I've tried using this link[link](https://www.elastic.co/guide/en/elasticsearch/reference/current/deb.html) as well but same issue. ---
**Author:** ![Vivek\_Burman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_burman/32/118310_2.png) [@Vivek\_Burman](https://discuss.elastic.co/u/Vivek_Burman)\ **Post date:** [March 29, 2023, 4:21am UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/2 "2023-03-29T04:21:54Z")
For any one looking for an answer setting up Java heap memory to 4GB fixed it. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [March 29, 2023, 4:42am UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/3 "2023-03-29T04:42:10Z")
Hi @Vivek_Burman I suspect that you have many other processes running on that system and elastic will try to take half the RAM up to about 30 GB and if it's not available then it won't start. So what you did is manually set it to a smaller amount and thus it started. What size is the server and do you have other processes running on it?. It's working so that's good. Just in case you're curious about the why.. ---
**Author:** ![Vivek\_Burman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vivek_burman/32/118310_2.png) [@Vivek\_Burman](https://discuss.elastic.co/u/Vivek_Burman)\ **Post date:** [March 29, 2023, 5:30am UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/4 "2023-03-29T05:30:52Z")
`elastic will try to take half the RAM up to about 30 GB` Interesting I didn't knew this. Is it how Elastic Search works? Ya, so we have couple of other processes running on same machine. The server has 32 GB RAM ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [March 29, 2023, 1:52pm UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/5 "2023-03-29T13:52:35Z")
Perhaps take a look at this > **[Advanced configuration | Elasticsearch Guide \[8.6\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/advanced-configuration.html#set-jvm-heap-size)** ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 26, 2023, 1:53pm UTC](https://discuss.elastic.co/t/unable-to-start-elastic-search-on-ubuntu-aws-ec2-instance/328343/6 "2023-04-26T13:53:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.