feat(pipes-targets): add Redshift #30674
Conversation
github-actions
bot
added
the
distinguished-contributor
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
msambol
force-pushed
the
pipes-targets-redshift
branch
from
9c29777 to
518ef9e
Compare
| masterUser: { masterUsername: 'admin' }, | ||
| nodeType: NodeType.DC2_LARGE, | ||
| clusterType: ClusterType.SINGLE_NODE, | ||
| publiclyAccessible: true, // not recommended, only for integration test |
There was a problem hiding this comment.
@redwheeler3 I assume the Redshift cluster needs to be publicly accessible in order for Pipes to hit it ?
There was a problem hiding this comment.
@redwheeler3, any insight on this one? I can get the pipe to execute (I see the BatchExecuteStatement API call in CloudTrail), but I don't see the query run in Redshift. I think my networking/security group look good but the Redshift cluster has to be publicly accessible for Pipes to hit it, right?
There was a problem hiding this comment.
Yes. For now, the Redshift cluster needs to be publicly accessible.
|
This PR has been in the CHANGES REQUESTED state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error. |
aws-cdk-automation
added
the
closed-for-staleness
|
Comments on closed issues and PRs are hard for our team to see. |
|
The pull request linter fails with the following errors: PRs must pass status checks before we can provide a meaningful review. If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing |
Add Redshift as a Pipes target