AWS DynamoDB Construct Library
Here is a minimal deployable DynamoDB table definition:
import dynamodb = require('@aws-cdk/aws-dynamodb');
const table = new dynamodb.Table(this, 'Table', {
partitionKey: { name: 'id', type: dynamodb.AttributeType.String }
});
Keys
When a table is defined, you must define it's schema using the partitionKey
(required) and sortKey (optional) properties.
Billing Mode
DynamoDB supports two billing modes:
- PROVISIONED - the default mode where the table and global secondary indexes have configured read and write capacity.
- PAY_PER_REQUEST - on-demand pricing and scaling. You only pay for what you use and there is no read and write capacity for the table or its global secondary indexes.
import dynamodb = require('@aws-cdk/aws-dynamodb');
const table = new dynamodb.Table(this, 'Table', {
partitionKey: { name: 'id', type: dynamodb.AttributeType.String },
billingMode: dynamodb.BillingMode.PayPerRequest
});
Further reading: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.
Configure AutoScaling for your table
You can have DynamoDB automatically raise and lower the read and write capacities of your table by setting up autoscaling. You can use this to either keep your tables at a desired utilization level, or by scaling up and down at preconfigured times of the day:
Auto-scaling is only relevant for tables with the billing mode, PROVISIONED.
const readScaling = table.autoScaleReadCapacity({ minCapacity: 1, maxCapacity: 50 });
readScaling.scaleOnUtilization({
targetUtilizationPercent: 50
});
readScaling.scaleOnSchedule('ScaleUpInTheMorning', {
schedule: appscaling.Cron.dailyUtc(8),
minCapacity: 20,
});
readScaling.scaleOnSchedule('ScaleDownAtNight', {
schedule: appscaling.Cron.dailyUtc(20),
maxCapacity: 20
});
Further reading: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/AutoScaling.html https://aws.amazon.com/blogs/database/how-to-use-aws-cloudformation-to-configure-auto-scaling-for-amazon-dynamodb-tables-and-indexes/
2 maintainers
Metadata
2 maintainers
Release files for aws-cdk.aws-dynamodb 0.27.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws-cdk.aws-dynamodb-0.27.0.tar.gz | 85.1 kB | Without provenance | Details for aws-cdk.aws-dynamodb-0.27.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk.aws_dynamodb-0.27.0-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk.aws_dynamodb-0.27.0-py3-none-any.whl |
Total release size: 168.5 kB
Release files / aws-cdk.aws-dynamodb-0.27.0.tar.gz
| Download URL | aws-cdk.aws-dynamodb-0.27.0.tar.gz |
|---|---|
| Size | 85.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e85467c650673fb64a615caf54719d2936a58928d2fee5a9dffaeee15a0565ea
|
|
BLAKE2b-256 checksum How to use checksums |
f2d4fc0ef35dd2294704920d62dd7d46e552d371afcc25c25c0d0efd4607d6ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Release files / aws_cdk.aws_dynamodb-0.27.0-py3-none-any.whl
| Download URL | aws_cdk.aws_dynamodb-0.27.0-py3-none-any.whl |
|---|---|
| Size | 83.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4ca22cc13788c8adba4c2428a3238960eb1d4c262f373c18c356ab073d98433
|
|
BLAKE2b-256 checksum How to use checksums |
9d6dd2a6b16959ede2c63629ec213d21fb2e5518e01e185696b725865ad6d6e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.5
|
Security for aws-cdk.aws-dynamodb 0.27.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
