thapakazi

1. create sns topic

2. Under Amazon SNS > Text messaging (SMS) 

Add your phone number and verify it with otp.

reason:
by default SMS is in sandbox mode: https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html
Need to create a support ticket to "Exit SMS Sandbox" :weird: which only allows us to send sms on verified number.

thapakazi

#!/bin/bash

set -e
stderr_log="/tmp/stderr.log"
exec 2>"$stderr_log"

notify() {
    local exit_code=$?
    local lineno=$1
    if ! [ $exit_code -eq 0 ]; then

thapakazi

#!/bin/bash

export AWS_PROFILE=nonproduction
export AWS_REGION=us-east-1

source_env=staging
dest_env=testing

SECRETS_DIR=/tmp/secrets && mkdir -p $SECRETS_DIR
SECRETS_ALL=$SECRETS_DIR/secrets.json

thapakazi

apiVersion: v2
name: secret-app
description: A Helm chart for Kubernetes

type: application
version: 0.1.0
appVersion: "0.1.0"

thapakazi

Keybase proof

I hereby claim:

• I am thapakazi on github.
• I am thapakazi (https://keybase.io/thapakazi) on keybase.
• I have a public key whose fingerprint is D960 A6D6 BEC6 E198 1393 BFAB 00F2 8320 44FF 5DE8

To claim this, I am signing this object:

thapakazi

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h or --help depending on your psql version):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

thapakazi

• enable pod eni: https://github.com/aws/amazon-vpc-cni-k8s#enable_pod_eni-v170

kubectl -n kube-system set env daemonset aws-node ENABLE_POD_ENI=true

• for healthcheck set, DISABLE_TCP_EARLY_DEMUX=true for init container https://github.com/aws/amazon-vpc-cni-k8s#disable_tcp_early_demux-v173

thapakazi

resource "tls_private_key" "ca" {
  algorithm = "RSA"
}

resource "tls_self_signed_cert" "ca" {
  key_algorithm   = "RSA"
  private_key_pem = "${tls_private_key.ca.private_key_pem}"

  subject {
    common_name  = "${var.domain}"

thapakazi

Session Manager - Simplified

• Alternative login to your ec2 instances via session manager
  • Make sure you are using vm with session manager installed
  • Your instance is attached with a iam role that has following policy attached:
    • policy_arn = “arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore”

thapakazi

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "iam:CreatePolicy",
                "iam:CreateRole",
                "iam:AttachRolePolicy"