Thank you for bringing this to our attention. We have identified the issue and are working on a fix.
Is fix maybe released for this issue in a meantime?
There is a limit in how long it is possible to defer an cluster update. I am afraid that we will be forced to update Redshift in couple of days despite this bug is not yet resolved.
Yes, this issue is fixed in all recent builds.
Please let me know if you have any further issues after your maintenance window.
Solved with one of the Redshift updates.
Is it possible to update the user-defined authorizer context (i.e., event.requestContext.authorizer.context) after the initial authorizer lambda has already run?asked 9 months ago
Trying to track redshift Assert errorasked 4 months ago
Error 500310 context: num_tuples != 0asked 9 months ago
Assert Error in redshiftAccepted Answerasked 5 years ago
SQS Message retrival after message is deletedasked 2 months ago
wrong IP address is being returned - anyone else having this issue?asked 3 years ago
Appium chromedriver error: "Process didn't end after 10000ms" after switching to webview contextAccepted Answerasked 8 months ago
User is not able to see data in the QuickSight table/visual even after getting the accessasked 2 months ago
After Upgrade to 1.0.6630 view is failing with Assert errorasked 4 years ago
What is the VPC subnet route priority when two targets have the same default 0.0.0.0/0 route as the destination?Accepted Answerasked 2 years ago