ReadonlyenabledWhen true, creates the s3tablescatalog Glue federated catalog so S3 Tables
are queryable from AWS analytics services without a manual console step.
Region/partition note: AWS offers the IAM-based-access-control form of this integration only in a subset of Regions (elsewhere it additionally requires Lake Formation), and it is not available in every partition; in an unsupported Region/partition the custom resource may report success while the integration is functionally incomplete. See the AWS S3 Tables documentation for the current list.
Use cases: Automated S3 Tables analytics enablement; Athena/Redshift/EMR access to Iceberg tables
AWS: Glue CreateCatalog (federated aws:s3tables catalog), Lake Formation location registration
Validation: Required; boolean
Optional ReadonlyremoveWhen true, the s3tablescatalog catalog is deleted when the stack is deleted.
Defaults to false so that deleting this stack does NOT break queries for other
S3 Tables deployments sharing this account/Region integration. Only enable if
this stack owns the integration and you want it torn down on delete.
Use cases: Full lifecycle ownership of the shared integration; ephemeral/test environments
AWS: Glue DeleteCatalog on stack delete
Validation: Optional; boolean
Automates the "Enable integration" action for Amazon S3 Tables so table buckets in this account/Region are queryable from Athena, Redshift, EMR, and QuickSight without a manual console step. When enabled, MDAA creates the
s3tablescatalogfederated catalog in AWS Glue; Glue in turn registers the table bucket location with Lake Formation using IAM (IAM_ALLOWED_PRINCIPALS) access controls. The integration is a single, shared resource per account/Region, which is why it lives in this account-level module.