Skip to content

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Dec 29, 2025

Adds a warning admonition in the Prerequisites section to explicitly state that Redshift endpoints must be publicly accessible. Addresses connection failures caused by private-only endpoints accessible only within VPCs.

Trigger Events

Open this suggestion in the Promptless dashboard


Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.

If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)


Note

Docs update

  • In content/collections/destination-catalog/en/amazon-redshift.md Prerequisites, adds explicit note that Amplitude supports only public Redshift endpoints and private endpoints aren't supported.

Written by Cursor Bugbot for commit 800a11e. This will update automatically on new commits. Configure here.

@promptless promptless bot requested a review from a team as a code owner December 29, 2025 19:35
@vercel
Copy link

vercel bot commented Dec 29, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
amplitude-docs Ready Ready Preview Dec 29, 2025 8:36pm

@markzegarelli markzegarelli self-requested a review December 29, 2025 19:35
You need admin privileges in Amplitude, and a role that allows you to enable resources in Redshift.

{{partial:admonition type="warning" heading="Redshift endpoint must be publicly accessible"}}
Your Redshift endpoint must be publicly accessible for Amplitude to connect. Private endpoints accessible only within your VPC aren't supported.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Passive voice used in warning admonition (Bugbot Rules)

The phrase "aren't supported" uses passive voice, which violates Rule #1 (Active Voice - Critical Priority). The style guide requires 100% active voice and flags constructions like "is/are [verb]ed". Consider rephrasing to active voice, such as "Amplitude doesn't support private endpoints accessible only within your VPC."

Fix in Cursor Fix in Web

@promptless
Copy link
Contributor Author

promptless bot commented Dec 29, 2025

I've added new changes to address this Slack mention in commit 8d00eb9

@promptless
Copy link
Contributor Author

promptless bot commented Dec 29, 2025

I've added new changes to address this Slack mention in commit 800a11e

@promptless
Copy link
Contributor Author

promptless bot commented Dec 29, 2025

Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants