-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
feat(redshift): adds elasticIp parameter to redshift cluster #21085
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daschaa it looks like there are some additional considerations when creating a public redshift cluster and using an elasticIP https://docs.aws.amazon.com/redshift/latest/mgmt/managing-clusters-vpc.html.
Can you update the README to have a section that discusses this?
Of course! Thanks for the feedback.
Is it ok to copy this to the readme? Imho it explains it very good and simple. :) |
yeah I think that is fine. Some of the other items I think it is important to include:
|
@corymhall I updated the Readme and added the section about the elastic ip. I hope everything is ok - it would be great if you could double check. In the topic of when to use elastic ip vs. cluster endpoint I'm not quite sure how to formulate it. As far as I understand it, the elastic ip should only be used when you need to have a static ip which you use to connect to the Redshift Cluster and the cluster endpoint is more dynamic, because it is a DNS address which is generated. Is it correct? And the last thing about changing the ip after the cluster has been completed I do not quite understand. Could you give me a hint where to look regarding this topic? Thanks in advance! ❤️ |
It's near the bottom of that page:
I would just take from this portion. I think the important thing to not is just that they are not the same thing. There might be some confusion if there is a public elasticIP and a public node ip address.
|
@corymhall Thank you very much for the hints! I added the sections you mentioned in your comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daschaa awesome! love the readme updates ❤️
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
@corymhall Are the tests flaky? Because I did not change anything I think.. |
@Mergifyio update |
✅ Branch has been successfully updated |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Fixes aws#19191. Adds the property `elasticIp` to the `ClusterProps`. ---- ### All Submissions: * [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Fixes #19191.
Adds the property
elasticIp
to theClusterProps
.All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integ
to deploy the infrastructure and generate the snapshot (i.e.yarn integ
without--dry-run
)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license