Private Link Support for Cloud Connect Services - AutoOps and Elastic Inference Service (EIS)
- Dominant language
- No language data
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
**What the feature is and who it's for**
Private network connectivity (e.g. AWS PrivateLink, Azure Private Link, GCP Private Service Connect) for the AutoOps and Elastic Inference Service (EIS) [Cloud Connect](https://www.elastic.co/docs/deploy-manage/cloud-connect) services, for customers whose network policies prohibit Internet egress and public DNS resolution.
**Value proposition**
For customers with network policies that restrict outbound Internet access or public DNS, private connectivity lets them reach Elastic's SaaS-based AutoOps and EIS Cloud Connect endpoints within their existing constraints.
**Outcome**
- Customers can connect to AutoOps Cloud Connect over private networks.
- Customers can connect to EIS Cloud Connect over private networks.
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation files, tests, or entry points are identified in this roadmap issue. Start by reviewing the Cloud Connect documentation and the requirements for AWS PrivateLink, Azure Private Link, and GCP Private Service Connect. Done means AutoOps and EIS Cloud Connect endpoints are reachable through private connectivity without Internet egress or public DNS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100