You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Amazon ElasticSearch/OpenSearch domains (clusters) may connect to other ElasticSearch/OpenSearch domains via "Connections", that are available on AWS API:
This allows cross-cluster search use cases, for example creating hub-and-spoke search architectures with search clusters distributed across the globe in multiple locations.
Attempted Solutions
Use the local-exec provisioner to run a custom script after creating the Domain resource that uses the AWS CLI/API under the hood to create the Connections.
Leverage the AWS CloudFormation Stack resource to deploy a custom CloudFormation resource that creates the Connections for the domain.
Proposal
Proposal is to add two new resources to OpenSearch: opensearch_connection and opensearch_connection_accepter
This appears to be a question or an issue with a provider, not with Terraform itself. You can check existing issues and file a new one in the provider's project repository, linked from the their registry page. If you have questions about Terraform or the provider, it's better to use the community forum where there are more people ready to help. The GitHub issues here are monitored only by a few core maintainers.
thanks, just for tracking/reference: there's an issue and a PR already available for this on the Terraform AWS Provider project: hashicorp/terraform-provider-aws#13609
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Terraform Version
Use Cases
Amazon ElasticSearch/OpenSearch domains (clusters) may connect to other ElasticSearch/OpenSearch domains via "Connections", that are available on AWS API:
https://docs.aws.amazon.com/opensearch-service/latest/developerguide/configuration-api.html
This allows cross-cluster search use cases, for example creating hub-and-spoke search architectures with search clusters distributed across the globe in multiple locations.
Attempted Solutions
Use the local-exec provisioner to run a custom script after creating the Domain resource that uses the AWS CLI/API under the hood to create the Connections.
Leverage the AWS CloudFormation Stack resource to deploy a custom CloudFormation resource that creates the Connections for the domain.
Proposal
Proposal is to add two new resources to OpenSearch: opensearch_connection and opensearch_connection_accepter
Similar to how Resource Access Manager resource shares work (ram_resource_share and ram_resource_share_accepter)
References
No response
The text was updated successfully, but these errors were encountered: