{"id":14957867,"url":"https://github.com/cloudposse/terraform-aws-elasticsearch","last_synced_at":"2025-05-15T18:06:21.103Z","repository":{"id":33703168,"uuid":"141645281","full_name":"cloudposse/terraform-aws-elasticsearch","owner":"cloudposse","description":"Terraform module to provision an Elasticsearch cluster with built-in integrations with Kibana and Logstash.","archived":false,"fork":false,"pushed_at":"2025-01-01T06:46:51.000Z","size":4312,"stargazers_count":219,"open_issues_count":31,"forks_count":229,"subscribers_count":23,"default_branch":"main","last_synced_at":"2025-03-31T22:18:28.232Z","etag":null,"topics":["aws","efk","elasticsearch","elk","fluentd","hcl2","kibana","terraform","terraform-module"],"latest_commit_sha":null,"homepage":"https://cloudposse.com/accelerate","language":"HCL","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cloudposse.png","metadata":{"funding":{"github":"cloudposse"},"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-07-20T00:51:21.000Z","updated_at":"2025-01-01T03:10:27.000Z","dependencies_parsed_at":"2023-11-15T04:22:24.671Z","dependency_job_id":"43a0cff3-8ec6-4ed1-a1dc-1df2794b570c","html_url":"https://github.com/cloudposse/terraform-aws-elasticsearch","commit_stats":{"total_commits":94,"total_committers":49,"mean_commits":"1.9183673469387754","dds":0.8829787234042553,"last_synced_commit":"8046e8647e5939ceb6b9bded5b6cd072234179ab"},"previous_names":[],"tags_count":72,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-elasticsearch","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-elasticsearch/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-elasticsearch/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-elasticsearch/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cloudposse","download_url":"https://codeload.github.com/cloudposse/terraform-aws-elasticsearch/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247744332,"owners_count":20988783,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["aws","efk","elasticsearch","elk","fluentd","hcl2","kibana","terraform","terraform-module"],"created_at":"2024-09-24T13:15:44.183Z","updated_at":"2025-05-15T18:06:21.088Z","avatar_url":"https://github.com/cloudposse.png","language":"HCL","funding_links":["https://github.com/sponsors/cloudposse"],"categories":[],"sub_categories":[],"readme":"\n\n\u003c!-- markdownlint-disable --\u003e\n\u003ca href=\"https://cpco.io/homepage\"\u003e\u003cimg src=\"https://github.com/cloudposse/terraform-aws-elasticsearch/blob/main/.github/banner.png?raw=true\" alt=\"Project Banner\"/\u003e\u003c/a\u003e\u003cbr/\u003e\n    \u003cp align=\"right\"\u003e\n\u003ca href=\"https://github.com/cloudposse/terraform-aws-elasticsearch/releases/latest\"\u003e\u003cimg src=\"https://img.shields.io/github/release/cloudposse/terraform-aws-elasticsearch.svg?style=for-the-badge\" alt=\"Latest Release\"/\u003e\u003c/a\u003e\u003ca href=\"https://github.com/cloudposse/terraform-aws-elasticsearch/commits\"\u003e\u003cimg src=\"https://img.shields.io/github/last-commit/cloudposse/terraform-aws-elasticsearch.svg?style=for-the-badge\" alt=\"Last Updated\"/\u003e\u003c/a\u003e\u003ca href=\"https://slack.cloudposse.com\"\u003e\u003cimg src=\"https://slack.cloudposse.com/for-the-badge.svg\" alt=\"Slack Community\"/\u003e\u003c/a\u003e\u003c/p\u003e\n\u003c!-- markdownlint-restore --\u003e\n\n\u003c!--\n\n\n\n\n  ** DO NOT EDIT THIS FILE\n  **\n  ** This file was automatically generated by the `cloudposse/build-harness`.\n  ** 1) Make all changes to `README.yaml`\n  ** 2) Run `make init` (you only need to do this once)\n  ** 3) Run`make readme` to rebuild this file.\n  **\n  ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)\n  **\n\n\n\n\n\n--\u003e\n\nTerraform module to provision an [`Elasticsearch`](https://aws.amazon.com/elasticsearch-service/) cluster with built-in integrations with [Kibana](https://aws.amazon.com/elasticsearch-service/kibana/) and [Logstash](https://aws.amazon.com/elasticsearch-service/logstash/).\n\n\n\u003e [!TIP]\n\u003e #### 👽 Use Atmos with Terraform\n\u003e Cloud Posse uses [`atmos`](https://atmos.tools) to easily orchestrate multiple environments using Terraform. \u003cbr/\u003e\n\u003e Works with [Github Actions](https://atmos.tools/integrations/github-actions/), [Atlantis](https://atmos.tools/integrations/atlantis), or [Spacelift](https://atmos.tools/integrations/spacelift).\n\u003e\n\u003e \u003cdetails\u003e\n\u003e \u003csummary\u003e\u003cstrong\u003eWatch demo of using Atmos with Terraform\u003c/strong\u003e\u003c/summary\u003e\n\u003e \u003cimg src=\"https://github.com/cloudposse/atmos/blob/main/docs/demo.gif?raw=true\"/\u003e\u003cbr/\u003e\n\u003e \u003ci\u003eExample of running \u003ca href=\"https://atmos.tools\"\u003e\u003ccode\u003eatmos\u003c/code\u003e\u003c/a\u003e to manage infrastructure from our \u003ca href=\"https://atmos.tools/quick-start/\"\u003eQuick Start\u003c/a\u003e tutorial.\u003c/i\u003e\n\u003e \u003c/detalis\u003e\n\n\n## Introduction\n\nThis module will create:\n- Elasticsearch cluster with the specified node count in the provided subnets in a VPC\n- Elasticsearch domain policy that accepts a list of IAM role ARNs from which to permit management traffic to the cluster\n- Security Group to control access to the Elasticsearch domain (inputs to the Security Group are other Security Groups or CIDRs blocks to be allowed to connect to the cluster)\n- DNS hostname record for Elasticsearch cluster (if DNS Zone ID is provided)\n- DNS hostname record for Kibana (if DNS Zone ID is provided)\n\n__NOTE:__ To enable [zone awareness](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-managedomains.html#es-managedomains-zoneawareness) to deploy Elasticsearch nodes into two different Availability Zones, you need to set `zone_awareness_enabled` to `true` and provide two different subnets in `subnet_ids`.\nIf you enable zone awareness for your domain, Amazon ES places an endpoint into two subnets.\nThe subnets must be in different Availability Zones in the same region.\nIf you don't enable zone awareness, Amazon ES places an endpoint into only one subnet. You also need to set `availability_zone_count` to `1`.\n\n\n\n\n## Usage\n\n\n```hcl\nmodule \"elasticsearch\" {\n  source = \"cloudposse/elasticsearch/aws\"\n  # Cloud Posse recommends pinning every module to a specific version\n  # version     = \"x.x.x\"\n  namespace               = \"eg\"\n  stage                   = \"dev\"\n  name                    = \"es\"\n  dns_zone_id             = \"Z14EN2YD427LRQ\"\n  security_groups         = [\"sg-XXXXXXXXX\", \"sg-YYYYYYYY\"]\n  vpc_id                  = \"vpc-XXXXXXXXX\"\n  subnet_ids              = [\"subnet-XXXXXXXXX\", \"subnet-YYYYYYYY\"]\n  zone_awareness_enabled  = true\n  elasticsearch_version   = \"6.5\"\n  instance_type           = \"t2.small.elasticsearch\"\n  instance_count          = 4\n  ebs_volume_size         = 10\n  iam_role_arns           = [\"arn:aws:iam::XXXXXXXXX:role/ops\", \"arn:aws:iam::XXXXXXXXX:role/dev\"]\n  iam_actions             = [\"es:ESHttpGet\", \"es:ESHttpPut\", \"es:ESHttpPost\"]\n  encrypt_at_rest_enabled = true\n  kibana_subdomain_name   = \"kibana-es\"\n\n  advanced_options = {\n    \"rest.action.multi.allow_explicit_index\" = \"true\"\n  }\n}\n```\n\n\u003e [!IMPORTANT]\n\u003e In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation\n\u003e and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version\n\u003e you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic\n\u003e approach for updating versions to avoid unexpected changes.\n\n\n\n\n\n## Examples\n\nHere is a working example of using this module:\n- [`examples/complete`](examples/complete)\n\nHere are automated tests for the complete example using [bats](https://github.com/bats-core/bats-core) and [Terratest](https://github.com/gruntwork-io/terratest) (which tests and deploys the example on AWS):\n- [`test`](test)\n\n\n\n\n\u003c!-- markdownlint-disable --\u003e\n## Makefile Targets\n```text\nAvailable targets:\n\n  help                                Help screen\n  help/all                            Display help for all targets\n  help/short                          This help short screen\n  lint                                Lint terraform code\n\n```\n\u003c!-- markdownlint-restore --\u003e\n\u003c!-- markdownlint-disable --\u003e\n## Requirements\n\n| Name | Version |\n|------|---------|\n| \u003ca name=\"requirement_terraform\"\u003e\u003c/a\u003e [terraform](#requirement\\_terraform) | \u003e= 1.3 |\n| \u003ca name=\"requirement_aws\"\u003e\u003c/a\u003e [aws](#requirement\\_aws) | \u003e= 3.35.0 |\n\n## Providers\n\n| Name | Version |\n|------|---------|\n| \u003ca name=\"provider_aws\"\u003e\u003c/a\u003e [aws](#provider\\_aws) | \u003e= 3.35.0 |\n\n## Modules\n\n| Name | Source | Version |\n|------|--------|---------|\n| \u003ca name=\"module_domain_hostname\"\u003e\u003c/a\u003e [domain\\_hostname](#module\\_domain\\_hostname) | cloudposse/route53-cluster-hostname/aws | 0.12.3 |\n| \u003ca name=\"module_kibana_hostname\"\u003e\u003c/a\u003e [kibana\\_hostname](#module\\_kibana\\_hostname) | cloudposse/route53-cluster-hostname/aws | 0.12.3 |\n| \u003ca name=\"module_kibana_label\"\u003e\u003c/a\u003e [kibana\\_label](#module\\_kibana\\_label) | cloudposse/label/null | 0.25.0 |\n| \u003ca name=\"module_this\"\u003e\u003c/a\u003e [this](#module\\_this) | cloudposse/label/null | 0.25.0 |\n| \u003ca name=\"module_user_label\"\u003e\u003c/a\u003e [user\\_label](#module\\_user\\_label) | cloudposse/label/null | 0.25.0 |\n\n## Resources\n\n| Name | Type |\n|------|------|\n| [aws_elasticsearch_domain.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain) | resource |\n| [aws_elasticsearch_domain_policy.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticsearch_domain_policy) | resource |\n| [aws_iam_role.elasticsearch_user](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role) | resource |\n| [aws_iam_service_linked_role.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_service_linked_role) | resource |\n| [aws_opensearch_domain.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/opensearch_domain) | resource |\n| [aws_opensearch_domain_policy.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/opensearch_domain_policy) | resource |\n| [aws_security_group.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group) | resource |\n| [aws_security_group_rule.egress](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule) | resource |\n| [aws_security_group_rule.ingress_cidr_blocks](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule) | resource |\n| [aws_security_group_rule.ingress_security_groups](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule) | resource |\n| [aws_iam_policy_document.assume_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |\n| [aws_iam_policy_document.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |\n\n## Inputs\n\n| Name | Description | Type | Default | Required |\n|------|-------------|------|---------|:--------:|\n| \u003ca name=\"input_additional_tag_map\"\u003e\u003c/a\u003e [additional\\_tag\\_map](#input\\_additional\\_tag\\_map) | Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.\u003cbr/\u003eThis is for some rare cases where resources want additional configuration of tags\u003cbr/\u003eand therefore take a list of maps with tag key, value, and additional configuration. | `map(string)` | `{}` | no |\n| \u003ca name=\"input_advanced_options\"\u003e\u003c/a\u003e [advanced\\_options](#input\\_advanced\\_options) | Key-value string pairs to specify advanced configuration options | `map(string)` | `{}` | no |\n| \u003ca name=\"input_advanced_security_options_enabled\"\u003e\u003c/a\u003e [advanced\\_security\\_options\\_enabled](#input\\_advanced\\_security\\_options\\_enabled) | AWS Elasticsearch Kibana enchanced security plugin enabling (forces new resource) | `bool` | `false` | no |\n| \u003ca name=\"input_advanced_security_options_internal_user_database_enabled\"\u003e\u003c/a\u003e [advanced\\_security\\_options\\_internal\\_user\\_database\\_enabled](#input\\_advanced\\_security\\_options\\_internal\\_user\\_database\\_enabled) | Whether to enable or not internal Kibana user database for ELK OpenDistro security plugin | `bool` | `false` | no |\n| \u003ca name=\"input_advanced_security_options_master_user_arn\"\u003e\u003c/a\u003e [advanced\\_security\\_options\\_master\\_user\\_arn](#input\\_advanced\\_security\\_options\\_master\\_user\\_arn) | ARN of IAM user who is to be mapped to be Kibana master user (applicable if advanced\\_security\\_options\\_internal\\_user\\_database\\_enabled set to false) | `string` | `\"\"` | no |\n| \u003ca name=\"input_advanced_security_options_master_user_name\"\u003e\u003c/a\u003e [advanced\\_security\\_options\\_master\\_user\\_name](#input\\_advanced\\_security\\_options\\_master\\_user\\_name) | Master user username (applicable if advanced\\_security\\_options\\_internal\\_user\\_database\\_enabled set to true) | `string` | `\"\"` | no |\n| \u003ca name=\"input_advanced_security_options_master_user_password\"\u003e\u003c/a\u003e [advanced\\_security\\_options\\_master\\_user\\_password](#input\\_advanced\\_security\\_options\\_master\\_user\\_password) | Master user password (applicable if advanced\\_security\\_options\\_internal\\_user\\_database\\_enabled set to true) | `string` | `\"\"` | no |\n| \u003ca name=\"input_allowed_cidr_blocks\"\u003e\u003c/a\u003e [allowed\\_cidr\\_blocks](#input\\_allowed\\_cidr\\_blocks) | List of CIDR blocks to be allowed to connect to the cluster | `list(string)` | `[]` | no |\n| \u003ca name=\"input_anonymous_iam_actions\"\u003e\u003c/a\u003e [anonymous\\_iam\\_actions](#input\\_anonymous\\_iam\\_actions) | List of actions to allow for the anonymous (`*`) IAM roles, _e.g._ `es:ESHttpGet`, `es:ESHttpPut`, `es:ESHttpPost` | `list(string)` | `[]` | no |\n| \u003ca name=\"input_attributes\"\u003e\u003c/a\u003e [attributes](#input\\_attributes) | ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,\u003cbr/\u003ein the order they appear in the list. New attributes are appended to the\u003cbr/\u003eend of the list. The elements of the list are joined by the `delimiter`\u003cbr/\u003eand treated as a single ID element. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_auto_tune\"\u003e\u003c/a\u003e [auto\\_tune](#input\\_auto\\_tune) | This object represents the auto\\_tune configuration. It contains the following filed:\u003cbr/\u003e- enabled - Whether to enable autotune.\u003cbr/\u003e- rollback\\_on\\_disable - Whether to roll back to default Auto-Tune settings when disabling Auto-Tune.\u003cbr/\u003e- starting\\_time - Date and time at which to start the Auto-Tune maintenance schedule in RFC3339 format. Time should be in the future.\u003cbr/\u003e- cron\\_schedule - A cron expression specifying the recurrence pattern for an Auto-Tune maintenance schedule.\u003cbr/\u003e- duration - Autotune maintanance window duration time in hours. | \u003cpre\u003eobject({\u003cbr/\u003e    enabled             = bool\u003cbr/\u003e    rollback_on_disable = string\u003cbr/\u003e    starting_time       = string\u003cbr/\u003e    cron_schedule       = string\u003cbr/\u003e    duration            = number\u003cbr/\u003e  })\u003c/pre\u003e | \u003cpre\u003e{\u003cbr/\u003e  \"cron_schedule\": null,\u003cbr/\u003e  \"duration\": null,\u003cbr/\u003e  \"enabled\": false,\u003cbr/\u003e  \"rollback_on_disable\": \"NO_ROLLBACK\",\u003cbr/\u003e  \"starting_time\": null\u003cbr/\u003e}\u003c/pre\u003e | no |\n| \u003ca name=\"input_automated_snapshot_start_hour\"\u003e\u003c/a\u003e [automated\\_snapshot\\_start\\_hour](#input\\_automated\\_snapshot\\_start\\_hour) | Hour at which automated snapshots are taken, in UTC | `number` | `0` | no |\n| \u003ca name=\"input_availability_zone_count\"\u003e\u003c/a\u003e [availability\\_zone\\_count](#input\\_availability\\_zone\\_count) | Number of Availability Zones for the domain to use. | `number` | `2` | no |\n| \u003ca name=\"input_aws_ec2_service_name\"\u003e\u003c/a\u003e [aws\\_ec2\\_service\\_name](#input\\_aws\\_ec2\\_service\\_name) | AWS EC2 Service Name | `list(string)` | \u003cpre\u003e[\u003cbr/\u003e  \"ec2.amazonaws.com\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_aws_service_type\"\u003e\u003c/a\u003e [aws\\_service\\_type](#input\\_aws\\_service\\_type) | The type of AWS service to deploy (`elasticsearch` or `opensearch`). | `string` | `\"elasticsearch\"` | no |\n| \u003ca name=\"input_cognito_authentication_enabled\"\u003e\u003c/a\u003e [cognito\\_authentication\\_enabled](#input\\_cognito\\_authentication\\_enabled) | Whether to enable Amazon Cognito authentication with Kibana | `bool` | `false` | no |\n| \u003ca name=\"input_cognito_iam_role_arn\"\u003e\u003c/a\u003e [cognito\\_iam\\_role\\_arn](#input\\_cognito\\_iam\\_role\\_arn) | ARN of the IAM role that has the AmazonESCognitoAccess policy attached | `string` | `\"\"` | no |\n| \u003ca name=\"input_cognito_identity_pool_id\"\u003e\u003c/a\u003e [cognito\\_identity\\_pool\\_id](#input\\_cognito\\_identity\\_pool\\_id) | The ID of the Cognito Identity Pool to use | `string` | `\"\"` | no |\n| \u003ca name=\"input_cognito_user_pool_id\"\u003e\u003c/a\u003e [cognito\\_user\\_pool\\_id](#input\\_cognito\\_user\\_pool\\_id) | The ID of the Cognito User Pool to use | `string` | `\"\"` | no |\n| \u003ca name=\"input_cold_storage_enabled\"\u003e\u003c/a\u003e [cold\\_storage\\_enabled](#input\\_cold\\_storage\\_enabled) | Enables cold storage support. | `bool` | `false` | no |\n| \u003ca name=\"input_context\"\u003e\u003c/a\u003e [context](#input\\_context) | Single object for setting entire context at once.\u003cbr/\u003eSee description of individual variables for details.\u003cbr/\u003eLeave string and numeric variables as `null` to use default value.\u003cbr/\u003eIndividual variable settings (non-null) override settings in context object,\u003cbr/\u003eexcept for attributes, tags, and additional\\_tag\\_map, which are merged. | `any` | \u003cpre\u003e{\u003cbr/\u003e  \"additional_tag_map\": {},\u003cbr/\u003e  \"attributes\": [],\u003cbr/\u003e  \"delimiter\": null,\u003cbr/\u003e  \"descriptor_formats\": {},\u003cbr/\u003e  \"enabled\": true,\u003cbr/\u003e  \"environment\": null,\u003cbr/\u003e  \"id_length_limit\": null,\u003cbr/\u003e  \"label_key_case\": null,\u003cbr/\u003e  \"label_order\": [],\u003cbr/\u003e  \"label_value_case\": null,\u003cbr/\u003e  \"labels_as_tags\": [\u003cbr/\u003e    \"unset\"\u003cbr/\u003e  ],\u003cbr/\u003e  \"name\": null,\u003cbr/\u003e  \"namespace\": null,\u003cbr/\u003e  \"regex_replace_chars\": null,\u003cbr/\u003e  \"stage\": null,\u003cbr/\u003e  \"tags\": {},\u003cbr/\u003e  \"tenant\": null\u003cbr/\u003e}\u003c/pre\u003e | no |\n| \u003ca name=\"input_create_elasticsearch_user_role\"\u003e\u003c/a\u003e [create\\_elasticsearch\\_user\\_role](#input\\_create\\_elasticsearch\\_user\\_role) | Whether to create an IAM role for Users/EC2 to assume to access the Elasticsearch domain. Set it to `false` if you already manage access through other means. | `bool` | `true` | no |\n| \u003ca name=\"input_create_iam_service_linked_role\"\u003e\u003c/a\u003e [create\\_iam\\_service\\_linked\\_role](#input\\_create\\_iam\\_service\\_linked\\_role) | Whether to create `AWSServiceRoleForAmazonElasticsearchService` service-linked role. Set it to `false` if you already have an ElasticSearch cluster created in the AWS account and AWSServiceRoleForAmazonElasticsearchService already exists. See https://github.com/terraform-providers/terraform-provider-aws/issues/5218 for more info | `bool` | `true` | no |\n| \u003ca name=\"input_create_security_group\"\u003e\u003c/a\u003e [create\\_security\\_group](#input\\_create\\_security\\_group) | Whether to create a dedicated security group for the Elasticsearch domain. Set it to `false` if you already have security groups that you want to attach to the domain and specify them in the `security_groups` variable. | `bool` | `true` | no |\n| \u003ca name=\"input_custom_endpoint\"\u003e\u003c/a\u003e [custom\\_endpoint](#input\\_custom\\_endpoint) | Fully qualified domain for custom endpoint. | `string` | `\"\"` | no |\n| \u003ca name=\"input_custom_endpoint_certificate_arn\"\u003e\u003c/a\u003e [custom\\_endpoint\\_certificate\\_arn](#input\\_custom\\_endpoint\\_certificate\\_arn) | ACM certificate ARN for custom endpoint. | `string` | `\"\"` | no |\n| \u003ca name=\"input_custom_endpoint_enabled\"\u003e\u003c/a\u003e [custom\\_endpoint\\_enabled](#input\\_custom\\_endpoint\\_enabled) | Whether to enable custom endpoint for the Elasticsearch domain. | `bool` | `false` | no |\n| \u003ca name=\"input_dedicated_master_count\"\u003e\u003c/a\u003e [dedicated\\_master\\_count](#input\\_dedicated\\_master\\_count) | Number of dedicated master nodes in the cluster | `number` | `0` | no |\n| \u003ca name=\"input_dedicated_master_enabled\"\u003e\u003c/a\u003e [dedicated\\_master\\_enabled](#input\\_dedicated\\_master\\_enabled) | Indicates whether dedicated master nodes are enabled for the cluster | `bool` | `false` | no |\n| \u003ca name=\"input_dedicated_master_type\"\u003e\u003c/a\u003e [dedicated\\_master\\_type](#input\\_dedicated\\_master\\_type) | Instance type of the dedicated master nodes in the cluster | `string` | `\"t2.small.elasticsearch\"` | no |\n| \u003ca name=\"input_delimiter\"\u003e\u003c/a\u003e [delimiter](#input\\_delimiter) | Delimiter to be used between ID elements.\u003cbr/\u003eDefaults to `-` (hyphen). Set to `\"\"` to use no delimiter at all. | `string` | `null` | no |\n| \u003ca name=\"input_descriptor_formats\"\u003e\u003c/a\u003e [descriptor\\_formats](#input\\_descriptor\\_formats) | Describe additional descriptors to be output in the `descriptors` output map.\u003cbr/\u003eMap of maps. Keys are names of descriptors. Values are maps of the form\u003cbr/\u003e`{\u003cbr/\u003e   format = string\u003cbr/\u003e   labels = list(string)\u003cbr/\u003e}`\u003cbr/\u003e(Type is `any` so the map values can later be enhanced to provide additional options.)\u003cbr/\u003e`format` is a Terraform format string to be passed to the `format()` function.\u003cbr/\u003e`labels` is a list of labels, in order, to pass to `format()` function.\u003cbr/\u003eLabel values will be normalized before being passed to `format()` so they will be\u003cbr/\u003eidentical to how they appear in `id`.\u003cbr/\u003eDefault is `{}` (`descriptors` output will be empty). | `any` | `{}` | no |\n| \u003ca name=\"input_dns_zone_id\"\u003e\u003c/a\u003e [dns\\_zone\\_id](#input\\_dns\\_zone\\_id) | Route53 DNS Zone ID to add hostname records for Elasticsearch domain and Kibana | `string` | `\"\"` | no |\n| \u003ca name=\"input_domain_endpoint_options_enforce_https\"\u003e\u003c/a\u003e [domain\\_endpoint\\_options\\_enforce\\_https](#input\\_domain\\_endpoint\\_options\\_enforce\\_https) | Whether or not to require HTTPS | `bool` | `true` | no |\n| \u003ca name=\"input_domain_endpoint_options_tls_security_policy\"\u003e\u003c/a\u003e [domain\\_endpoint\\_options\\_tls\\_security\\_policy](#input\\_domain\\_endpoint\\_options\\_tls\\_security\\_policy) | The name of the TLS security policy that needs to be applied to the HTTPS endpoint | `string` | `\"Policy-Min-TLS-1-0-2019-07\"` | no |\n| \u003ca name=\"input_domain_hostname_enabled\"\u003e\u003c/a\u003e [domain\\_hostname\\_enabled](#input\\_domain\\_hostname\\_enabled) | Explicit flag to enable creating a DNS hostname for ES. If `true`, then `var.dns_zone_id` is required. | `bool` | `false` | no |\n| \u003ca name=\"input_ebs_iops\"\u003e\u003c/a\u003e [ebs\\_iops](#input\\_ebs\\_iops) | The baseline input/output (I/O) performance of EBS volumes attached to data nodes. Applicable only for the Provisioned IOPS EBS volume type | `number` | `0` | no |\n| \u003ca name=\"input_ebs_throughput\"\u003e\u003c/a\u003e [ebs\\_throughput](#input\\_ebs\\_throughput) | Specifies the throughput (in MiB/s) of the EBS volumes attached to data nodes. Applicable only for the gp3 volume type. Valid values are between 125 and 1000. | `number` | `null` | no |\n| \u003ca name=\"input_ebs_volume_size\"\u003e\u003c/a\u003e [ebs\\_volume\\_size](#input\\_ebs\\_volume\\_size) | EBS volumes for data storage in GB | `number` | `0` | no |\n| \u003ca name=\"input_ebs_volume_type\"\u003e\u003c/a\u003e [ebs\\_volume\\_type](#input\\_ebs\\_volume\\_type) | Storage type of EBS volumes | `string` | `\"gp2\"` | no |\n| \u003ca name=\"input_elasticsearch_domain_name\"\u003e\u003c/a\u003e [elasticsearch\\_domain\\_name](#input\\_elasticsearch\\_domain\\_name) | The name of the Elasticsearch domain. Must be at least 3 and no more than 28 characters long. Valid characters are a-z (lowercase letters), 0-9, and - (hyphen). | `string` | `\"\"` | no |\n| \u003ca name=\"input_elasticsearch_subdomain_name\"\u003e\u003c/a\u003e [elasticsearch\\_subdomain\\_name](#input\\_elasticsearch\\_subdomain\\_name) | The name of the subdomain for Elasticsearch in the DNS zone (\\_e.g.\\_ `elasticsearch`, `ui`, `ui-es`, `search-ui`) | `string` | `\"\"` | no |\n| \u003ca name=\"input_elasticsearch_version\"\u003e\u003c/a\u003e [elasticsearch\\_version](#input\\_elasticsearch\\_version) | Version of Elasticsearch to deploy (\\_e.g.\\_ `7.4`, `7.1`, `6.8`, `6.7`, `6.5`, `6.4`, `6.3`, `6.2`, `6.0`, `5.6`, `5.5`, `5.3`, `5.1`, `2.3`, `1.5` | `string` | `\"7.4\"` | no |\n| \u003ca name=\"input_enabled\"\u003e\u003c/a\u003e [enabled](#input\\_enabled) | Set to false to prevent the module from creating any resources | `bool` | `null` | no |\n| \u003ca name=\"input_encrypt_at_rest_enabled\"\u003e\u003c/a\u003e [encrypt\\_at\\_rest\\_enabled](#input\\_encrypt\\_at\\_rest\\_enabled) | Whether to enable encryption at rest | `bool` | `true` | no |\n| \u003ca name=\"input_encrypt_at_rest_kms_key_id\"\u003e\u003c/a\u003e [encrypt\\_at\\_rest\\_kms\\_key\\_id](#input\\_encrypt\\_at\\_rest\\_kms\\_key\\_id) | The KMS key ID to encrypt the Elasticsearch domain with. If not specified, then it defaults to using the AWS/Elasticsearch service KMS key | `string` | `\"\"` | no |\n| \u003ca name=\"input_environment\"\u003e\u003c/a\u003e [environment](#input\\_environment) | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' | `string` | `null` | no |\n| \u003ca name=\"input_iam_actions\"\u003e\u003c/a\u003e [iam\\_actions](#input\\_iam\\_actions) | List of actions to allow for the user IAM roles, _e.g._ `es:ESHttpGet`, `es:ESHttpPut`, `es:ESHttpPost` | `list(string)` | `[]` | no |\n| \u003ca name=\"input_iam_authorizing_role_arns\"\u003e\u003c/a\u003e [iam\\_authorizing\\_role\\_arns](#input\\_iam\\_authorizing\\_role\\_arns) | List of IAM role ARNs to permit to assume the Elasticsearch user role | `list(string)` | `[]` | no |\n| \u003ca name=\"input_iam_role_arns\"\u003e\u003c/a\u003e [iam\\_role\\_arns](#input\\_iam\\_role\\_arns) | List of IAM role ARNs to permit access to the Elasticsearch domain | `list(string)` | `[]` | no |\n| \u003ca name=\"input_iam_role_max_session_duration\"\u003e\u003c/a\u003e [iam\\_role\\_max\\_session\\_duration](#input\\_iam\\_role\\_max\\_session\\_duration) | The maximum session duration (in seconds) for the user role. Can have a value from 1 hour to 12 hours | `number` | `3600` | no |\n| \u003ca name=\"input_iam_role_permissions_boundary\"\u003e\u003c/a\u003e [iam\\_role\\_permissions\\_boundary](#input\\_iam\\_role\\_permissions\\_boundary) | The ARN of the permissions boundary policy which will be attached to the Elasticsearch user role | `string` | `null` | no |\n| \u003ca name=\"input_id_length_limit\"\u003e\u003c/a\u003e [id\\_length\\_limit](#input\\_id\\_length\\_limit) | Limit `id` to this many characters (minimum 6).\u003cbr/\u003eSet to `0` for unlimited length.\u003cbr/\u003eSet to `null` for keep the existing setting, which defaults to `0`.\u003cbr/\u003eDoes not affect `id_full`. | `number` | `null` | no |\n| \u003ca name=\"input_ingress_port_range_end\"\u003e\u003c/a\u003e [ingress\\_port\\_range\\_end](#input\\_ingress\\_port\\_range\\_end) | End number for allowed port range. (e.g. `443`) | `number` | `65535` | no |\n| \u003ca name=\"input_ingress_port_range_start\"\u003e\u003c/a\u003e [ingress\\_port\\_range\\_start](#input\\_ingress\\_port\\_range\\_start) | Start number for allowed port range. (e.g. `443`) | `number` | `0` | no |\n| \u003ca name=\"input_instance_count\"\u003e\u003c/a\u003e [instance\\_count](#input\\_instance\\_count) | Number of data nodes in the cluster | `number` | `4` | no |\n| \u003ca name=\"input_instance_type\"\u003e\u003c/a\u003e [instance\\_type](#input\\_instance\\_type) | Elasticsearch instance type for data nodes in the cluster | `string` | `\"t2.small.elasticsearch\"` | no |\n| \u003ca name=\"input_kibana_hostname_enabled\"\u003e\u003c/a\u003e [kibana\\_hostname\\_enabled](#input\\_kibana\\_hostname\\_enabled) | Explicit flag to enable creating a DNS hostname for Kibana. If `true`, then `var.dns_zone_id` is required. | `bool` | `false` | no |\n| \u003ca name=\"input_kibana_subdomain_name\"\u003e\u003c/a\u003e [kibana\\_subdomain\\_name](#input\\_kibana\\_subdomain\\_name) | The name of the subdomain for Kibana in the DNS zone (\\_e.g.\\_ `kibana`, `ui`, `ui-es`, `search-ui`, `kibana.elasticsearch`) | `string` | `\"\"` | no |\n| \u003ca name=\"input_label_key_case\"\u003e\u003c/a\u003e [label\\_key\\_case](#input\\_label\\_key\\_case) | Controls the letter case of the `tags` keys (label names) for tags generated by this module.\u003cbr/\u003eDoes not affect keys of tags passed in via the `tags` input.\u003cbr/\u003ePossible values: `lower`, `title`, `upper`.\u003cbr/\u003eDefault value: `title`. | `string` | `null` | no |\n| \u003ca name=\"input_label_order\"\u003e\u003c/a\u003e [label\\_order](#input\\_label\\_order) | The order in which the labels (ID elements) appear in the `id`.\u003cbr/\u003eDefaults to [\"namespace\", \"environment\", \"stage\", \"name\", \"attributes\"].\u003cbr/\u003eYou can omit any of the 6 labels (\"tenant\" is the 6th), but at least one must be present. | `list(string)` | `null` | no |\n| \u003ca name=\"input_label_value_case\"\u003e\u003c/a\u003e [label\\_value\\_case](#input\\_label\\_value\\_case) | Controls the letter case of ID elements (labels) as included in `id`,\u003cbr/\u003eset as tag values, and output by this module individually.\u003cbr/\u003eDoes not affect values of tags passed in via the `tags` input.\u003cbr/\u003ePossible values: `lower`, `title`, `upper` and `none` (no transformation).\u003cbr/\u003eSet this to `title` and set `delimiter` to `\"\"` to yield Pascal Case IDs.\u003cbr/\u003eDefault value: `lower`. | `string` | `null` | no |\n| \u003ca name=\"input_labels_as_tags\"\u003e\u003c/a\u003e [labels\\_as\\_tags](#input\\_labels\\_as\\_tags) | Set of labels (ID elements) to include as tags in the `tags` output.\u003cbr/\u003eDefault is to include all labels.\u003cbr/\u003eTags with empty values will not be included in the `tags` output.\u003cbr/\u003eSet to `[]` to suppress all generated tags.\u003cbr/\u003e**Notes:**\u003cbr/\u003e  The value of the `name` tag, if included, will be the `id`, not the `name`.\u003cbr/\u003e  Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be\u003cbr/\u003e  changed in later chained modules. Attempts to change it will be silently ignored. | `set(string)` | \u003cpre\u003e[\u003cbr/\u003e  \"default\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_log_publishing_application_cloudwatch_log_group_arn\"\u003e\u003c/a\u003e [log\\_publishing\\_application\\_cloudwatch\\_log\\_group\\_arn](#input\\_log\\_publishing\\_application\\_cloudwatch\\_log\\_group\\_arn) | ARN of the CloudWatch log group to which log for ES\\_APPLICATION\\_LOGS needs to be published | `string` | `\"\"` | no |\n| \u003ca name=\"input_log_publishing_application_enabled\"\u003e\u003c/a\u003e [log\\_publishing\\_application\\_enabled](#input\\_log\\_publishing\\_application\\_enabled) | Specifies whether log publishing option for ES\\_APPLICATION\\_LOGS is enabled or not | `bool` | `false` | no |\n| \u003ca name=\"input_log_publishing_audit_cloudwatch_log_group_arn\"\u003e\u003c/a\u003e [log\\_publishing\\_audit\\_cloudwatch\\_log\\_group\\_arn](#input\\_log\\_publishing\\_audit\\_cloudwatch\\_log\\_group\\_arn) | ARN of the CloudWatch log group to which log for AUDIT\\_LOGS needs to be published | `string` | `\"\"` | no |\n| \u003ca name=\"input_log_publishing_audit_enabled\"\u003e\u003c/a\u003e [log\\_publishing\\_audit\\_enabled](#input\\_log\\_publishing\\_audit\\_enabled) | Specifies whether log publishing option for AUDIT\\_LOGS is enabled or not | `bool` | `false` | no |\n| \u003ca name=\"input_log_publishing_index_cloudwatch_log_group_arn\"\u003e\u003c/a\u003e [log\\_publishing\\_index\\_cloudwatch\\_log\\_group\\_arn](#input\\_log\\_publishing\\_index\\_cloudwatch\\_log\\_group\\_arn) | ARN of the CloudWatch log group to which log for INDEX\\_SLOW\\_LOGS needs to be published | `string` | `\"\"` | no |\n| \u003ca name=\"input_log_publishing_index_enabled\"\u003e\u003c/a\u003e [log\\_publishing\\_index\\_enabled](#input\\_log\\_publishing\\_index\\_enabled) | Specifies whether log publishing option for INDEX\\_SLOW\\_LOGS is enabled or not | `bool` | `false` | no |\n| \u003ca name=\"input_log_publishing_search_cloudwatch_log_group_arn\"\u003e\u003c/a\u003e [log\\_publishing\\_search\\_cloudwatch\\_log\\_group\\_arn](#input\\_log\\_publishing\\_search\\_cloudwatch\\_log\\_group\\_arn) | ARN of the CloudWatch log group to which log for SEARCH\\_SLOW\\_LOGS needs to be published | `string` | `\"\"` | no |\n| \u003ca name=\"input_log_publishing_search_enabled\"\u003e\u003c/a\u003e [log\\_publishing\\_search\\_enabled](#input\\_log\\_publishing\\_search\\_enabled) | Specifies whether log publishing option for SEARCH\\_SLOW\\_LOGS is enabled or not | `bool` | `false` | no |\n| \u003ca name=\"input_name\"\u003e\u003c/a\u003e [name](#input\\_name) | ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.\u003cbr/\u003eThis is the only ID element not also included as a `tag`.\u003cbr/\u003eThe \"name\" tag is set to the full `id` string. There is no tag with the value of the `name` input. | `string` | `null` | no |\n| \u003ca name=\"input_namespace\"\u003e\u003c/a\u003e [namespace](#input\\_namespace) | ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique | `string` | `null` | no |\n| \u003ca name=\"input_node_to_node_encryption_enabled\"\u003e\u003c/a\u003e [node\\_to\\_node\\_encryption\\_enabled](#input\\_node\\_to\\_node\\_encryption\\_enabled) | Whether to enable node-to-node encryption | `bool` | `false` | no |\n| \u003ca name=\"input_regex_replace_chars\"\u003e\u003c/a\u003e [regex\\_replace\\_chars](#input\\_regex\\_replace\\_chars) | Terraform regular expression (regex) string.\u003cbr/\u003eCharacters matching the regex will be removed from the ID elements.\u003cbr/\u003eIf not set, `\"/[^a-zA-Z0-9-]/\"` is used to remove all characters other than hyphens, letters and digits. | `string` | `null` | no |\n| \u003ca name=\"input_security_groups\"\u003e\u003c/a\u003e [security\\_groups](#input\\_security\\_groups) | List of security group IDs to be allowed to connect to the cluster or the security group IDs to apply to the cluster when the `create_security_group` variable is set to false. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_stage\"\u003e\u003c/a\u003e [stage](#input\\_stage) | ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release' | `string` | `null` | no |\n| \u003ca name=\"input_subnet_ids\"\u003e\u003c/a\u003e [subnet\\_ids](#input\\_subnet\\_ids) | VPC Subnet IDs | `list(string)` | `[]` | no |\n| \u003ca name=\"input_tags\"\u003e\u003c/a\u003e [tags](#input\\_tags) | Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).\u003cbr/\u003eNeither the tag keys nor the tag values will be modified by this module. | `map(string)` | `{}` | no |\n| \u003ca name=\"input_tenant\"\u003e\u003c/a\u003e [tenant](#input\\_tenant) | ID element \\_(Rarely used, not included by default)\\_. A customer identifier, indicating who this instance of a resource is for | `string` | `null` | no |\n| \u003ca name=\"input_vpc_enabled\"\u003e\u003c/a\u003e [vpc\\_enabled](#input\\_vpc\\_enabled) | Set to false if ES should be deployed outside of VPC. | `bool` | `true` | no |\n| \u003ca name=\"input_vpc_id\"\u003e\u003c/a\u003e [vpc\\_id](#input\\_vpc\\_id) | VPC ID | `string` | `null` | no |\n| \u003ca name=\"input_warm_count\"\u003e\u003c/a\u003e [warm\\_count](#input\\_warm\\_count) | Number of UltraWarm nodes | `number` | `2` | no |\n| \u003ca name=\"input_warm_enabled\"\u003e\u003c/a\u003e [warm\\_enabled](#input\\_warm\\_enabled) | Whether AWS UltraWarm is enabled | `bool` | `false` | no |\n| \u003ca name=\"input_warm_type\"\u003e\u003c/a\u003e [warm\\_type](#input\\_warm\\_type) | Type of UltraWarm nodes | `string` | `\"ultrawarm1.medium.elasticsearch\"` | no |\n| \u003ca name=\"input_zone_awareness_enabled\"\u003e\u003c/a\u003e [zone\\_awareness\\_enabled](#input\\_zone\\_awareness\\_enabled) | Enable zone awareness for Elasticsearch cluster | `bool` | `true` | no |\n\n## Outputs\n\n| Name | Description |\n|------|-------------|\n| \u003ca name=\"output_domain_arn\"\u003e\u003c/a\u003e [domain\\_arn](#output\\_domain\\_arn) | ARN of the Elasticsearch domain |\n| \u003ca name=\"output_domain_endpoint\"\u003e\u003c/a\u003e [domain\\_endpoint](#output\\_domain\\_endpoint) | Domain-specific endpoint used to submit index, search, and data upload requests |\n| \u003ca name=\"output_domain_hostname\"\u003e\u003c/a\u003e [domain\\_hostname](#output\\_domain\\_hostname) | Elasticsearch domain hostname to submit index, search, and data upload requests |\n| \u003ca name=\"output_domain_id\"\u003e\u003c/a\u003e [domain\\_id](#output\\_domain\\_id) | Unique identifier for the Elasticsearch domain |\n| \u003ca name=\"output_domain_name\"\u003e\u003c/a\u003e [domain\\_name](#output\\_domain\\_name) | Name of the Elasticsearch domain |\n| \u003ca name=\"output_elasticsearch_user_iam_role_arn\"\u003e\u003c/a\u003e [elasticsearch\\_user\\_iam\\_role\\_arn](#output\\_elasticsearch\\_user\\_iam\\_role\\_arn) | The ARN of the IAM role to allow access to Elasticsearch cluster |\n| \u003ca name=\"output_elasticsearch_user_iam_role_name\"\u003e\u003c/a\u003e [elasticsearch\\_user\\_iam\\_role\\_name](#output\\_elasticsearch\\_user\\_iam\\_role\\_name) | The name of the IAM role to allow access to Elasticsearch cluster |\n| \u003ca name=\"output_kibana_endpoint\"\u003e\u003c/a\u003e [kibana\\_endpoint](#output\\_kibana\\_endpoint) | Domain-specific endpoint for Kibana without https scheme |\n| \u003ca name=\"output_kibana_hostname\"\u003e\u003c/a\u003e [kibana\\_hostname](#output\\_kibana\\_hostname) | Kibana hostname |\n| \u003ca name=\"output_security_group_id\"\u003e\u003c/a\u003e [security\\_group\\_id](#output\\_security\\_group\\_id) | Security Group ID to control access to the Elasticsearch domain |\n\u003c!-- markdownlint-restore --\u003e\n\n\n\n\n## References\n\nFor additional context, refer to some of these links.\n\n- [What is Amazon Elasticsearch Service](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/what-is-amazon-elasticsearch-service.html) - Complete description of Amazon Elasticsearch Service\n- [Amazon Elasticsearch Service Access Control](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-ac.html) - Describes several ways of controlling access to Elasticsearch domains\n- [VPC Support for Amazon Elasticsearch Service Domains](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-vpc.html) - Describes Elasticsearch Service VPC Support and VPC architectures with and without zone awareness\n- [Creating and Configuring Amazon Elasticsearch Service Domains](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-createupdatedomains.html) - Provides a complete description on how to create and configure Amazon Elasticsearch Service (Amazon ES) domains\n- [Kibana and Logstash](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-kibana.html) - Describes some considerations for using Kibana and Logstash with Amazon Elasticsearch Service\n- [Amazon Cognito Authentication for Kibana](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-cognito-auth.html) - Amazon Elasticsearch Service uses Amazon Cognito to offer user name and password protection for Kibana\n- [Control Access to Amazon Elasticsearch Service Domain](https://aws.amazon.com/blogs/security/how-to-control-access-to-your-amazon-elasticsearch-service-domain/) - Describes how to Control Access to Amazon Elasticsearch Service Domain\n- [elasticsearch_domain](https://www.terraform.io/docs/providers/aws/r/elasticsearch_domain.html) - Terraform reference documentation for the `elasticsearch_domain` resource\n- [elasticsearch_domain_policy](https://www.terraform.io/docs/providers/aws/r/elasticsearch_domain_policy.html) - Terraform reference documentation for the `elasticsearch_domain_policy` resource\n\n\n\n\u003e [!TIP]\n\u003e #### Use Terraform Reference Architectures for AWS\n\u003e\n\u003e Use Cloud Posse's ready-to-go [terraform architecture blueprints](https://cloudposse.com/reference-architecture/) for AWS to get up and running quickly.\n\u003e\n\u003e ✅ We build it together with your team.\u003cbr/\u003e\n\u003e ✅ Your team owns everything.\u003cbr/\u003e\n\u003e ✅ 100% Open Source and backed by fanatical support.\u003cbr/\u003e\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e \u003cdetails\u003e\u003csummary\u003e📚 \u003cstrong\u003eLearn More\u003c/strong\u003e\u003c/summary\u003e\n\u003e\n\u003e \u003cbr/\u003e\n\u003e\n\u003e Cloud Posse is the leading [**DevOps Accelerator**](https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=commercial_support) for funded startups and enterprises.\n\u003e\n\u003e *Your team can operate like a pro today.*\n\u003e\n\u003e Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.\n\u003e #### Day-0:  Your Foundation for Success\n\u003e - **Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.\n\u003e - **Deployment Strategy.** Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.\n\u003e - **Site Reliability Engineering.** Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.\n\u003e - **Security Baseline.** Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.\n\u003e - **GitOps.** Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e\n\u003e #### Day-2: Your Operational Mastery\n\u003e - **Training.** Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.\n\u003e - **Support.** Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.\n\u003e - **Troubleshooting.** Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.\n\u003e - **Code Reviews.** Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.\n\u003e - **Bug Fixes.** Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.\n\u003e - **Migration Assistance.** Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.\n\u003e - **Customer Workshops.** Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e \u003c/details\u003e\n\n## ✨ Contributing\n\nThis project is under active development, and we encourage contributions from our community.\n\n\n\nMany thanks to our outstanding contributors:\n\n\u003ca href=\"https://github.com/cloudposse/terraform-aws-elasticsearch/graphs/contributors\"\u003e\n  \u003cimg src=\"https://contrib.rocks/image?repo=cloudposse/terraform-aws-elasticsearch\u0026max=24\" /\u003e\n\u003c/a\u003e\n\nFor 🐛 bug reports \u0026 feature requests, please use the [issue tracker](https://github.com/cloudposse/terraform-aws-elasticsearch/issues).\n\nIn general, PRs are welcome. We follow the typical \"fork-and-pull\" Git workflow.\n 1. Review our [Code of Conduct](https://github.com/cloudposse/terraform-aws-elasticsearch/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).\n 2. **Fork** the repo on GitHub\n 3. **Clone** the project to your own machine\n 4. **Commit** changes to your own branch\n 5. **Push** your work back up to your fork\n 6. Submit a **Pull Request** so that we can review your changes\n\n**NOTE:** Be sure to merge the latest changes from \"upstream\" before making a pull request!\n\n### 🌎 Slack Community\n\nJoin our [Open Source Community](https://cpco.io/slack?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=slack) on Slack. It's **FREE** for everyone! Our \"SweetOps\" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.\n\n### 📰 Newsletter\n\nSign up for [our newsletter](https://cpco.io/newsletter?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.\nDropped straight into your Inbox every week — and usually a 5-minute read.\n\n### 📆 Office Hours \u003ca href=\"https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=office_hours\"\u003e\u003cimg src=\"https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png\" align=\"right\" /\u003e\u003c/a\u003e\n\n[Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q\u0026A_ that you can’t find anywhere else.\nIt's **FREE** for everyone!\n## License\n\n\u003ca href=\"https://opensource.org/licenses/Apache-2.0\"\u003e\u003cimg src=\"https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=for-the-badge\" alt=\"License\"\u003e\u003c/a\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003ePreamble to the Apache License, Version 2.0\u003c/summary\u003e\n\u003cbr/\u003e\n\u003cbr/\u003e\n\nComplete license is available in the [`LICENSE`](LICENSE) file.\n\n```text\nLicensed to the Apache Software Foundation (ASF) under one\nor more contributor license agreements.  See the NOTICE file\ndistributed with this work for additional information\nregarding copyright ownership.  The ASF licenses this file\nto you under the Apache License, Version 2.0 (the\n\"License\"); you may not use this file except in compliance\nwith the License.  You may obtain a copy of the License at\n\n  https://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing,\nsoftware distributed under the License is distributed on an\n\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied.  See the License for the\nspecific language governing permissions and limitations\nunder the License.\n```\n\u003c/details\u003e\n\n## Trademarks\n\nAll other trademarks referenced herein are the property of their respective owners.\n\n\n---\nCopyright © 2017-2025 [Cloud Posse, LLC](https://cpco.io/copyright)\n\n\n\u003ca href=\"https://cloudposse.com/readme/footer/link?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-elasticsearch\u0026utm_content=readme_footer_link\"\u003e\u003cimg alt=\"README footer\" src=\"https://cloudposse.com/readme/footer/img\"/\u003e\u003c/a\u003e\n\n\u003cimg alt=\"Beacon\" width=\"0\" src=\"https://ga-beacon.cloudposse.com/UA-76589703-4/cloudposse/terraform-aws-elasticsearch?pixel\u0026cs=github\u0026cm=readme\u0026an=terraform-aws-elasticsearch\"/\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fterraform-aws-elasticsearch","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcloudposse%2Fterraform-aws-elasticsearch","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fterraform-aws-elasticsearch/lists"}