-
Notifications
You must be signed in to change notification settings - Fork 4k
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
aws_redshiftserverless.CfnWorkgroup: creation of Redshift-managed VPC endpoints not working #26585
Comments
We are simply generating the CloudFormation template here directly as you've defined it. Be sure to check if the template that's deploying is synthesizing correctly. Please share the template synthesized if you're not sure If it is synthing correctly, and you're finding issues after deployment with a Cfn resource, you'll want to report that to the Cloudformation coverage roadmap repository https://github.com/aws-cloudformation/cloudformation-coverage-roadmap |
If this snippet is exactly what you used then you'll need to actually specify the properties in the construct constructor, or use escape hatches on the construct after the fact |
I'm working alongside @davyto and I'm experiencing the same issue. The synthetized Cloudformation code for the above snippet is the following:
The problem is that in the generated Cloudformation resource there is no Endpoint property being created |
Yeah, you aren't specifying this property with the snippet you gave
|
|
@peterwoodworth the The cdk documentation also does not show it https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_redshiftserverless/CfnWorkgroup.html |
I have exactly the same problem with [davyto], can we reopen this issue? @peterwoodworth |
Describe the bug
Hi, we are trying to create a Redshift-managed VPC endpoints in our Redshift Serverless workgroup, but this does not seem to be supported with CDK. There is no option in CfnWorkgroup to create one, while the VpcEndpointProperty and WorkgroupProperty are ignored at deploy.
Expected Behavior
The vpc endpoint creation should be triggered by VpcEndpointProperty, or something that calls this API https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_CreateEndpointAccess.html
Current Behavior
The creation of the endpoint gets ignored by cdk deploy.
Reproduction Steps
Possible Solution
The construct should use this api https://docs.aws.amazon.com/redshift-serverless/latest/APIReference/API_CreateEndpointAccess.html
Additional Information/Context
No response
CDK CLI Version
2.87.0
Framework Version
No response
Node.js Version
16.20
OS
mac and linux
Language
Python
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: