adopters: add case study links (#4742)#4755
Merged
CaitinChen merged 1 commit intopingcap:release-3.1from Jan 29, 2021
Merged
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
11 tasks
Contributor
Author
|
@CaitinChen you're already a collaborator in bot's repo. |
CaitinChen
approved these changes
Jan 29, 2021
CaitinChen
approved these changes
Jan 29, 2021
alastori
added a commit
to alastori/tidb-docs
that referenced
this pull request
May 1, 2026
Premium DM now supports AWS PrivateLink for source connectivity, sharing the Private Endpoint UI with Premium Changefeed (dataflow-service pingcap#3347, dbaas-ui pingcap#4755). The canonical Cloud DM doc had no Premium variant for the connection methods table or Step 2 wizard guidance, and the supported-sources block still asserted public-only access. Changes (all in migrate-from-mysql-using-data-migration.md): - Replace the stale "connect via the public endpoint" sentence with a pointer to the connection-methods section. - Add Premium variant of the connection methods table (Public for all providers; Private Link for AWS only). - Add Premium variant of the "Private link or private endpoint" section covering the AWS-side NLB and Endpoint Service setup plus the TiDB Cloud-side Private Endpoint creation under Networking > Private Endpoint for External Services. - Add Premium variants for Step 2 connectivity-method selection and the conditional follow-up (Hostname or IP address for Public, Private Endpoint dropdown with inline create-here link for Private Link). - Add Premium variant for the post-validate step (Public IP allowlist or AWS endpoint connection acceptance). Field labels verified end-to-end against the wizard on dev (cluster keep-720h-cslb, us-east-1, 2026-04-30).
This was referenced May 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cherry-pick #4742 to release-3.1
You can switch your code base to this Pull Request by using git-extras:
# In docs repo: git pr https://github.com/pingcap/docs/pull/4755After apply modifications, you can push your change to this PR via:
First-time contributors' checklist
What is changed, added or deleted? (Required)
add case study links for Shopee, Zhihu, and XiaomiWhich TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?