Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenSearch - Connections for Cross-Cluster Search #31881

Closed
arturobayo opened this issue Sep 28, 2022 · 3 comments
Closed

OpenSearch - Connections for Cross-Cluster Search #31881

arturobayo opened this issue Sep 28, 2022 · 3 comments
Labels
enhancement new new issue not yet triaged question

Comments

@arturobayo
Copy link

arturobayo commented Sep 28, 2022

Terraform Version

1.3.0 (latest)

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

  • AcceptInboundConnection
  • CreateOutboundConnection
  • DeleteInboundConnection
  • DescribeInboundConnections
  • DescribeOutboundConnections
  • RejectInboundConnection

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

  1. 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.

  2. 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

@arturobayo arturobayo added enhancement new new issue not yet triaged labels Sep 28, 2022
@jbardin
Copy link
Member

jbardin commented Sep 28, 2022

Hello,

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!

@jbardin jbardin closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2022
@arturobayo
Copy link
Author

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

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement new new issue not yet triaged question
Projects
None yet
Development

No branches or pull requests

2 participants