https://github.com/math280h/terraform-elastic-cloud-private-link-aws
Terraform module for Elastic Cloud deployments using AWS PrivateLink
https://github.com/math280h/terraform-elastic-cloud-private-link-aws
Last synced: 5 months ago
JSON representation
Terraform module for Elastic Cloud deployments using AWS PrivateLink
- Host: GitHub
- URL: https://github.com/math280h/terraform-elastic-cloud-private-link-aws
- Owner: math280h
- License: mit
- Created: 2022-04-11T03:51:42.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-04-19T00:33:17.000Z (about 4 years ago)
- Last Synced: 2025-10-05T19:42:44.626Z (9 months ago)
- Language: HCL
- Homepage: https://registry.terraform.io/modules/math280h/cloud-private-link-aws/elastic/latest
- Size: 8.79 KB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Elastic Cloud AWS PrivateLink module
This module is an easy-to-use module for creating an Elastic Cloud deployment that connects to an existing AWS VPC via PrivateLink.
## Usage
This example will deploy a small elasticsearch cluster on us-east-1 that can be reached via PrivateLink from the VPC provided
given that the ingress_cidr and subnet_ids provided are correct.
For more information see: https://registry.terraform.io/modules/math280h/cloud-private-link-aws/elastic/latest
````terraform
provider "ec" {
apikey = var.elastic_cloud_api_key
}
data "ec_stack" "latest" {
version_regex = "latest"
region = "us-east-1"
}
module "elastic_cloud" {
source = "math280h/cloud-private-link-aws/elastic"
version = "0.0.1"
vpc_id = "some-vpc-id"
ingress_cidr = ["192.168.0.0/32"]
subnet_ids = ["", ""]
deployment_name = "my-elastic-cloud-deployment"
deployment_version = data.ec_stack.latest.version
}
````
Once deployed, the elastic deployment is reachable via the following link (On 443): `https://.es.vpce..aws.elastic-cloud.com`
### AWS VPC Configuration
For this to work, you must have the DNS Hostnames and DNS Resolution enabled on your VPC. (https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-updating)
## Resources
https://www.elastic.co/guide/en/cloud/current/ec-traffic-filtering-vpc.html
https://aws.amazon.com/premiumsupport/knowledge-center/route-53-fix-dns-resolution-issues/