CREATELEDGER()`¶

About CreateLedger¶

Creates a new ledger in your Amazon Web Services account in the current Region.

Method Signature¶

IMPORTING¶

Required arguments:¶

`iv_name` `TYPE /AWS1/QLDLEDGERNAME` `/AWS1/QLDLEDGERNAME`¶

The name of the ledger that you want to create. The name must be unique among all of the ledgers in your Amazon Web Services account in the current Region.

Naming constraints for ledger names are defined in Quotas in Amazon QLDB in the Amazon QLDB Developer Guide.

`iv_permissionsmode` `TYPE /AWS1/QLDPERMISSIONSMODE` `/AWS1/QLDPERMISSIONSMODE`¶

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 the SendCommand API permission 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 the SendCommand API permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.

We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.

Optional arguments:¶

`it_tags` `TYPE /AWS1/CL_QLDTAGS_W=>TT_TAGS` `TT_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.

`iv_deletionprotection` `TYPE /AWS1/QLDDELETIONPROTECTION` `/AWS1/QLDDELETIONPROTECTION`¶

Specifies whether the ledger is protected from being deleted by any user. If not defined during 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. You can disable it by calling the UpdateLedger operation to set this parameter to false.

`iv_kmskey` `TYPE /AWS1/QLDKMSKEY` `/AWS1/QLDKMSKEY`¶

The key in Key Management Service (KMS) to use for encryption of data at rest in the ledger. For more information, see Encryption at rest in the Amazon QLDB Developer Guide.

Use one of the following options to specify this parameter:

AWS_OWNED_KMS_KEY: Use an KMS key that is owned and managed by Amazon Web Services on your behalf.

Undefined: By default, use an Amazon Web Services owned KMS key.

A valid symmetric customer managed KMS key: Use the specified symmetric encryption KMS key in your account that you create, own, and manage.

Amazon QLDB does not support asymmetric keys. For more information, see Using symmetric and asymmetric keys in the Key Management Service Developer Guide.

To specify a customer managed KMS key, you can use its key ID, Amazon Resource Name (ARN), alias name, or alias ARN. When using an alias name, prefix it with "alias/". To specify a key in a different Amazon Web Services account, you must use the key ARN or alias ARN.

For example:

Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab

Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab

Alias name: alias/ExampleAlias

Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias

For more information, see Key identifiers (KeyId) in the Key Management Service Developer Guide.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_qldcreateledgerrsp` `/AWS1/CL_QLDCREATELEDGERRSP`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->/aws1/if_qld~createledger(
  it_tags = VALUE /aws1/cl_qldtags_w=>tt_tags(
    (
      VALUE /aws1/cl_qldtags_w=>ts_tags_maprow(
        value = new /aws1/cl_qldtags_w( |string| )
        key = |string|
      )
    )
  )
  iv_deletionprotection = ABAP_TRUE
  iv_kmskey = |string|
  iv_name = |string|
  iv_permissionsmode = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_ledgername = lo_result->get_name( ).
  lv_arn = lo_result->get_arn( ).
  lv_ledgerstate = lo_result->get_state( ).
  lv_timestamp = lo_result->get_creationdatetime( ).
  lv_permissionsmode = lo_result->get_permissionsmode( ).
  lv_deletionprotection = lo_result->get_deletionprotection( ).
  lv_arn = lo_result->get_kmskeyarn( ).
ENDIF.

/AWS1/CL_QLD=>CREATELEDGER()¶