Shield provides DDOS protection and WAF is a Layer 7 Application Firewall.

Ref: https://www.cloudflare.com/en-au/learning/ddos/what-is-a-ddos-attack/

We can use CDK to create AWS WAF with the expected rules and associate it to the ALB

What’s In This Document

• Init WAF CDK Project
• Write code stack
• Deploy stacks

🚀 Init WAF CDK Project

⚡ $ mkdir waf_alb
⚡ $ cd waf_alb
⚡ $ cdk init -l python

🚀 Write code stack

• At RuleProperty, we set OverrideActionProperty to count so that if a rule matches a web request, it only counts the match.
• To defines and enables Amazon CloudWatch…

- Once we’ve found the problem in the worker, fixed the bug and deployed a new version, we want to send all the messages from the DLQ back to the original input queue, so they can be processed by the updated worker. There’s no way to do this in SQS directly, so we’ve written a script to do it for us.

- The automation script moves SQS messages between queues with proper way to avoid impact to other services which using the same queue. This post also provides CDK code to create SQS queues to test and the python script to generate a bunch of messages.

- CDK helps to create this project by coding (python language), What’s its benefits?

+ Infra structure as code

+ Update lambda function code and just need to execute cdk deploy, all the code and modules will be up-to-date

+ Create and destroy the structure quickly, and we can manage the structure by separate stacks such dynamodb stack, IAM stack, lambda stack and API Gateway stack.

What’s In This Document

• Write the code
• Run example

🚀 Write the code

add_key.sh

#!/usr/bin/expect

set access_key [lindex $argv 0]
set screte_key [lindex $argv 1]

spawn aws configure

# Add access key
expect "]:"
send "$access_key\r"

# Add secrete key
expect "]:"
send "$screte_key\r"

# Default region
expect "]:"
send "\r"

# Default output format
expect "]:"
send "\r"

interact

🚀 Run example

⚡ $ ./add_key.sh a1234a b4567b
spawn aws configure
AWS Access Key ID [****************XXXX]: a1234a
AWS Secret Access Key [****************YYYY]: b4567b
Default region name [ap-northeast-2]: 
Default output format [None]: 

⚡ $ aws configure list
      Name                    Value             Type    Location
      ----                    -----             ----    --------
   profile                <not set>             None    None
access_key     ****************234a shared-credentials-file    
secret_key     ****************567b shared-credentials-file    
    region           ap-northeast-2      config-file    ~/.aws/config

🌠 Blog · Web · Linkedin · Group · Page · Twitter 🌠

Any commits should be tagged align with build version especially master branch. How to configure Gitlab runner to do this?

What’s In This Document

• What is the usecase
• Solve problem by using OAUTH2.0 and tokens

🚀 What is the usecase

• Developer tells gitlab runner to tag the commit and publish the tag .gitlab-ci.yml

build:
  stage: build
  script:
    - echo "Build and tag the commit"
    - tag=1.0-${CI_COMMIT_SHORT_SHA}
    - git tag $tag
    - git push origin $tag
  tags:
    - gitlab-runner

• But…

- With RDS you don’t edit config files directly. Instead edit the parameters through the RDS console, or via the API.

- As of now, RDS does allow changing configurations. So you can

• See the list of configurations that your RDS is using.
• You can change these parameters. You can change those that are listed in the RDS reference page.

- This post give an example of change wal_level from replica to logical

What’s In This Document

• General RDS configruation
• Change RDS configruation
• Check wal_level

🚀 General RDS configruation

What’s In This Document

• Create access token
• Get project ID to call API
• Get raw file from repository

🚀 Create access token

• Go to User Setttings -> Access Tokens

Quick start aws-chalice

A very simple example of creating lambda function with cloudwatch event using aws-chalice. It provides an optional of how to create lambda function beyond aws-cdk (eg. python lamdbda cron)

What’s In This Document

• Create new chalice project
• Create the functions in app.py
• Config lambda fuction attributes
• Deploy chalice to create cloudwatch event which trigger lambda cron
• Check result
• Clean up

🚀 Create new chalice project

⚡ $ chalice new-project lambda-cron
⚡ $ cd lambda-cron/

🚀 Create the functions in app.py

app,py

from datetime import datetime
from chalice import Chalice


app = Chalice(app_name='lambda-cron')
app.debug = True


#@app.schedule('cron(0 18 …