Elasticsearch to aws

Hi Everyone. im new to this technology. since last week ive been trying to setup or connect my elasticsearch AWS to my local elasticsearch.
i downloaded elasticsearch 7.6.2 and kibana 7.6.2 version to my local and setup all the default. i tried to connect with http://localhost:9200/http:localhost:5601 (they're working).
now we have elasticsearch setup from AWS. i want to connect that aws ES to this elasticsearch on my local.
could please tell me how? thank you

i have already tried to edit the elasticsearch.yml. here is my settings. but this one cannot connect or start the elasticsearch service on my mac

  # ======================== 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: Dev-ES

    #

    # ------------------------------------ Node ------------------------------------

    #

    # Use a descriptive name for the node:

    #

    #node.name: node-1

    node.master: true

    node.data: true

    #

    # 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 -----------------------------------

    #

    # Set the bind address to a specific IP (IPv4 or IPv6):

    #

    #network.host: 192.168.0.1

    network.host: **.***.***.***

    #

    # Set a custom port for HTTP:

    #Set a custom port for HTTP: http://es.host.net:5601

    #

    #transport.tcp.port: 9300

    http.port: 9200

    #http.port: 5601

    #

    # 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: ["es.host.net", "[::1]"]

    discovery.zen.ping.unicast.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.

    #

    # ---------------------------------- Gateway -----------------------------------

    #

    # Block initial recovery after a full cluster restart until N nodes are started:

    #

    #gateway.recover_after_nodes: 3

    #

    # For more information, consult the gateway module documentation.

    #

    # ---------------------------------- Various -----------------------------------

    #

    # Require explicit names when deleting indices:

    #

   #action.destructive_requires_name: true

If you are using AWS Elasticsearch service you can not connect this to external nodes. You may be able to use an external Kibana, but that may be a question for AWS support.

If you instead are hosting your own nodes on AWS it is not recommended or supported to have clusters span multiple data centres or locations.

thank you for answering.
i tried to connect my aws ES endpoint using postman and it works.
but im just wondering if there is any other program to install and use like postman (except to docker which im not very well and known to that) to connect this aws ES endpoint and create kibana API.
kibana is very useful API for my workaround.

BTW did you look at https://www.elastic.co/cloud and https://aws.amazon.com/marketplace/pp/B01N6YCISK ?

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, APM, Logs UI, Infra UI, SIEM, Maps UI, AppSearch and what is coming next :slight_smile: ...

hahaha i got it now. :smiley:

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.