- 新しい順
- 投票が多い順
- コメントが多い順
Based on the available information, while AWS CloudFormation and CDK support for S3 Tables was announced in August 2025, there doesn't appear to be documented support specifically for configuring partitioning when creating Apache Iceberg tables through the aws_cdk.aws_s3tables_alpha module.
When creating Iceberg tables in S3 Tables, you typically need to specify partitioning using the PARTITIONED BY clause, as shown in your example. This allows you to define partition transforms and specify multiple columns for partitioning.
Since the CDK module doesn't appear to have explicit support for these partitioning configurations, you have a few options:
-
You could implement a custom CDK resource that uses AWS SDK calls or executes the necessary SQL statements to create the table with your desired partitioning configuration.
-
You could use the CDK to create the table bucket and namespace, and then use a separate mechanism (like a Lambda function triggered by CloudFormation custom resources) to execute the SQL statements needed to create the properly partitioned table.
Regarding schema evolution, Iceberg tables inherently support schema evolution as part of the Apache Iceberg specification. However, managing schema changes through CDK would likely require you to define the new schema in your CDK code and implement a deployment mechanism that applies these changes. Since the CDK module appears to be focused on resource creation rather than ongoing schema management, you might need to implement custom logic to handle schema evolution scenarios.
For the most accurate and up-to-date information, I'd recommend checking the latest CDK documentation or reaching out to AWS Support, as the capabilities of the aws_cdk.aws_s3tables_alpha module may have evolved since the information provided.
Sources
What's New at AWS - Cloud Innovation & News
Create Iceberg tables - Amazon Athena
Register S3 table bucket catalogs and query Tables from Athena - Amazon Athena
