Registry /
aws / aws-cdk-aws-redshift-alpha
Install & Compatibility
Where this runs
tested against v2.259.0a0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.910 runs
installs and imports cleanly · install 0.0s · import 0.000s · 359.7MB
glibcpy 3.10–3.910 runs
installs and imports cleanly · install 17.4s · import 0.000s · 360MB
397MB installed
● package 397MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
Cluster
✓ from aws_cdk import aws_redshift_alpha as redshift_alpha
# ... then use redshift_alpha.Cluster
✗ from aws_cdk.aws_redshift import Cluster
Alpha modules live under `aws_cdk.aws_MODULENAME_alpha`. There is no direct `aws_cdk.aws_redshift` L2 construct in the main library yet, only L1 (CfnCluster).
Login
✓ from aws_cdk import aws_redshift_alpha as redshift_alpha
# ... then use redshift_alpha.Login
✗ from aws_cdk.aws_redshift_alpha import Login as RedshiftLogin
While directly importing `Login` is technically possible, the idiomatic CDK alpha import pattern is to alias the entire `aws_redshift_alpha` module.
This quickstart defines a basic AWS CDK stack that provisions an AWS Redshift cluster within a new VPC. It uses single-node, DC2.LARGE instance types for a low-cost, quick-to-provision example. After saving this code to a file (e.g., `app.py`), you can run `python app.py` to synthesize the CloudFormation template, and then `cdk deploy` to provision the resources in your AWS account.
from aws_cdk import (
App, Stack,
aws_ec2 as ec2,
aws_redshift_alpha as redshift_alpha,
)
from constructs import Construct
class RedshiftAlphaQuickstartStack(Stack):
def __init__(self, scope: Construct, construct_id: str, **kwargs) -> None:
super().__init__(scope, construct_id, **kwargs)
# Create a VPC for the Redshift cluster
vpc = ec2.Vpc(self, "RedshiftQuickstartVPC", max_azs=1)
# Create an AWS Redshift Cluster using the alpha construct
cluster = redshift_alpha.Cluster(self, "MyRedshiftQuickstartCluster",
vpc=vpc,
cluster_type=redshift_alpha.ClusterType.SINGLE_NODE, # Use SINGLE_NODE for a quicker, cheaper example
node_type=redshift_alpha.NodeType.DC2_LARGE, # Use a smaller node type for example
master_user=redshift_alpha.Login("admin"),
db_name="quickstartdb",
publicly_accessible=False
)
# Instantiate the CDK App and synthesize the stack
app = App()
RedshiftAlphaQuickstartStack(app, "RedshiftAlphaQuickstartStack")
app.synth()
print("CDK Redshift Alpha quickstart stack synthesized successfully.")
# To deploy this stack: cdk deploy RedshiftAlphaQuickstartStack
Debug
Known issues
breakingAs an 'alpha' module, `aws-cdk-aws-redshift-alpha` APIs are subject to change without notice, even in minor CDK releases. Avoid using it for production workloads requiring stable APIs.fixBe prepared for frequent updates and refactoring. For production, consider using `CfnCluster` (L1 construct) from `aws-cdk-lib.aws_redshift` for stability, or wait for a stable L2 construct.
affects: All alpha versions (2.x.x.a0)
gotchaRedshift cluster creation and deletion can take a significant amount of time (15-30+ minutes). Be mindful of this during development and testing cycles.fixPlan your deployment and deletion windows accordingly. For rapid iteration, consider simpler, less resource-intensive services or use `SINGLE_NODE` clusters.
affects: All versions
gotchaRedshift clusters can incur significant costs, especially with multi-node and larger instance types. Ensure you understand the pricing model and remember to delete clusters when no longer needed.fixAlways use `cdk destroy` to tear down resources after testing. Monitor your AWS billing. For quick tests, use `SINGLE_NODE` and `DC2_LARGE` node types.
affects: All versions
gotchaCorrect VPC, subnet group, and security group configurations are critical for Redshift. Misconfigurations often lead to cluster creation failures or connectivity issues.fixEnsure your VPC has sufficient subnets in multiple AZs. Verify security group rules allow ingress from intended sources (e.g., your IP, EC2 instances). Ensure your cluster subnet group spans private subnets if `publicly_accessible` is false.
affects: All versions
Upgrade
Version history
2.259.0a0latest on PyPI · released Jun 12, 2026
Audit
Dependencies
aws-cdk-librequiredCore AWS CDK library, required for all CDK applications.
constructsrequiredPeer dependency of aws-cdk-lib, often installed implicitly.