Kong / Kong/developer.konghq.com
Fix: decK AWS PrivateLink note about global domain
Open
Nobody has claimed this yet.
feedback
internal
onboarding
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 121
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 313
Description
Definition of done
- Update the section of the docs here to mention that they need to configure the global DNS entry https://developer.konghq.com/deck/gateway/konnect-configuration/#making-deck-work-with-aws-privatelink
- Also make a FAQ on that same decK page with the contents of the error message and how to resolve it from the linked Slack thread
Information
Slack: https://kongstrong.slack.com/archives/CDSTDSG9J/p1769074428580779
Size
S
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the decK Konnect configuration page and its AWS PrivateLink regional service-name reference. Read the linked Slack thread for the exact error message and resolution, then update the referenced section and add the FAQ; done means both documentation changes clearly explain the required global DNS entry and fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100