aws-simple

set et " expandtab
set ts=2 " tabstop
set sw=2 " shiftwidth
set sts=2 " softtabstop
set hls " highlightsearch
set ic " ignorecase
set nu " numbers

colorscheme desert
set bg=dark

aws-simple

alias a='ansible'
alias b='brew'
alias d='docker'
alias f='find'
alias g='git'
alias h='helm'
alias j='journalctl'
alias k='kubectl'
alias m='make'
alias o='openssl'

aws-simple

What if we use Ingress-Nginx Controller and would like to look through logs of its Pods to get specific details on the passing traffic

• According to Ingress-Nginx Controller documentation the default configuration uses a custom logging format

log_format upstreaminfo
    '$remote_addr - $remote_user [$time_local] "$request" '
    '$status $body_bytes_sent "$http_referer" "$http_user_agent" '
    '$request_length $request_time [$proxy_upstream_name] [$proxy_alternative_upstream_name] $upstream_addr '
    '$upstream_response_length $upstream_response_time $upstream_status $req_id';

aws-simple

What if we have a certain nodegroup (for example EKS Node Group) and would like to see which applications load their node mostly

• Let's say we have node group labeled as purpose=workers and would like to see top pod sorted by cpu usage

LABELS='purpose=workers'
kubectl top pods --no-headers -A --sort-by=cpu | \
  grep -f <(kubectl get pod -A --no-headers -o wide | \
  grep -f <(kubectl get nodes -l ${LABELS} -oname | sed -e 's|^node/||') | awk '{print $2}')

aws-simple

This document provides instructions on how to use the following tools to manage access to AWS on macOS/Linux engineer's workplace

• GnuPG
• AWS vault
• pass password manager
• pass OTP extension

Note

The storage of the first factor authenticatiton (credentials keys) and the source for the second factor (OTP key, which is used to generate OTP codes) in the same vault (even encrypted) runs against security best practices. It is recommended that you use a dedicated MFA device to generate OTP codes. The instructions provided in the document show how all the mentioned tools can interact and help understand how to manage these and/or other tools according to security best practices

aws-simple

### Using the following aliases provides possibilities to use variables both
###   for backend initialization ('terraform init') and for other operations
###   ('terraform plan/apply/...') by applying so called 'partial configuration'.
### The alias 'tf' runs 'terraform' command with all passed arguments and
###   additional flag (either '-backend-config=...' or '-var-file=...') with
###   path to 'backend.hcl' file (containing terraform variables) which 
###   depends on:
###     - a current directory (the directory where 'terraform' command was called)
###     - whether the command was called within a 'git' repo
###     - a location of 'backend.hcl' file in the 'git' repo directory structure