npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@aws-mdaa/dataops-dynamodb

v1.3.0

Published

MDAA dataops-dynamodb module

Downloads

101

Readme

DynamoDB

The Data Ops DynamoDB CDK application is used to deploy the resources required to orchestrate data operations on the data lake (primarily Glue Crawlers, Glue Jobs, Step Functions and Lambdas).


Deployed Resources and Compliance Details

Mdaa Dynamodb Architecture

DynamoDB - DynamoDB tables will be created for each table specification in the configs

  • DynamoDB table configs can be handcrafted using the simple yaml files

Configuration

MDAA Config

Add the following snippet to your mdaa.yaml under the modules: section of a domain/env in order to use this module:

          dataops-dynamodb: # Module Name can be customized
            module_path: "@aws-mdaa/dataops-dynamodb" # Must match module NPM package name
            module_configs:
              - ./dataops-dynamodb.yaml # Filename/path can be customized

Module Config (./dataops-stepfunction.yaml)

Config Schema Docs

Sample DynamoDB Config

DynamoDB configs are stored under the ./dynamodb/ directory, relative to the dynamodb config. Multiple dynamodb tables can be defined in a single config file or across multiple files, as long as they have globally unique names.


# (Required) Name of the Data Ops Project
# Name the project the resources of which can be used by this dynamodb app.
# Other resources within the project can be referenced in the dynamodb config using
# the "project:" prefix on the config value.
projectName: dataops-project-sample
# List of dynamodb definitions
tableDefinitions:
  table-complex:
    # Partition key, required
    partitionKey:
      name: pk1
      type: S
    # Sort key, optional
    sortKey:
      name: sk1
      type: S
    # if PROVISIONED will need to indicate the read and write capacities
    billingMode: PROVISIONED
    # For an item up to 4 KB, one read capacity unit (RCU) represents one strongly consistent read operation per second, or two eventually consistent read operations per second
    readCapacity: 2
    # A write capacity unit (WCU) represents one write per second for an item up to 1 KB
    writeCapacity: 1
    # a specific attribute to store the TTL expiration timestamp, see https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html
    timeToLiveAttribute: ttl
  table-simple:
    # Partition key, required
    partitionKey:
      name: pk1
      type: S
    # if PAY_PER_REQUEST don't indicate read/write capacity
    billingMode: PAY_PER_REQUEST