Amazon Elasticsearch Service
Overview
This service contains code to deploy an Amazon Elasticsearch Service cluster. See the Amazon Elasticsearch Service documentation and the Getting Started page for more information.
Features
- A fully-managed native Elasticsearch cluster in a VPC
- A fully functional Kibana UI
- VPC-based security
- Zone awareness, i.e., deployment of Elasticsearch nodes across Availability Zones
- Automatic nightly snapshots
- CloudWatch Alarms for alerting when CPU, memory, and disk metrics exceed certain thresholds
Learn
note
This repo is a part of the Gruntwork Service Catalog, a collection of reusable, battle-tested, production ready infrastructure code. If you’ve never used the Service Catalog before, make sure to read How to use the Gruntwork Service Catalog!
- About Amazon Elasticsearch Service
- Features of Amazon ES
- Developer Guide: Contains the main documentation on how to use Amazon ES and answers questions such as "What is Amazon Elasticsearch Service?"
- Streaming CloudWatch monitoring logs to Amazon Elasticsearch Service
Deploy
Non-production deployment (quick start for learning)
If you just want to try this repo out for experimenting and learning, check out the following resources:
examples/for-learning-and-testing folder: The
examples/for-learning-and-testingfolder contains standalone sample code optimized for learning, experimenting, and testing (but not direct production usage).AWS Free tier: Using Amazon ES on Amazon’s free tier is a great way to get started, but it has limited features and does not include encryption at rest, ultra warm data notes, or advanced security options such as fine-grained access control. The free tier does allow multiple availability zones, VPC-based access control, TLS-only requests, and node-to-node encryption.
Production deployment
If you want to deploy this repo in production, check out the following resources:
examples/for-production folder: The
examples/for-productionfolder contains sample code optimized for direct usage in production. This is code from the Gruntwork Reference Architecture, and it shows you how we build an end-to-end, integrated tech stack on top of the Gruntwork Service Catalog.
Reference
- Inputs
- Outputs
Required
domain_namestringThe name of the Elasticsearch cluster. It must be unique to your account and region, start with a lowercase letter, contain between 3 and 28 characters, and contain only lowercase letters a-z, the numbers 0-9, and the hyphen (-).
instance_countnumberThe number of instances to deploy in the Elasticsearch cluster. This must be an even number if zone_awareness_enabled is true.
instance_typestringThe instance type to use for Elasticsearch data nodes (e.g., t2.small.elasticsearch, or m4.large.elasticsearch). For supported instance types see https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-supported-instance-types.html.
volume_sizenumberThe size in GiB of the EBS volume for each node in the cluster (e.g. 10, or 512). For volume size limits see https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-limits.html.
volume_typestringThe type of EBS volumes to use in the cluster. Must be one of: standard, gp2, io1, sc1, or st1. For a comparison of EBS volume types, see https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ebs-volume-types.html.
Whether to deploy the Elasticsearch nodes across two Availability Zones instead of one. Note that if you enable this, the instance_count MUST be an even number.
Optional
advanced_optionsmap(any)Key-value string pairs to specify advanced configuration options. Note that the values for these configuration options must be strings (wrapped in quotes).
Any types represent complex values of variable type. For details, please consult `variables.tf` in the source repo.
{}Enable fine grain access control
falsealarm_sns_topic_arnslist(string)ARNs of the SNS topics associated with the CloudWatch alarms for the Elasticsearch cluster.
[]allow_connections_from_cidr_blocksset(string)The list of network CIDR blocks to allow network access to Aurora from. One of allow_connections_from_cidr_blocks or allow_connections_from_security_groups must be specified for the database to be reachable.
[]allow_connections_from_security_groupsset(string)The list of IDs or Security Groups to allow network access to Aurora from. All security groups must either be in the VPC specified by vpc_id, or a peered VPC with the VPC specified by vpc_id. One of allow_connections_from_cidr_blocks or allow_connections_from_security_groups must be specified for the database to be reachable.
[]Hour during which the service takes an automated daily snapshot of the indices in the domain. This setting has no effect on Elasticsearch 5.3 and later.
0availability_zone_countnumberNumber of Availability Zones for the domain to use with zone_awareness_enabled. Defaults to 2. Valid values: 2 or 3.
2Whether or not the Service Linked Role for Elasticsearch should be created within this module. Normally the service linked role is created automatically by AWS when creating the Elasticsearch domain in the web console, but API does not implement this logic. You can either have AWS automatically manage this by creating a domain manually in the console, or manage it in terraform using the landing zone modules or this variable.
falsecustom_endpointstringFully qualified domain for your custom endpoint.
nullACM certificate ARN for your custom endpoint.
nullWhether to enable custom endpoint for the Elasticsearch domain.
falsecustom_tagsmap(string)A map of custom tags to apply to the ElasticSearch Domain. The key is the tag name and the value is the tag value.
{}dedicated_master_countnumberThe number of dedicated master nodes to run. We recommend setting this to 3 for production deployments. Only used if dedicated_master_enabled is true.
nullWhether to deploy separate nodes specifically for performing cluster management tasks (e.g. tracking number of nodes, monitoring health, replicating changes). This increases the stability of large clusters and is required for clusters with more than 10 nodes.
falsededicated_master_typestringThe instance type for the dedicated master nodes. These nodes can use a different instance type than the rest of the cluster. Only used if dedicated_master_enabled is true.
nullebs_enabledboolSet to false to disable EBS volumes. This is useful for nodes that have optimized instance storage, like hosts running the i3 instance type.
trueelasticsearch_versionstringThe version of Elasticsearch to deploy.
"7.7"Set to true to enable several basic CloudWatch alarms around CPU usage, memory usage, and disk space usage. If set to true, make sure to specify SNS topics to send notifications to using alarms_sns_topic_arns.
trueFalse by default because encryption at rest is not included in the free tier. When true, the Elasticsearch domain storage will be encrypted at rest using the KMS key described with encryption_kms_key_id. We strongly recommend configuring a custom KMS key instead of using the shared service key for a better security posture when configuring encryption at rest.
trueWhether to enable node-to-node encryption.
trueencryption_kms_key_idstringThe ID of the KMS key to use to encrypt the Elasticsearch domain storage. Only used if enable_encryption_at_rest. When null, uses the aws/es service KMS key.
nulliam_principal_arnslist(string)The ARNS of the IAM users and roles to which to allow full access to the Elasticsearch cluster. Setting this to a restricted list is useful when using a public access cluster.
[ "*"
]Whether the internal user database is enabled. Enable this to use master accounts. Only used if advanced_security_options is set to true.
falseiopsnumberThe baseline input/output (I/O) performance of EBS volumes attached to data nodes. Must be between 1000 and 4000. Applicable only if volume_type is io1.
nullis_publicboolWhether the cluster is publicly accessible.
falsemaster_user_arnstringARN of the master user. Only used if advanced_security_options and internal_user_database_enabled are set to true.
nullmaster_user_namestringMaster account user name. Only used if advanced_security_options and internal_user_database_enabled are set to true.
nullmaster_user_passwordstringMaster account user password. Only used if advanced_security_options and internal_user_database_enabled are set to true. WARNING: this password will be stored in Terraform state.
nullsubnet_idslist(string) List of VPC Subnet IDs for the Elasticsearch domain endpoints to be created in. If zone_awareness_enabled is true, the first 2 or 3 provided subnet ids are used, depending on availability_zone_count. Otherwise only the first one is used.
[]tls_security_policystringThe name of the TLS security policy that needs to be applied to the HTTPS endpoint. Valid values are Policy-Min-TLS-1-0-2019-07 and Policy-Min-TLS-1-2-2019-07. Terraform performs drift detection if this is configured.
"Policy-Min-TLS-1-2-2019-07"update_timeoutstringHow long to wait for updates to the ES cluster before timing out and reporting an error.
"90m"vpc_idstringThe id of the VPC to deploy into. It must be in the same region as the Elasticsearch domain and its tenancy must be set to Default. If zone_awareness_enabled is false, the Elasticsearch cluster will have an endpoint in one subnet of the VPC; otherwise it will have endpoints in two subnets.
nullThe ARN of the Elasticsearch cluster created by this module.
The domain ID of the Elasticsearch cluster created by this module.
The name of the Elasticsearch domain.
The endpoint of the Elasticsearch cluster created by this module.
If the domain was created inside a VPC, the ID of the security group created by this module for securing the Elasticsearch cluster.
Domain-specific endpoint for Kibana without https scheme.