Multiple Redshift Serverless Workgroups Stuck in CREATING State for 8+ Hours

While there are no known widespread issues with Redshift Serverless workgroup creation getting stuck, the situation you're experiencing is certainly unusual and concerning. Here are some insights and recommendations based on the information provided:

1. Stuck workgroup creation: This is not a common occurrence, but it can happen due to various reasons such as network configuration issues, resource constraints, or temporary service disruptions.

2. Force clean-up: Unfortunately, there isn't a straightforward CLI command to force clean-up of stuck workgroups. Amazon Redshift Serverless manages the infrastructure, which limits direct intervention options.

3. Recommended approach:

   a. Contact AWS Support: Given the extended duration of the issue and the lack of visible errors, it's advisable to open a support ticket with AWS. They can investigate backend issues that might not be visible to you.

   b. Review VPC and subnet configuration: Ensure that your VPC and subnets meet all requirements for Redshift Serverless. This includes having at least three subnets across three Availability Zones.

   c. Check IAM permissions: Verify that the IAM role associated with your Redshift workgroup has the necessary permissions, including full access to Redshift Serverless resources.

   d. Attempt creation in a different VPC: If possible, try creating a new workgroup in a different VPC to isolate whether the issue is specific to your current VPC configuration.

   e. Monitor CloudWatch Logs: Continue monitoring CloudWatch logs for any new error messages or indications of the root cause.

   f. Consider using SQL commands: If you have access to the Redshift query editor, you might try creating the database using SQL commands instead of the UI. This could potentially bypass any UI-related issues.

If the issue persists after trying these steps, waiting for AWS Support's intervention might be necessary. They have access to more detailed logs and can perform actions that are not available to customers.

Remember that Redshift Serverless is designed to handle most infrastructure management automatically, which is why there are limited options for manual intervention in such scenarios.

Sources
Redshift Serverless - unable to create a database - ERROR: permission denied to create database | AWS re:Post
Unable to Create Redshift Serverless due to Workgroup in Preview State & requires 3 avail zone subnets | AWS re:Post