ReadonlynodeThe tree node.
ReadonlytableThe ARN of the provisioned Table Bucket.
ReadonlytableThe physical name applied to the Table Bucket.
Returns a string representation of this construct.
Applies one or more mixins to this construct.
Mixins are applied in order. The list of constructs is captured at the
start of the call, so constructs added by a mixin will not be visited.
Use multiple with() calls if subsequent mixins should apply to added
constructs.
The mixins to apply
This construct for chaining
StaticisChecks if x is a construct.
Use this method instead of instanceof to properly detect Construct
instances, even when the construct library is symlinked.
Explanation: in JavaScript, multiple copies of the constructs library on
disk are seen as independent, completely different libraries. As a
consequence, the class Construct in each copy of the constructs library
is seen as a different class, and an instance of one class will not test as
instanceof the other class. npm install will not create installations
like this, but users may manually symlink construct libraries together or
use a monorepo tool: in those cases, multiple copies of the constructs
library can be accidentally installed, and instanceof will behave
unpredictably. It is safest to avoid using instanceof, and using
this type-testing method instead.
Any object
true if x is an object created from a class which extends Construct.
L2 construct wrapping AWS::S3Tables::TableBucket with MDAA naming, KMS encryption enforcement, and data protection via RETAIN removal policy.
In-transit protection (deny-non-TLS) is baked in by default: this construct owns the single AWS::S3Tables::TableBucketPolicy allowed per table bucket and always attaches it (via MdaaTableBucketPolicy, which injects the deny-non-TLS statement) unless MdaaTableBucketProps.attachBucketPolicy is explicitly set to false. Callers append the deny-all baseline and least-privilege grant statements through MdaaTableBucketProps.additionalPolicyStatements. This keeps exactly one policy per bucket with TLS enforcement always present, rather than relying on a separate resource being wired up.