A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html below:

DynamoDB global tables versions - Amazon DynamoDB

DynamoDB global tables versions

There are two versions of DynamoDB global tables available: Global Tables version 2019.11.21 (Current) and Global tables version 2017.11.29 (Legacy). We recommend using Global Tables version 2019.11.21 (Current), as it is easier to use, supported in more Regions, and lower cost for most workloads compared to version 2017.11.29 (Legacy).

Determining the version of a global table Determining the version using the AWS CLI Identifying a version 2019.11.21 (Current) global table replica

To determine if a table is a global tables version 2019.11.21 (Current) replica, invoke the describe-table command for the table. If the output contains the GlobalTableVersion attribute with a value of "2019.11.21", the table is a version 2019.11.21 (Current) global table replica.

An example CLI command for describe-table:

aws dynamodb describe-table \
--table-name users \
--region us-east-2

The (abridged) output contains the GlobalTableVersion attribute with a value of "2019.11.21", so this table is a version 2019.11.21 (Current) global table replica.

{
    "Table": {
        "AttributeDefinitions": [
            {
                "AttributeName": "id",
                "AttributeType": "S"
            },
            {
                "AttributeName": "name",
                "AttributeType": "S"
            }
        ],
        "TableName": "users",
        ...
        "GlobalTableVersion": "2019.11.21",
        "Replicas": [
            {
                "RegionName": "us-west-2",
                "ReplicaStatus": "ACTIVE",
            }
        ],
        ...
    }
}
Identifying a version 2017.11.29 (Legacy) global table replica

Global tables version 2017.11.29 (Legacy) uses a dedicated set of commands for global table management. To determine if a table is a global tables version 2017.11.29 (Legacy) replica, invoke the describe-global-table command for the table. If you receive a successful response, the table is a version 2017.11.29 (Legacy) global table replica. If the describe-global-table command returns a GlobalTableNotFoundException error, the table is not a version 2017.11.29 (Legacy) replica.

An example CLI command for describe-global-table:

aws dynamodb describe-global-table \
--table-name users \
--region us-east-2

The command returns a successful response, so this table is a version 2017.11.29 (Legacy) global table replica.

{
    "GlobalTableDescription": {
        "ReplicationGroup": [
            {
                "RegionName": "us-west-2"
            },
            {
                "RegionName": "us-east-2"
            }
        ],
        "GlobalTableArn": "arn:aws:dynamodb::123456789012:global-table/users",
        "CreationDateTime": "2025-06-10T13:55:53.630000-04:00",
        "GlobalTableStatus": "ACTIVE",
        "GlobalTableName": "users"
    }
}
Determining the version using the DynamoDB Console

To identify the version of a global table replica, perform the following:

  1. Open the DynamoDB console at https://console.aws.amazon.com/dynamodb/home.

  2. In the navigation pane on the left side of the console, choose Tables.

  3. Choose the table you want to identify the global tables version for.

  4. Choose the Global Tables tab.

    The Summary section displays the version of global tables in use.

Differences in behavior between Legacy and Current versions

The following list describes the differences in behavior between the Legacy and Current versions of global tables.

Upgrading to the current version Required permissions for global tables upgrade

To upgrade to version 2019.11.21 (Current), you must have dynamodb:UpdateGlobalTableversion permissions in all Regions with replicas. These permissions are required in addition to the permissions needed for accessing the DynamoDB console and viewing tables.

The following IAM policy grants permissions to upgrade any global table to version 2019.11.21 (Current).

{
    "version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "dynamodb:UpdateGlobalTableversion",
            "Resource": "*"
        }
    ]
}

The following IAM policy grants permissions to upgrade only the Music global table with replicas in two Regions to version 2019.11.21 (Current).

{
    "version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "dynamodb:UpdateGlobalTableversion",
            "Resource": [
                "arn:aws:dynamodb::123456789012:global-table/Music",
                "arn:aws:dynamodb:ap-southeast-1:123456789012:table/Music",
                "arn:aws:dynamodb:us-east-2:123456789012:table/Music"
            ]
        }
    ]
}
What to expect during the upgrade DynamoDB Streams behavior before, during, and after upgrade Operation Replica Region Behavior before upgrade Behavior during upgrade Behavior after upgrade

Put or Update

Source

Timestamp population happens using UpdateItem. Timestamp population happens using PutItem. No customer visible timestamp is generated. Two Streams records are generated. The first record contains the customer written attributes. The second record contains the aws:rep:* attributes. Two Streams records are generated. The first record contains the customer written attributes. The second record contains the aws:rep:* attributes. A single Streams record is generated containing the customer-writen attributes. Two rWCUs are consumed for each customer write. Two rWCUs are consumed for each customer write. One rWCU is consumed for each customer write. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency metric is published in CloudWatch.

Destination

Replication happens using PutItem. Replication happens using PutItem. Replication happens using PutItem. A single Streams record is generated, which contains both the customer-written attributes and the aws:rep:* attributes. A single Streams record is generated, which contains both the customer-written attributes and the aws:rep:* attributes. A single Streams record is generated, which contains the customer-written attributes only and no replication attributes. One rWCU is consumed if the item exists in the destination Region. Two rWCUs are consumed if the item doesn't exist in the destination Region. One rWCU is consumed if the item exists in the destination Region. Two rWCUs are consumed if the item doesn't exist in the destination Region. One rWCU is consumed for each customer write. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency metric is published in CloudWatch.

Delete

Source

Delete any item with smaller timestamp using DeleteItem. Delete any item with smaller timestamp using DeleteItem. Delete any item with smaller timestamp using DeleteItem. A single Streams record is generated, which contains both the customer-written attributes and the aws:rep:* attributes. A single Streams record is generated, which contains both the customer-written attributes and the aws:rep:* attributes. A single Streams record is generated, which contains the customer-written attributes. One rWCU is consumed for each customer delete. One rWCU is consumed for each customer delete. One rWCU is consumed for each customer delete. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency metric is published in CloudWatch.

Destination

Two-phase deletes take place:

Deletes the item using DeleteItem. Deletes the item using DeleteItem. Two Streams records are generated. The first record contains the change to the aws:rep:deleting field. The second record contains the customer-written attributes and the aws:rep:* attributes. A single Stream record is generated, which contains the customer-written attributes. A single Stream record is generated, which contains the customer-written attributes. Two rWCUs are consumed for each customer delete. One rWCU is consumed for each customer delete. One rWCU is consumed for each customer delete. ReplicationLatency and PendingReplicationCount metrics are published in CloudWatch. ReplicationLatency metric is published in CloudWatch. ReplicationLatency metric is published in CloudWatch. Upgrading to version 2019.11.21 (Current)

Perform the following steps to upgrade your version of DynamoDB global tables using the AWS Management Console.

To upgrade global tables to version 2019.11.21 (Current)

  1. Open the DynamoDB console at https://console.aws.amazon.com/dynamodb/home.

  2. In the navigation pane on the left side of the console, choose Tables, and then select the global table that you want to upgrade to version 2019.11.21 (Current).

  3. Choose the Global Tables tab.

  4. Choose Update version.

  5. Read and agree to the new requirements, and then choose Update version.

  6. After the upgrade process is complete, the global tables version that appears on the console changes to 2019.11.21.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4