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

cloud: update the intro sentence of creating AWS endpoints #20273

Merged
merged 1 commit into from
Feb 13, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions tidb-cloud/set-up-private-endpoint-connections.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ If you see the `TiDB Private Link Service is ready` message, the corresponding e
aws ec2 create-vpc-endpoint --vpc-id ${your_vpc_id} --region ${your_region} --service-name ${your_endpoint_service_name} --vpc-endpoint-type Interface --subnet-ids ${your_application_subnet_ids}
```

Then, you can create an AWS interface endpoint either using the [AWS Management Console](https://aws.amazon.com/console/) or using the AWS CLI.
Then, you can create an AWS interface endpoint either using the AWS CLI or using the [AWS Management Console](https://aws.amazon.com/console/).

<SimpleTab>
<div label="Use AWS CLI">
Expand Down Expand Up @@ -141,7 +141,7 @@ To use the AWS Management Console to create a VPC interface endpoint, perform th

### Step 4. Enable private DNS

Enable private DNS in AWS. You can either use the AWS Management Console or the AWS CLI.
Enable private DNS in AWS. You can either use the AWS CLI or the AWS Management Console.

<SimpleTab>
<div label="Use AWS CLI">
Expand Down