A simple, straightforward way export and import AWS DynamoDB table’s data with AWS CLI and a few scripts.

At first, export all the data from AWS DynamoDB table:

1

𝜆 aws --profile production dynamodb scan --table-name tile-event > tile-event-export.json

Convert a list of items/records (DynamoDB JSON) into individual PutRequest JSON with jq.

1

𝜆 cat tile-event-export.json | jq '{"Items": [.Items[] | {PutRequest: {Item: .}}]}' > tile-event-import.json

Transform the data if necessary:

1

𝜆 sed 's/tile-images-prod/tile-images-pdev/g' tile-event-import.json > tile-event-import-transformed.json

Split all requests into 25 requests per file, with jq and awk (Note: There are some restriction with AWS DynamoDB batch-write-item request - The BatchWriteItem operation can contain up to 25 individual PutItem and DeleteItem requests and can write up to 16 MB of data. The maximum size of an individual item is 400 KB.)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

𝜆 cat tile-event-processed.awk
#!/usr/bin/awk -f

NR%25==1 {
  x="tile-event-import-processed-"++i".json";
  print "{" > x
  print "  \"tile-event\": [" > x
}
{
  printf "    %s", $0 > x;
}
NR%25!=0 {
  print "," > x
}
NR%25==0 {
  print "" > x
  print "  ]" > x
  print "}" > x
}

𝜆 jq -c '.Items[]' tile-event-import-transformed.json | ./tile-event-processed.awk

Import all 22 processed JSON files into DynamoDB table:

1
2
3
4

$ for f in tile-event-import-processed-{1..22}.json; do \
    echo $f; \
    aws --profile development dynamodb batch-write-item --request-items file://$f; \
  done

For all the people painfully read logs on AWS CloudWatch console, saw is your friend.

Get CloudWatch log groups start with paradise-api:

1
2

𝜆 saw groups --profile ap-prod --prefix paradise-api
paradise-api-CloudFormationLogs-mwwmzgYOtbcB

Get last 2 hours logs for paradise-api from CloudWatch, with saw:

1

𝜆 saw get --profile ap-prod --start -2h paradise-api-CloudFormationLogs-mwwmzgYOtbcB --prefix docker | jq .log | sed 's/\\\n"$//; s/^"//'

AWS EC2 instance CloudFormation templates in Public Tier and App Tier:

When try to get the content of any /proc/PID/environ file in more readable format, you can:

1
2
3
4

/proc/[pid]/environ
      This file contains the environment for the process.  The entries
      are separated by null bytes ('\0'), and there may be a null byte
      at the end.

A simple way is to apply xargs -0 -L1 -a on it:

• -0 - read null-delimited lines,
• -L1 - read one line per execution of command
• -a - file read lines from file

1
2
3
4
5
6
7
8
9
10
11
12
13

# ps -aef
10101     3629  3589  0 Apr27 ?        00:00:00 /bin/bash bin/start
10101     3670  3629  0 Apr27 ?        00:00:00 /bin/bash bin/start-tomcat
10101     3671  3670  0 Apr27 ?        00:07:36 /usr/lib/jvm/java-11-amazon-corretto.x86_64/bin/java -Djava.util.logging.config.file=/usr/local/tomcat/conf/

# cat /proc/3629/environ
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binHOSTNAME=27c44e8a5c7cJAVA_HOME=/usr/lib/jvm/java-11-amazon-corretto.x86_64HOME=/usr/local/tomcat

# xargs -0 -L1 -a /proc/3629/environ
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=27c44e8a5c7c
JAVA_HOME=/usr/lib/jvm/java-11-amazon-corretto.x86_64
HOME=/usr/local/tomcat

With AWS CLI version 2:

1
2

𝜆 aws --version
aws-cli/2.1.17 Python/3.7.4 Darwin/20.3.0 exe/x86_64 prompt/off

Encrypt with AWS KMS key:

1
2
3
4
5
6
7

𝜆 aws kms encrypt --profile personal \
  --key-id e2695b79-cbe0-4c16-aa5e-b7dbf52df1f9 \
  --plaintext "string-to-encrypt" \
  --output text \
  --query CiphertextBlob \
  --cli-binary-format raw-in-base64-out
AQICAHjbJrIPgME ... lILuBSUdA==

Decrypt with AWS KMS key:

1
2
3
4
5

𝜆 echo "AQICAHjbJrIPgME ... lILuBSUdA==" | base64 -D | \
  aws kms decrypt --profile personal \
  --ciphertext-blob fileb:///dev/stdin \
  --output text \
  --query Plaintext | base64 -D

Reference

• cli_binary_format, https://docs.aws.amazon.com/credref/latest/refdocs/setting-global-cli_binary_format.html

RAD (Rapid Application Development) of a Serverless application “Notification Service” on modern technologies, e.g. AWS CDK & SAM, AWS Step Functions, TypeScript, VS Code, Open API Top Down Design and Test Driven Development, in order to rapidly build a prototype, or a POC, verify and test some technologies and approaches.

Request Handler => Step Functions (orchestration for Lambda functions, represents a single centralized executable business process, outsources low level operations like retry / exception catch and handle. Another choice is SNS) => Service Providers

Have experienced of Terraform, Serverless, AWS SAM … now this time based on code over configuration principle, what you get is flexibility, predictability and more control. You focus on code you tell the tools what steps it has to complete directly. At the end of day, it is a simple matter of separation of concerns and single responsibility principle.

• VS Code for API Spec editing

• Postman API, Environment and Mock server, for QA team, then switch to real service in DEV/TEST environment

1

𝜆 npm run openapi

• openapi-generator generates model classes; typescript-json-validator generates JSON Schema and validator

1
2

𝜆 openapi-generator generate -g typescript-node -i Notification\ API\ openapi.json -o Notification\ API\ generated
𝜆 npx typescript-json-validator notificationRequest.ts NotificationRequest

• Onboard on Kong / API Manager, https://konghq.com/kong/

• CDK, is based on CloudFormation but abstract layer on the top of it. It can generates CloudFormation template file template.yaml

1

𝜆 cdk synth --no-staging > template.yaml

• Demo of local run and debug lambda, with background TSC watch process

1
2
3
4

𝜆 npm run watch

𝜆 sam local invoke RequestNotification9F9F3C31 -e samples/api-gateway-notification-event.json
𝜆 sam local invoke RequestNotification9F9F3C31 -e samples/api-gateway-notification-event.json -d 5858

Data validation to make data integrity unbreachable will take a lot time.

ajv framework and performance benchmark, https://github.com/ebdrup/json-schema-benchmark

• Code lint with eslint and prettier and automatically correction

• Code commit rule enforcement

• Change code and deploy AWS stack by CDK

1

𝜆 cdk deploy --require-approval never --profile dev-cicd

• Behavior Driven Test Framework Jest, https://github.com/facebook/jest, 2x / 3x faster than Karma, with code coverage, easy mocking

1

𝜆 npm t

• Automatically generate application changelog and release notes

1

𝜆 npm run release:minor

• Automatically generate application document

1

𝜆 npm run docs

• AWS resources created by CDK

• Not Mono Repo app, which multiple projects all under one giant Repo

• ONE AWS Layers put all dependent NPM libs and shared code into; size of Lambda functions, readability

• AWS EventBridge tro trigger and send event to Request Handler, for scheduling task

• Health Check, with Service Monitoring Dashboard, verify dependencies at the endpoints, keep Lambda warming up

1

𝜆 curl https://c81234xdae8w1a9.execute-api.ap-southeast-2.amazonaws.com/health

Cloud computing and Serverless architecture let developers in fast lane for Application Development. Right now, there are so many low hanging fruit to pick up.

As developers, we should not always think about our comfort zone, we need to think about people who take over your work, think about BAU team to support the application. The codebase is not about you, but about the value that your code brings to others, and the organization that you work for.

Fix our destructive and throwaway economy, save our planet by making products both repairable, durable, environmentally friendly, and by defending our Right to Repair.

This is my second video created and composed by Apple Final Cut Pro X - Why Repairable Is Important https://www.youtube.com/watch?v=qSmFI6J7eRo

My first published video, created by Apple Final Cut Pro, on YouTube for official channel title Bring back MagSafe regard to solution that bring one of the most innovative design from Apple, back to MacBook Pro, iPad … and Android phones https://www.youtube.com/watch?v=yvkJR4Y0FK0

• WSKEN SHARK X4 TYPE-C TO TYPE-C PD 100W QUICK CHARGE MAGNETIC CABLE: http://wsken.my/WSKEN-Shark-X4-Type-C-To-Type-C-PD-100W-Quick-Charge-Magnetic-Cable

• WSKEN SHARK X5 TYPE-C 5A QUICK CHARGE MAGNETIC CABLE: http://wsken.my/WSKEN-Shark-X5-Type-C-5A-Quick-Charge-Magnetic-Cable

• WSKEN Official Store on AliExpress: https://www.aliexpress.com/store/3018058

Consider a full development and deployment cycle, and the potential risks involved during the different stages in CDP (CI / Continuous Integration, CD / Continuous Delivery, CDP / Continuous Deployment):

• Code

• Commit

• Test

• Deployment

• Runtime

AWS CloudWatch Metrics

The interface of Metrics in AWS CloudWatch console:

The URL:

1

https://ap-southeast-2.console.aws.amazon.com/cloudwatch/home?region=ap-southeast-2#metricsV2:graph=~(metrics~(~(~'AWS*2fRoute53Resolver~'InboundQueryVolume)~(~'.~'OutboundQueryVolume))~view~'timeSeries~stacked~false~region~'ap-southeast-2~stat~'Sum~period~86400~start~'-P28D~end~'P0D);query=~'*7bAWS*2fRoute53Resolver*7d

Metrics source:

1
2
3
4
5
6
7
8
9
10
11
12

{
    "metrics": [
        [ "AWS/Route53Resolver", "InboundQueryVolume" ],
        [ ".", "OutboundQueryVolume" ]
    ],
    "view": "timeSeries",
    "stacked": false,
    "region": "ap-southeast-2",
    "stat": "Sum",
    "period": 86400,
    "title": "Test"
}