{
    "componentChunkName": "component---src-templates-mdx-content-page-js",
    "path": "/dynamodb-warm-throughput/",
    "result": {"data":{"mdx":{"body":"var _excluded = [\"components\"];\n\nfunction _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsxRuntime classic */\n\n/* @jsx mdx */\nvar _frontmatter = {\n  \"path\": \"/dynamodb-warm-throughput/\",\n  \"publishedDate\": \"2026-11-20\",\n  \"updatedDate\": \"2026-11-20\",\n  \"metaTitle\": \"DynamoDB Warm Throughput: Pre-Warming, Limits and Cost\",\n  \"metaDescription\": \"Check DynamoDB warm throughput, pre-warm tables and global secondary indexes, and calculate the one-time fee. Includes CLI, SDK and IaC examples.\",\n  \"title\": \"DynamoDB Warm Throughput: How to Pre-Warm Tables and Indexes\",\n  \"authorName\": \"Rafal Wilinski\",\n  \"authorLink\": \"https://x.com/rafalwilinski\",\n  \"authorImage\": \"/images/authors/rafal-wilinski.jpg\"\n};\nvar layoutProps = {\n  _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n  var components = _ref.components,\n      props = _objectWithoutProperties(_ref, _excluded);\n\n  return mdx(MDXLayout, _extends({}, layoutProps, props, {\n    components: components,\n    mdxType: \"MDXLayout\"\n  }), mdx(\"p\", null, \"DynamoDB warm throughput is the read and write capacity a table or global secondary index (GSI) is prepared to serve immediately across its partitions. AWS launched it on November 13, 2024, for both on-demand and provisioned capacity modes. Pre-warming means setting a higher warm throughput ahead of a known traffic jump. Check \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"WarmThroughput\"), \" with \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"DescribeTable\"), \", then use \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"CreateTable\"), \" or \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"UpdateTable\"), \" to raise it if your peak will exceed the current values. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://aws.amazon.com/about-aws/whats-new/2024/11/amazon-dynamodb-warm-throughput-ondemand-provisioned-tables/\"\n  }, \"AWS launch announcement\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput.html\"\n  }, \"AWS warm throughput guide\")), mdx(\"h2\", null, \"Defaults and partition limits\"), mdx(\"p\", null, \"Pre-warming prepares DynamoDB's internal partition layout for higher aggregate traffic. DynamoDB also raises the warm values automatically as on-demand usage grows or you increase provisioned capacity. Each physical partition can serve up to \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"3,000 read units/s and 1,000 write units/s\"), \". A table prepared for 10,000 write units/s can still throttle well below that rate if most writes hit one partition. A GSI has its own partitions and can throttle base-table writes through back-pressure. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://aws.amazon.com/blogs/database/choose-the-right-throughput-strategy-for-amazon-dynamodb-applications/\"\n  }, \"AWS throughput strategies\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput-scenarios.html\"\n  }, \"AWS partition scenarios\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/gsi-throttling.html\"\n  }, \"AWS GSI back-pressure guide\")), mdx(\"table\", null, mdx(\"thead\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"thead\"\n  }, mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Capacity mode\"), mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Starting throughput without manual pre-warming\"))), mdx(\"tbody\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"On-demand\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"strong\", {\n    parentName: \"td\"\n  }, \"12,000 read units/s and 4,000 write units/s\"), \" for a new table. AWS shows the same default values for a new on-demand GSI. \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput-scenarios.html\"\n  }, \"AWS warm throughput scenarios\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/check-warm-throughput.html\"\n  }, \"AWS DescribeTable example\"))), mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Provisioned\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Use the \", mdx(\"strong\", {\n    parentName: \"td\"\n  }, \"RCUs and WCUs you specify at creation\"), \" as the initial baseline for the table and each GSI. For example, AWS shows a provisioned GSI with 50 RCUs and 25 WCUs reporting 50 read and 25 write units/s before a warm increase takes effect. Check the reported values with \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"DescribeTable\"), \". \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html\"\n  }, \"AWS provisioned capacity guide\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/update-warm-throughput.html\"\n  }, \"AWS provisioned GSI example\"))))), mdx(\"p\", null, \"Size the peak in units per second. For an item up to 4 KB, one strongly consistent read uses one read unit and an eventually consistent read uses half a unit. A standard write up to 1 KB uses one write unit. Larger items and \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"/dynamodb-transactions/\"\n  }, \"transactional operations\"), \" can use more. Estimate base-table and GSI demand separately, including the index writes your application generates. The \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"/dynamodb-capacity-modes/\"\n  }, \"DynamoDB capacity modes guide\"), \" covers the capacity and billing terminology. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/read-write-operations.html\"\n  }, \"AWS read and write operations\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.html\"\n  }, \"AWS GSI capacity guide\")), mdx(\"h2\", null, \"Check warm throughput and readiness\"), mdx(\"p\", null, \"In the DynamoDB console, open \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Tables\"), \", select your table, and find \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Warm throughput\"), \" on its details page. \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"DescribeTable\"), \" returns \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Table.WarmThroughput\"), \" and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Table.GlobalSecondaryIndexes[].WarmThroughput\"), \". Each object has \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ReadUnitsPerSecond\"), \", \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"WriteUnitsPerSecond\"), \", and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Status\"), \". This CLI v2 query shows the warm fields alongside the lifecycle status of the table and each index. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/check-warm-throughput.html\"\n  }, \"AWS console and DescribeTable walkthrough\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-bash\"\n  }, \"aws dynamodb describe-table --region us-east-1 --table-name Orders \\\\\\n  --query 'Table.{TableStatus:TableStatus,Warm:WarmThroughput,Indexes:GlobalSecondaryIndexes[].{Name:IndexName,IndexStatus:IndexStatus,Warm:WarmThroughput}}' \\\\\\n  --output json\\n\")), mdx(\"p\", null, \"Pre-warming is asynchronous. AWS says the time depends on the requested throughput and the size of the table or index. Build lead time into the rollout and poll \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"DescribeTable\"), \" until the warm status is \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ACTIVE\"), \" and both reported values meet your targets. Start the traffic increase only after the base table and every relevant GSI pass that check. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput.html\"\n  }, \"AWS warm throughput guide\")), mdx(\"table\", null, mdx(\"thead\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"thead\"\n  }, mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Change\"), mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Status to check\"))), mdx(\"tbody\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Pre-warm an existing table or GSI\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"WarmThroughput.Status\"), \" moves from \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"UPDATING\"), \" to \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"ACTIVE\"), \". The existing table and index can remain \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"ACTIVE\"), \" and continue serving traffic during pre-warming. \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/update-warm-throughput.html\"\n  }, \"AWS update walkthrough\"))), mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Create a table or GSI with higher warm throughput\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Wait for \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"TableStatus\"), \" or \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"IndexStatus\"), \" to reach \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"ACTIVE\"), \" from \", mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"CREATING\"), \", then check that resource's warm status and values. A \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"/dynamodb-faq/how-to-create-index-in-dynamodb/\"\n  }, \"GSI added to an existing table\"), \" can also spend time backfilling. \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/create-table-warm-throughput.html\"\n  }, \"AWS create walkthrough\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"td\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.html\"\n  }, \"AWS online GSI operations\"))))), mdx(\"h2\", null, \"How to pre-warm a DynamoDB table and GSI\"), mdx(\"p\", null, \"Pass \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"WarmThroughput\"), \" with \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ReadUnitsPerSecond\"), \", \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"WriteUnitsPerSecond\"), \", or both. Omit \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Status\"), \" from requests. Use the top-level field for the base table. Set the GSI's warm throughput on its own definition or update action. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_WarmThroughput.html\"\n  }, \"AWS WarmThroughput type\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateTable.html\"\n  }, \"CreateTable API\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html\"\n  }, \"UpdateTable API\")), mdx(\"table\", null, mdx(\"thead\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"thead\"\n  }, mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Operation\"), mdx(\"th\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, \"Field for the GSI\"))), mdx(\"tbody\", {\n    parentName: \"table\"\n  }, mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"CreateTable\"), \" with a new GSI\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"GlobalSecondaryIndexes[].WarmThroughput\"))), mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"UpdateTable\"), \" on an existing GSI\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"GlobalSecondaryIndexUpdates[].Update.WarmThroughput\"))), mdx(\"tr\", {\n    parentName: \"tbody\"\n  }, mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"UpdateTable\"), \" to add a GSI\"), mdx(\"td\", {\n    parentName: \"tr\",\n    \"align\": null\n  }, mdx(\"inlineCode\", {\n    parentName: \"td\"\n  }, \"GlobalSecondaryIndexUpdates[].Create.WarmThroughput\"))))), mdx(\"p\", null, \"In the console, choose \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Customize settings\"), \" and \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Increase warm throughput\"), \" when creating a table. For an existing table, choose \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Edit\"), \" in the \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Warm throughput\"), \" section, then \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"Increase warm throughput\"), \" and save. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/create-table-warm-throughput.html\"\n  }, \"AWS create instructions\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/update-warm-throughput.html\"\n  }, \"AWS update instructions\")), mdx(\"h3\", null, \"AWS CLI v2\"), mdx(\"p\", null, \"Create a new on-demand \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Orders\"), \" table with a \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ByCustomer\"), \" GSI. The base table starts with targets of 24,000 read and 10,000 write units/s. The index targets 18,000 read and 10,000 write units/s. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/cli/latest/reference/dynamodb/create-table.html\"\n  }, \"AWS CLI create-table reference\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-bash\"\n  }, \"aws dynamodb create-table --region us-east-1 --table-name Orders \\\\\\n  --billing-mode PAY_PER_REQUEST \\\\\\n  --attribute-definitions AttributeName=OrderId,AttributeType=S AttributeName=CustomerId,AttributeType=S \\\\\\n  --key-schema AttributeName=OrderId,KeyType=HASH \\\\\\n  --warm-throughput ReadUnitsPerSecond=24000,WriteUnitsPerSecond=10000 \\\\\\n  --global-secondary-indexes '[{\\n    \\\"IndexName\\\": \\\"ByCustomer\\\",\\n    \\\"KeySchema\\\": [{\\\"AttributeName\\\": \\\"CustomerId\\\", \\\"KeyType\\\": \\\"HASH\\\"}],\\n    \\\"Projection\\\": {\\\"ProjectionType\\\": \\\"KEYS_ONLY\\\"},\\n    \\\"WarmThroughput\\\": {\\\"ReadUnitsPerSecond\\\": 18000, \\\"WriteUnitsPerSecond\\\": 10000}\\n  }]'\\n\")), mdx(\"p\", null, \"If \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Orders\"), \" and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ByCustomer\"), \" already exist at lower warm values, use this update instead. Read the current values first and pass only the dimensions you want to increase. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/cli/latest/reference/dynamodb/update-table.html\"\n  }, \"AWS CLI update-table reference\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/update-warm-throughput.html\"\n  }, \"AWS warm throughput update walkthrough\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-bash\"\n  }, \"aws dynamodb update-table --region us-east-1 --table-name Orders \\\\\\n  --warm-throughput ReadUnitsPerSecond=24000,WriteUnitsPerSecond=10000 \\\\\\n  --global-secondary-index-updates '[{\\n    \\\"Update\\\": {\\n      \\\"IndexName\\\": \\\"ByCustomer\\\",\\n      \\\"WarmThroughput\\\": {\\\"ReadUnitsPerSecond\\\": 18000, \\\"WriteUnitsPerSecond\\\": 10000}\\n    }\\n  }]'\\n\")), mdx(\"h3\", null, \"AWS SDK for JavaScript v3\"), mdx(\"p\", null, \"With \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"@aws-sdk/client-dynamodb\"), \", send the same update using \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"UpdateTableCommand\"), \". This example assumes both resources exist and their warm values are below the requested targets. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/dynamodb/command/UpdateTableCommand/\"\n  }, \"AWS SDK v3 UpdateTableCommand\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html\"\n  }, \"AWS API request shape\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-js\"\n  }, \"import { DynamoDBClient, UpdateTableCommand } from \\\"@aws-sdk/client-dynamodb\\\"\\n\\nconst client = new DynamoDBClient({ region: \\\"us-east-1\\\" })\\nawait client.send(new UpdateTableCommand({\\n  TableName: \\\"Orders\\\",\\n  WarmThroughput: { ReadUnitsPerSecond: 24000, WriteUnitsPerSecond: 10000 },\\n  GlobalSecondaryIndexUpdates: [{\\n    Update: {\\n      IndexName: \\\"ByCustomer\\\",\\n      WarmThroughput: { ReadUnitsPerSecond: 18000, WriteUnitsPerSecond: 10000 },\\n    },\\n  }],\\n}))\\n\")), mdx(\"h3\", null, \"boto3\"), mdx(\"p\", null, \"To add a pre-warmed \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"ByWarehouse\"), \" index to an existing on-demand \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Orders\"), \" table, use \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"GlobalSecondaryIndexUpdates\"), \" with \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Create\"), \". The index can include orders that have a string \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"WarehouseId\"), \". \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/boto3/latest/reference/services/dynamodb/client/update_table.html\"\n  }, \"boto3 \", mdx(\"inlineCode\", {\n    parentName: \"a\"\n  }, \"update_table\"), \" reference\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/bp-indexes-general-sparse-indexes.html\"\n  }, \"AWS sparse index guide\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-python\"\n  }, \"import boto3\\n\\ndynamodb = boto3.client(\\\"dynamodb\\\", region_name=\\\"us-east-1\\\")\\ndynamodb.update_table(\\n    TableName=\\\"Orders\\\",\\n    AttributeDefinitions=[{\\\"AttributeName\\\": \\\"WarehouseId\\\", \\\"AttributeType\\\": \\\"S\\\"}],\\n    GlobalSecondaryIndexUpdates=[{\\n        \\\"Create\\\": {\\n            \\\"IndexName\\\": \\\"ByWarehouse\\\",\\n            \\\"KeySchema\\\": [{\\\"AttributeName\\\": \\\"WarehouseId\\\", \\\"KeyType\\\": \\\"HASH\\\"}],\\n            \\\"Projection\\\": {\\\"ProjectionType\\\": \\\"KEYS_ONLY\\\"},\\n            \\\"WarmThroughput\\\": {\\\"ReadUnitsPerSecond\\\": 18000, \\\"WriteUnitsPerSecond\\\": 10000},\\n        },\\n    }],\\n)\\n\")), mdx(\"h3\", null, \"CloudFormation\"), mdx(\"p\", null, \"On \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"AWS::DynamoDB::Table\"), \", set \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"Properties.WarmThroughput\"), \" for the table and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"GlobalSecondaryIndexes[].WarmThroughput\"), \" for each GSI you want to pre-warm. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-dynamodb-table.html\"\n  }, \"CloudFormation table reference\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-dynamodb-table-globalsecondaryindex.html\"\n  }, \"CloudFormation GSI reference\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-yaml\"\n  }, \"Resources:\\n  Orders:\\n    Type: AWS::DynamoDB::Table\\n    Properties:\\n      BillingMode: PAY_PER_REQUEST\\n      AttributeDefinitions:\\n        - AttributeName: OrderId\\n          AttributeType: S\\n        - AttributeName: CustomerId\\n          AttributeType: S\\n      KeySchema:\\n        - AttributeName: OrderId\\n          KeyType: HASH\\n      WarmThroughput:\\n        ReadUnitsPerSecond: 24000\\n        WriteUnitsPerSecond: 10000\\n      GlobalSecondaryIndexes:\\n        - IndexName: ByCustomer\\n          KeySchema:\\n            - AttributeName: CustomerId\\n              KeyType: HASH\\n          Projection:\\n            ProjectionType: KEYS_ONLY\\n          WarmThroughput:\\n            ReadUnitsPerSecond: 18000\\n            WriteUnitsPerSecond: 10000\\n\")), mdx(\"h3\", null, \"AWS CDK v2\"), mdx(\"p\", null, \"In a TypeScript CDK app, \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"TableV2\"), \" and its GSI properties both accept \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"warmThroughput\"), \" with \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"readUnitsPerSecond\"), \" and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"writeUnitsPerSecond\"), \". \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_dynamodb.TableV2.html\"\n  }, \"CDK TableV2 reference\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_dynamodb.GlobalSecondaryIndexPropsV2.html\"\n  }, \"CDK GSI properties\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-ts\"\n  }, \"import { App, Stack } from \\\"aws-cdk-lib\\\"\\nimport { AttributeType, Billing, ProjectionType, TableV2 } from \\\"aws-cdk-lib/aws-dynamodb\\\"\\n\\nconst app = new App()\\nconst stack = new Stack(app, \\\"OrdersStack\\\")\\n\\nnew TableV2(stack, \\\"Orders\\\", {\\n  partitionKey: { name: \\\"OrderId\\\", type: AttributeType.STRING },\\n  billing: Billing.onDemand(),\\n  warmThroughput: { readUnitsPerSecond: 24000, writeUnitsPerSecond: 10000 },\\n  globalSecondaryIndexes: [{\\n    indexName: \\\"ByCustomer\\\",\\n    partitionKey: { name: \\\"CustomerId\\\", type: AttributeType.STRING },\\n    projectionType: ProjectionType.KEYS_ONLY,\\n    warmThroughput: { readUnitsPerSecond: 18000, writeUnitsPerSecond: 10000 },\\n  }],\\n})\\n\")), mdx(\"h3\", null, \"Terraform\"), mdx(\"p\", null, \"With the HashiCorp AWS provider, use \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"warm_throughput\"), \" on \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"aws_dynamodb_table\"), \" and inside \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"global_secondary_index\"), \". Both blocks use \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"read_units_per_second\"), \" and \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"write_units_per_second\"), \". \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dynamodb_table\"\n  }, \"Terraform AWS provider reference\")), mdx(\"pre\", null, mdx(\"code\", {\n    parentName: \"pre\",\n    \"className\": \"language-hcl\"\n  }, \"resource \\\"aws_dynamodb_table\\\" \\\"orders\\\" {\\n  name         = \\\"Orders\\\"\\n  billing_mode = \\\"PAY_PER_REQUEST\\\"\\n  hash_key     = \\\"OrderId\\\"\\n\\n  attribute {\\n    name = \\\"OrderId\\\"\\n    type = \\\"S\\\"\\n  }\\n\\n  attribute {\\n    name = \\\"CustomerId\\\"\\n    type = \\\"S\\\"\\n  }\\n\\n  warm_throughput {\\n    read_units_per_second  = 24000\\n    write_units_per_second = 10000\\n  }\\n\\n  global_secondary_index {\\n    name            = \\\"ByCustomer\\\"\\n    projection_type = \\\"KEYS_ONLY\\\"\\n\\n    key_schema {\\n      attribute_name = \\\"CustomerId\\\"\\n      key_type       = \\\"HASH\\\"\\n    }\\n\\n    warm_throughput {\\n      read_units_per_second  = 18000\\n      write_units_per_second = 10000\\n    }\\n  }\\n}\\n\")), mdx(\"h2\", null, \"Quotas, on-demand maximums and provisioned capacity\"), mdx(\"ul\", null, mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"Service quotas.\"), \" You can pre-warm up to the applicable regional table or GSI quota. The adjustable defaults are \", mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"40,000 read units/s and 40,000 write units/s per table or GSI\"), \". Provisioned capacity also has regional account defaults of \", mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"80,000 RCUs and 80,000 WCUs\"), \" across tables and GSIs. Check your account in Service Quotas before submitting a larger target. AWS allows simultaneous pre-warm requests and documents no limit on the number of tables you can pre-warm at once. Warm values can increase only. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ServiceQuotas.html\"\n  }, \"AWS service quotas\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput.html\"\n  }, \"AWS warm throughput guide\")), mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"On-demand maximum throughput.\"), \" \", mdx(\"inlineCode\", {\n    parentName: \"li\"\n  }, \"OnDemandThroughput.MaxReadRequestUnits\"), \" and \", mdx(\"inlineCode\", {\n    parentName: \"li\"\n  }, \"MaxWriteRequestUnits\"), \" are separate settings on the table or GSI. If you warm a table to 24,000 read units/s and set its maximum to 10,000, plan for \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"/dynamodb-errors/dynamodb-throughput-error/\"\n  }, \"throughput throttling\"), \" above 10,000. AWS applies this maximum on a best-effort basis, so burst capacity can temporarily let requests through. See \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"/dynamodb-on-demand-vs-provisioned-scaling/\"\n  }, \"on-demand versus provisioned scaling\"), \" for how the two modes handle spikes. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode-max-throughput.html\"\n  }, \"AWS maximum throughput guide\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput-scenarios.html\"\n  }, \"AWS warm throughput scenarios\")), mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"Provisioned capacity.\"), \" A table warm to 10,000 writes/s with 2,000 WCUs provisioned still has 2,000 WCUs of configured capacity. Raise the provisioned capacity ahead of the event or adjust auto scaling so capacity is already in place when traffic arrives. Apply the same check to each provisioned GSI. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput-scenarios.html\"\n  }, \"AWS warm throughput scenarios\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html\"\n  }, \"AWS provisioned capacity guide\"))), mdx(\"h2\", null, \"Pricing and a worked cost example\"), mdx(\"p\", null, \"AWS charges a \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"one-time fee\"), \" for each manual increase. Multiply the extra read units by the regional RCU rate and the extra write units by the regional WCU rate. The calculation uses the difference from each resource's current warm throughput. AWS charges for table and index increases separately, and it applies the same model to Standard and Standard-Infrequent Access. Viewing the values and automatic increases carry no warm throughput fee. For current-version global tables (\", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"2019.11.21\"), \"), the settings propagate to replicas and AWS charges in each replica Region. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://aws.amazon.com/dynamodb/pricing/\"\n  }, \"DynamoDB pricing\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput.html\"\n  }, \"AWS warm throughput guide\")), mdx(\"p\", null, \"Suppose an on-demand table in \", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"us-east-1\"), \" is already warm to 12,000 read and 4,000 write units/s. Raising it to 24,000 read and 10,000 write units/s adds 12,000 read and 6,000 write units. At the N. Virginia rates of $0.00013 per added read unit and $0.00065 per added write unit, the one-time charge is \", mdx(\"strong\", {\n    parentName: \"p\"\n  }, \"$5.46\"), \" (\", mdx(\"inlineCode\", {\n    parentName: \"p\"\n  }, \"12,000 \\xD7 $0.00013 + 6,000 \\xD7 $0.00065\"), \"). Add any GSI or replica fees separately. Use the \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"/dynamodb-pricing-calculator/\"\n  }, \"DynamoDB pricing calculator\"), \" for ongoing traffic and storage costs. \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://aws.amazon.com/dynamodb/pricing/\"\n  }, \"DynamoDB pricing\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"p\",\n    \"href\": \"https://aws.amazon.com/blogs/database/pre-warming-amazon-dynamodb-tables-with-warm-throughput/\"\n  }, \"AWS pre-warming rate example\")), mdx(\"h2\", null, \"When to pre-warm DynamoDB\"), mdx(\"ul\", null, mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"Launches and peak events.\"), \" Pre-warm when a cutover, flash sale or launch will bring a predictable step increase across many keys. Compare the expected peak with the current warm values and raise only the resources and dimensions that need more capacity. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://aws.amazon.com/blogs/database/pre-warming-amazon-dynamodb-tables-with-warm-throughput/\"\n  }, \"AWS pre-warming use cases\")), mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"Migrations.\"), \" Prepare the destination before switching live traffic or starting a \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"/dynamodb-batch-write-update-delete/\"\n  }, \"write-heavy backfill via the DynamoDB API\"), \". Include index write demand when sizing the target. If you control the producer rate, gradual ramp-up is another option. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://aws.amazon.com/blogs/database/pre-warming-amazon-dynamodb-tables-with-warm-throughput/\"\n  }, \"AWS pre-warming use cases\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html\"\n  }, \"AWS on-demand scaling guidance\")), mdx(\"li\", {\n    parentName: \"ul\"\n  }, mdx(\"strong\", {\n    parentName: \"li\"\n  }, \"Gradual growth and hot keys.\"), \" Skip paid pre-warming when the expected load fits the current warm values or can ramp gradually. AWS says on-demand traffic can throttle if it exceeds twice the previous peak within 30 minutes. If throttling is concentrated on one key or one index key range, fix the \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"/dynamodb-hot-partitions/\"\n  }, \"hot partitions\"), \" by redistributing traffic. Use the \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"/dynamodb-throttling/\"\n  }, \"DynamoDB throttling guide\"), \" to identify the affected resource and limit. \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html\"\n  }, \"AWS on-demand scaling guidance\"), \" \\xB7 \", mdx(\"a\", {\n    parentName: \"li\",\n    \"href\": \"https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/warm-throughput-scenarios.html\"\n  }, \"AWS warm throughput scenarios\"))), mdx(FAQ, {\n    questions: [{\n      question: \"What is DynamoDB warm throughput?\",\n      answer: \"It is the read and write capacity per second that a DynamoDB table or global secondary index is prepared to serve immediately. DynamoDB adjusts it as usage or provisioned capacity grows, and you can raise it ahead of a planned traffic spike.\"\n    }, {\n      question: \"How do I pre-warm an existing DynamoDB table?\",\n      answer: \"Send UpdateTable with WarmThroughput and the desired read units per second, write units per second, or both. Specify a global secondary index in GlobalSecondaryIndexUpdates if it also needs a higher target. Use DescribeTable to confirm the warm status and values.\"\n    }, {\n      question: \"How long does DynamoDB pre-warming take?\",\n      answer: \"The time varies with the requested values and the storage size of the table or index. Check that WarmThroughput.Status is ACTIVE and the reported values meet your targets before increasing traffic.\"\n    }, {\n      question: \"Does DynamoDB warm throughput cost extra?\",\n      answer: \"AWS bills a one-time regional charge for the extra read and write units you request manually. Default values and automatic increases carry no warm throughput fee.\"\n    }, {\n      question: \"Can pre-warming fix a hot partition key?\",\n      answer: \"Pre-warming prepares aggregate capacity across partitions. If requests concentrate on a hot key, redistribute the traffic or reduce repeated access to that key.\"\n    }],\n    mdxType: \"FAQ\"\n  }));\n}\n;\nMDXContent.isMDXComponent = true;","frontmatter":{"publishedDate":"2026-11-20","updatedDate":"2026-11-20","path":"/dynamodb-warm-throughput/","metaTitle":"DynamoDB Warm Throughput: Pre-Warming, Limits and Cost","metaDescription":"Check DynamoDB warm throughput, pre-warm tables and global secondary indexes, and calculate the one-time fee. Includes CLI, SDK and IaC examples.","title":"DynamoDB Warm Throughput: How to Pre-Warm Tables and Indexes","authorName":"Rafal Wilinski","authorLink":"https://x.com/rafalwilinski","authorImage":"/images/authors/rafal-wilinski.jpg","image":null}}},"pageContext":{}},
    "staticQueryHashes": ["3649515864"]}