AWS PrivateLink Private Beta [DOC-876] #6708
Merged
Conversation
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
forstisabella
requested review from
a team and
cmastr
and removed request for
a team
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
AnnieZhao17
reviewed
Jun 14, 2024
| - ra3.4xlarge | ||
| - ra3.xlplus | ||
| - **You've enabled cluster relocation**: Cluster relocation migrates your cluster behind a proxy and keeps the cluster endpoint unchanged, even if your cluster needs to be migrated to a new Availability Zone. A consistent cluster endpoint makes it possible for Segment's Edge account and VPC to remain connected to your cluster. To enable cluster relocation, follow the instructions in the AWS [Relocating your cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html){:target="_blank”} documentation. | ||
| - **Your warehouse is using port range 5431-5455 and 8191-8215**: Clusters with cluster relocation enabled [might encounter an error if updated to include a port outside of this range](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html#:~:text=You%20can%20change%20to%20another%20port%20from%20the%20port%20range%20of%205431%2D5455%20or%208191%2D8215.%20(Don%27t%20change%20to%20a%20port%20outside%20the%20ranges.%20It%20results%20in%20an%20error.)){:target="_blank”}. |
There was a problem hiding this comment.
Sorry, I think we gave you the wrong info on the privatelink slides (assuming that's where you got this from). It's actually the Redshift cluster that needs to use a port within the ranges 5431-5455 or 8191-8215. Naturally, the warehouse needs to point to the same port as the cluster, but that's for later rather than a prerequisite.
There was a problem hiding this comment.
@forstisabella It's the cluster that needs to be in the port range, not warehouse! Looks like you made a suggestion comment earlier which looked perfect, but it wasn't applied
forstisabella
commented
Jun 17, 2024
AnnieZhao17
reviewed
Jun 17, 2024
| 2. Reach out to your Customer Success Manager (CSM) for more details about Segment's AWS principal. | ||
| 3. Add the Segment AWS principal as an “Allowed Principal” to consume the Network Load Balancer VPC endpoint service you created in step 1. | ||
| 4. Reach out to your CSM and provide them with the Service name for the service that you created above. Segment's engineering team provisions a VPC endpoint for the service in the Segment Edge VPC. | ||
| 5. After creating the VPC, Segment provides you with private DNS so you can update the **Host** in your Segment app settings or create a new Redshift integration. <br> The following RDS Postgres integrations support PrivateLink: |
There was a problem hiding this comment.
You wrote new Redshift integration, but this is the Postgres section!
There was a problem hiding this comment.
good catch!! thank you
| - ra3.4xlarge | ||
| - ra3.xlplus | ||
| - **You've enabled cluster relocation**: Cluster relocation migrates your cluster behind a proxy and keeps the cluster endpoint unchanged, even if your cluster needs to be migrated to a new Availability Zone. A consistent cluster endpoint makes it possible for Segment's Edge account and VPC to remain connected to your cluster. To enable cluster relocation, follow the instructions in the AWS [Relocating your cluster](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html){:target="_blank”} documentation. | ||
| - **Your warehouse is using port range 5431-5455 and 8191-8215**: Clusters with cluster relocation enabled [might encounter an error if updated to include a port outside of this range](https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-recovery.html#:~:text=You%20can%20change%20to%20another%20port%20from%20the%20port%20range%20of%205431%2D5455%20or%208191%2D8215.%20(Don%27t%20change%20to%20a%20port%20outside%20the%20ranges.%20It%20results%20in%20an%20error.)){:target="_blank”}. |
There was a problem hiding this comment.
@forstisabella It's the cluster that needs to be in the port range, not warehouse! Looks like you made a suggestion comment earlier which looked perfect, but it wasn't applied
forstisabella
commented
Jun 17, 2024
forstisabella
commented
Jun 17, 2024
Co-authored-by: Annie Zhao <anniezhao107@gmail.com>
AnnieZhao17
approved these changes
Jun 17, 2024
forstisabella
requested review from
pwseg
and removed request for
cmastr and
a team
pwseg
approved these changes
Jun 18, 2024
Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com>
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Merged
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.
Proposed changes
Added a doc for the AWS PrivateLink private beta. Will readjust IA as this goes public, but for now, it's a giant hidden page.
Merge timing
After approval from eng!
Related issues (optional)