public static interface CreateLedgerRequest.Builder extends QldbRequest.Builder, SdkPojo, CopyableBuilder<CreateLedgerRequest.Builder,CreateLedgerRequest>
| Modifier and Type | Method and Description |
|---|---|
CreateLedgerRequest.Builder |
deletionProtection(Boolean deletionProtection)
The flag that prevents a ledger from being deleted by any user.
|
CreateLedgerRequest.Builder |
name(String name)
The name of the ledger that you want to create.
|
CreateLedgerRequest.Builder |
overrideConfiguration(AwsRequestOverrideConfiguration overrideConfiguration) |
CreateLedgerRequest.Builder |
overrideConfiguration(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer) |
CreateLedgerRequest.Builder |
permissionsMode(PermissionsMode permissionsMode)
The permissions mode to assign to the ledger that you want to create.
|
CreateLedgerRequest.Builder |
permissionsMode(String permissionsMode)
The permissions mode to assign to the ledger that you want to create.
|
CreateLedgerRequest.Builder |
tags(Map<String,String> tags)
The key-value pairs to add as tags to the ledger that you want to create.
|
buildoverrideConfigurationequalsBySdkFields, sdkFieldscopyapplyMutation, buildCreateLedgerRequest.Builder name(String name)
The name of the ledger that you want to create. The name must be unique among all of your ledgers in the current AWS Region.
Naming constraints for ledger names are defined in Quotas in Amazon QLDB in the Amazon QLDB Developer Guide.
name - The name of the ledger that you want to create. The name must be unique among all of your ledgers in
the current AWS Region.
Naming constraints for ledger names are defined in Quotas in Amazon QLDB in the Amazon QLDB Developer Guide.
CreateLedgerRequest.Builder tags(Map<String,String> tags)
The key-value pairs to add as tags to the ledger that you want to create. Tag keys are case sensitive. Tag values are case sensitive and can be null.
tags - The key-value pairs to add as tags to the ledger that you want to create. Tag keys are case sensitive.
Tag values are case sensitive and can be null.CreateLedgerRequest.Builder permissionsMode(String permissionsMode)
The permissions mode to assign to the ledger that you want to create. This parameter can have one of the following values:
ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for
ledgers.
This mode allows users who have SendCommand permissions for this ledger to run all PartiQL
commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode disregards any
table-level or command-level IAM permissions policies that you create for the ledger.
STANDARD: (Recommended) A permissions mode that enables access control with finer
granularity for ledgers, tables, and PartiQL commands.
By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To
allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and
PartiQL actions, in addition to SendCommand API permissions for the ledger.
We strongly recommend using the STANDARD permissions mode to maximize the security of your
ledger data.
permissionsMode - The permissions mode to assign to the ledger that you want to create. This parameter can have one of
the following values:
ALLOW_ALL: A legacy permissions mode that enables access control with API-level
granularity for ledgers.
This mode allows users who have SendCommand permissions for this ledger to run all
PartiQL commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode
disregards any table-level or command-level IAM permissions policies that you create for the ledger.
STANDARD: (Recommended) A permissions mode that enables access control with finer
granularity for ledgers, tables, and PartiQL commands.
By default, this mode denies all user requests to run any PartiQL commands on any tables in this
ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table
resources and PartiQL actions, in addition to SendCommand API permissions for the ledger.
We strongly recommend using the STANDARD permissions mode to maximize the security of
your ledger data.
PermissionsMode,
PermissionsModeCreateLedgerRequest.Builder permissionsMode(PermissionsMode permissionsMode)
The permissions mode to assign to the ledger that you want to create. This parameter can have one of the following values:
ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for
ledgers.
This mode allows users who have SendCommand permissions for this ledger to run all PartiQL
commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode disregards any
table-level or command-level IAM permissions policies that you create for the ledger.
STANDARD: (Recommended) A permissions mode that enables access control with finer
granularity for ledgers, tables, and PartiQL commands.
By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To
allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and
PartiQL actions, in addition to SendCommand API permissions for the ledger.
We strongly recommend using the STANDARD permissions mode to maximize the security of your
ledger data.
permissionsMode - The permissions mode to assign to the ledger that you want to create. This parameter can have one of
the following values:
ALLOW_ALL: A legacy permissions mode that enables access control with API-level
granularity for ledgers.
This mode allows users who have SendCommand permissions for this ledger to run all
PartiQL commands (hence, ALLOW_ALL) on any tables in the specified ledger. This mode
disregards any table-level or command-level IAM permissions policies that you create for the ledger.
STANDARD: (Recommended) A permissions mode that enables access control with finer
granularity for ledgers, tables, and PartiQL commands.
By default, this mode denies all user requests to run any PartiQL commands on any tables in this
ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table
resources and PartiQL actions, in addition to SendCommand API permissions for the ledger.
We strongly recommend using the STANDARD permissions mode to maximize the security of
your ledger data.
PermissionsMode,
PermissionsModeCreateLedgerRequest.Builder deletionProtection(Boolean deletionProtection)
The flag that prevents a ledger from being deleted by any user. If not provided on ledger creation, this
feature is enabled (true) by default.
If deletion protection is enabled, you must first disable it before you can delete the ledger using the QLDB
API or the AWS Command Line Interface (AWS CLI). You can disable it by calling the UpdateLedger
operation to set the flag to false. The QLDB console disables deletion protection for you when
you use it to delete a ledger.
deletionProtection - The flag that prevents a ledger from being deleted by any user. If not provided on ledger creation,
this feature is enabled (true) by default.
If deletion protection is enabled, you must first disable it before you can delete the ledger using
the QLDB API or the AWS Command Line Interface (AWS CLI). You can disable it by calling the
UpdateLedger operation to set the flag to false. The QLDB console disables
deletion protection for you when you use it to delete a ledger.
CreateLedgerRequest.Builder overrideConfiguration(AwsRequestOverrideConfiguration overrideConfiguration)
overrideConfiguration in interface AwsRequest.BuilderCreateLedgerRequest.Builder overrideConfiguration(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer)
overrideConfiguration in interface AwsRequest.BuilderCopyright © 2021. All rights reserved.