Amazon DynamoDB + NodeHub

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Returns DynamoDB on-demand backups, not AWS Backup service jobs. The lower time bound is inclusive and the upper bound is exclusive.
• Collections pace to the provider limit and stop at 100 pages, 60 seconds or 1.8 MB. Results are not a snapshot.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Limit counts evaluated items before filtering. Continue after an empty filtered page when nextCursor exists. Preserve table, index, expressions and scan segment when resuming.
• Scan reads consume capacity and are not snapshot reads, even with consistentRead. Global indexes do not support strong consistency. AWS enforces index projection and expression semantics.
• Collections stop at 100 pages, 60 seconds or 1.8 MB. Count mode returns counts without items. Segment selects one existing parallel-scan segment; this operation does not launch other workers.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Limit counts evaluated items before filtering. Continue after an empty filtered page when nextCursor exists. Preserve table, index, expressions and scan segment when resuming.
• Scan reads consume capacity and are not snapshot reads, even with consistentRead. Global indexes do not support strong consistency. AWS enforces index projection and expression semantics.
• Collections stop at 100 pages, 60 seconds or 1.8 MB. Count mode returns counts without items. Segment selects one existing parallel-scan segment; this operation does not launch other workers.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Collections stop at 100 pages, 60 seconds or 1.8 MB. Keep the same table, stream and parent filter when continuing. Empty pages with nextCursor still require continuation.
• Calls within this collection are spaced below the per-operation AWS request rate. Concurrent workflows share provider limits and can still be throttled.
• Shard inventory changes over time and is not a snapshot. Duplicate shards or changing stream identity fail explicitly. Process parent shards before children; this operation does not consume records.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Collections stop at 100 pages, 60 seconds or 1.8 MB. Keep the same table, stream and parent filter when continuing. Empty pages with nextCursor still require continuation.
• Calls within this collection are spaced below the per-operation AWS request rate. Concurrent workflows share provider limits and can still be throttled.
• Shard inventory changes over time and is not a snapshot. Duplicate shards or changing stream identity fail explicitly. Process parent shards before children; this operation does not consume records.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Use a table ARN in the connection region. Preserve that ARN when continuing. Empty pages with nextCursor are incomplete. Tags remain a list, with empty and null values preserved.
• Collections stop at 100 pages, 60 seconds or 1.8 MB and reject duplicate tag keys. Concurrent tag changes are not a snapshot. This operation does not add or remove tags.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Collections stop at 100 pages, 60 seconds or 1.85 MB. Preserve the region and use nextCursor to continue. Listing is not a snapshot.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• The receipt confirms the asynchronous backup request, not that the backup is available for restore. Inspect its status separately.
• A lost or malformed response remains uncertain and is not resent automatically. AWS quotas, table state and permissions apply.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• The receipt confirms asynchronous creation in CREATING state, not a table ready for traffic. Poll Describe Table before use.
• This bounded operation creates only the primary key. Add secondary indexes, streams, TTL, recovery, tags and scaling separately.
• Provisioned capacities are limited to 1 through 40000 per request. AWS quotas and charges apply. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Deletion cannot be undone. AWS Backup service recovery points use a different API.
• A lost or malformed response remains uncertain and is not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Put replaces the whole item. Update can create an item if none exists. Use conditionExpression to restrict changes. Conditional refusal is a failed operation; lost replies remain uncertain without resend.
• Numbers remain strings, including precision beyond JavaScript numbers. Binary uses base64; false, null, lists and maps retain their DynamoDB descriptors. AWS validates table keys, indexes, item sizes and expression semantics.
• Local typed maps are bounded to 600 KB of encoded JSON, 32 nested levels and 20000 attributes, subject to the existing workflow mapping and 1 MB request limits. AWS limits stored items to 400 KB. Server credentials never enter workflow fields.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• This permanently deletes the table, its items and indexes. Streams become disabled and are removed later by AWS. Deletion protection and table state can prevent the request.
• The receipt can report DELETING before removal finishes. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Backup status can still be CREATING or DELETED. A successful read does not mean the backup is currently restorable.
• This describes DynamoDB on-demand backups, not AWS Backup service recovery points.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Streams must already be enabled on the table. Verification of ListTables does not prove stream permissions. Stream records expire after 24 hours; shard iterators expire after 15 minutes.
• An empty record page can still have nextShardIterator. Continue with it; complete is true only when the shard has ended. Process parent shards before child shards. These operations do not start a continuous consumer.
• ListStreams is limited to five requests per second and DescribeStream to ten. Read pages contain at most 1000 records or 1 MB of native data, subject to the local 1.9 MB encoded reply limit. Use a smaller page if necessary.
• Sequence numbers remain strings. Expired iterators and trimmed history fail explicitly; no data recovery is invented.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Size and item counts are approximate. Optional metadata stays absent when AWS omits it. This reads settings and does not configure streams, recovery, encryption or replication.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Put replaces the whole item. Update can create an item if none exists. Use conditionExpression to restrict changes. Conditional refusal is a failed operation; lost replies remain uncertain without resend.
• Numbers remain strings, including precision beyond JavaScript numbers. Binary uses base64; false, null, lists and maps retain their DynamoDB descriptors. AWS validates table keys, indexes, item sizes and expression semantics.
• Local typed maps are bounded to 600 KB of encoded JSON, 32 nested levels and 20000 attributes, subject to the existing workflow mapping and 1 MB request limits. AWS limits stored items to 400 KB. Server credentials never enter workflow fields.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Streams must already be enabled on the table. Verification of ListTables does not prove stream permissions. Stream records expire after 24 hours; shard iterators expire after 15 minutes.
• An empty record page can still have nextShardIterator. Continue with it; complete is true only when the shard has ended. Process parent shards before child shards. These operations do not start a continuous consumer.
• ListStreams is limited to five requests per second and DescribeStream to ten. Read pages contain at most 1000 records or 1 MB of native data, subject to the local 1.9 MB encoded reply limit. Use a smaller page if necessary.
• Sequence numbers remain strings. Expired iterators and trimmed history fail explicitly; no data recovery is invented.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Returns DynamoDB on-demand backups, not AWS Backup service jobs. The lower time bound is inclusive and the upper bound is exclusive.
• Collections pace to the provider limit and stop at 100 pages, 60 seconds or 1.8 MB. Results are not a snapshot.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Streams must already be enabled on the table. Verification of ListTables does not prove stream permissions. Stream records expire after 24 hours; shard iterators expire after 15 minutes.
• An empty record page can still have nextShardIterator. Continue with it; complete is true only when the shard has ended. Process parent shards before child shards. These operations do not start a continuous consumer.
• ListStreams is limited to five requests per second and DescribeStream to ten. Read pages contain at most 1000 records or 1 MB of native data, subject to the local 1.9 MB encoded reply limit. Use a smaller page if necessary.
• Sequence numbers remain strings. Expired iterators and trimmed history fail explicitly; no data recovery is invented.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Use a table ARN in the connection region. Preserve that ARN when continuing. Empty pages with nextCursor are incomplete. Tags remain a list, with empty and null values preserved.
• Collections stop at 100 pages, 60 seconds or 1.8 MB and reject duplicate tag keys. Concurrent tag changes are not a snapshot. This operation does not add or remove tags.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Collections stop at 100 pages, 60 seconds or 1.85 MB. Preserve the region and use nextCursor to continue. Listing is not a snapshot.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Put replaces the whole item. Update can create an item if none exists. Use conditionExpression to restrict changes. Conditional refusal is a failed operation; lost replies remain uncertain without resend.
• Numbers remain strings, including precision beyond JavaScript numbers. Binary uses base64; false, null, lists and maps retain their DynamoDB descriptors. AWS validates table keys, indexes, item sizes and expression semantics.
• Local typed maps are bounded to 600 KB of encoded JSON, 32 nested levels and 20000 attributes, subject to the existing workflow mapping and 1 MB request limits. AWS limits stored items to 400 KB. Server credentials never enter workflow fields.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• A successful call can process only part of the batch. Inspect complete and unprocessedCount. No automatic resend occurs. Lost or malformed write replies remain uncertain.
• At most 100 read keys or 25 writes across all tables. Requests are locally capped at 950 KB and replies at 1.9 MB, below AWS batch limits. Split larger batches. Put replaces an item; batch writes cannot use conditions or updates.
• Read results are unordered and missing items are omitted. Include primary keys in projections to associate returned items. Unprocessed read output preserves submitted projection and consistency options.
• AWS checks key schema, duplicate put/delete targets and native item size. Table identifiers with the same table name cannot share one batch. Credentials remain in the server vault.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Limit counts evaluated items before filtering. Continue after an empty filtered page when nextCursor exists. Preserve table, index, expressions and scan segment when resuming.
• Scan reads consume capacity and are not snapshot reads, even with consistentRead. Global indexes do not support strong consistency. AWS enforces index projection and expression semantics.
• Collections stop at 100 pages, 60 seconds or 1.8 MB. Count mode returns counts without items. Segment selects one existing parallel-scan segment; this operation does not launch other workers.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• TTL state does not confirm that an expired item was deleted. Continuous backup status is distinct from point-in-time recovery status. Omitted recovery dates remain unknown. This operation does not enable TTL, backups or recovery.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Limit counts evaluated items before filtering. Continue after an empty filtered page when nextCursor exists. Preserve table, index, expressions and scan segment when resuming.
• Scan reads consume capacity and are not snapshot reads, even with consistentRead. Global indexes do not support strong consistency. AWS enforces index projection and expression semantics.
• Collections stop at 100 pages, 60 seconds or 1.8 MB. Count mode returns counts without items. Segment selects one existing parallel-scan segment; this operation does not launch other workers.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Streams must already be enabled on the table. Verification of ListTables does not prove stream permissions. Stream records expire after 24 hours; shard iterators expire after 15 minutes.
• An empty record page can still have nextShardIterator. Continue with it; complete is true only when the shard has ended. Process parent shards before child shards. These operations do not start a continuous consumer.
• ListStreams is limited to five requests per second and DescribeStream to ten. Read pages contain at most 1000 records or 1 MB of native data, subject to the local 1.9 MB encoded reply limit. Use a smaller page if necessary.
• Sequence numbers remain strings. Expired iterators and trimmed history fail explicitly; no data recovery is invented.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Up to 100 actions; local request and response caps are 950 KB and 1.9 MB. AWS enforces native 4 MB transaction and 400 KB item limits. No two write actions may target one item.
• Put replaces an item; Update can create one. Use conditions to restrict writes. Atomic cancellation fails the operation. In-progress, lost or malformed write replies remain uncertain without automatic resend.
• An optional clientRequestId maps to AWS ClientRequestToken. Identical requests are idempotent for only ten minutes after first completion; reusing it later can repeat changes. Changed parameters within that window are refused by AWS.
• Ordered read response envelopes preserve missing and empty results. Condition failure item bodies are not requested or returned. Account credentials stay in the server vault.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• TTL state does not confirm that an expired item was deleted. Continuous backup status is distinct from point-in-time recovery status. Omitted recovery dates remain unknown. This operation does not enable TTL, backups or recovery.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• This asynchronous receipt confirms request acceptance only. ListTagsOfResource is eventually consistent and can briefly return removed keys.
• Missing keys are ignored by AWS. Keys beginning with aws: are reserved. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• The receipt confirms an asynchronous restore request in CREATING state, not a usable table. Poll table status separately.
• This basic operation restores the backup defaults. Billing, capacity, encryption and index overrides are not exposed here. Tags, streams, TTL, auto scaling, IAM policies, metrics and alarms must be configured separately.
• The target table must not already exist. Restores can incur AWS charges and quota use. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Supply exactly one of latest available time or an explicit Unix timestamp. The source must already have point-in-time recovery for that moment.
• The receipt confirms an asynchronous restore in CREATING state, not a usable table. This basic operation does not expose billing, capacity, encryption or index overrides.
• Tags, streams, TTL, point-in-time recovery, auto scaling, IAM policies, metrics and alarms must be configured separately on the new table. Charges and restore quotas apply. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• This asynchronous receipt confirms request acceptance only. ListTagsOfResource is eventually consistent and can briefly return the previous set.
• Existing matching keys are replaced. Each table supports up to 50 user tags. Keys beginning with aws: are reserved. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Put replaces the whole item. Update can create an item if none exists. Use conditionExpression to restrict changes. Conditional refusal is a failed operation; lost replies remain uncertain without resend.
• Numbers remain strings, including precision beyond JavaScript numbers. Binary uses base64; false, null, lists and maps retain their DynamoDB descriptors. AWS validates table keys, indexes, item sizes and expression semantics.
• Local typed maps are bounded to 600 KB of encoded JSON, 32 nested levels and 20000 attributes, subject to the existing workflow mapping and 1 MB request limits. AWS limits stored items to 400 KB. Server credentials never enter workflow fields.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• The optional recovery period is 1 to 35 days and applies only while enabling recovery. AWS reports the actual restorable interval separately.
• Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Enabling requires one stream view type. Disabling must omit the view type. AWS creates a new stream descriptor when stream settings change.
• The receipt confirms configuration acceptance, not that stream discovery is ready. Use Describe Table or List Streams before publishing a trigger.
• Changing or disabling a stream can interrupt consumers. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Supply at least one setting. The provider can return ACTIVE or UPDATING while the change propagates.
• Switching to provisioned billing requires both capacities. Existing provisioned tables can change both capacities without resubmitting billing mode. Switching to on-demand does not accept capacity values.
• Table-class and billing changes can affect pricing. Deletion protection prevents DeleteTable but does not prevent item writes. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• The change can take up to one hour. Expired items are deleted later on a best-effort basis and can remain visible meanwhile.
• Disabling TTL still requires the existing attribute name. Lost or malformed replies remain uncertain and are not resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• A successful call can process only part of the batch. Inspect complete and unprocessedCount. No automatic resend occurs. Lost or malformed write replies remain uncertain.
• At most 100 read keys or 25 writes across all tables. Requests are locally capped at 950 KB and replies at 1.9 MB, below AWS batch limits. Split larger batches. Put replaces an item; batch writes cannot use conditions or updates.
• Read results are unordered and missing items are omitted. Include primary keys in projections to associate returned items. Unprocessed read output preserves submitted projection and consistency options.
• AWS checks key schema, duplicate put/delete targets and native item size. Table identifiers with the same table name cannot share one batch. Credentials remain in the server vault.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

• Up to 100 actions; local request and response caps are 950 KB and 1.9 MB. AWS enforces native 4 MB transaction and 400 KB item limits. No two write actions may target one item.
• Put replaces an item; Update can create one. Use conditions to restrict writes. Atomic cancellation fails the operation. In-progress, lost or malformed write replies remain uncertain without automatic resend.
• An optional clientRequestId maps to AWS ClientRequestToken. Identical requests are idempotent for only ten minutes after first completion; reusing it later can repeat changes. Changed parameters within that window are refused by AWS.
• Ordered read response envelopes preserve missing and empty results. Condition failure item bodies are not requested or returned. Account credentials stay in the server vault.

A repeated request may repeat the external action. Review the previous result before retrying a write.