elastic / elastic/docs-content
[Website]: Cover limitation of Private Link for Managed Inputs on Serverless
- Dominant language
- No language data
- Stars
- 47
- Forks
- 261
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 116
Description
### Before you submit
- [x] This issue is about a documentation page, flow, or piece of content.
### Type of issue
Missing information
### What documentation page or section is affected
https://www.elastic.co/docs/reference/opentelemetry/managed-inputs/authentication-delivery-and-failure-handling
### What happened?
We correctly document ECH limitation of ip filtering & privatelink. We might add a "planned" tag if we're working on it?
For Serverless, the `ingest` endpoint / Managed Input supports privatelink for AWS and Azure - GCP is pending (as per https://www.elastic.co/docs/deploy-manage/security/private-connectivity)
FYI @perk / @jlind23 / @raultorrecilla
### Additional info
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the affected authentication, delivery, and failure-handling page and compare its Private Link coverage with the private connectivity page. Document that Serverless Managed Inputs support Private Link for AWS and Azure while GCP is pending, and clarify whether a planned tag is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100