ffjia

AWS CLI command to update CNAME

When you have a set of application servers running in EC2 in an active/passive configuration, the easiest way to failover is to simply update the DNS to point to the second server as soon as it's available to serve requests. If you are using Route 53 to manage your DNS configuration, with the AWS CLI you can make this change in a single command.

Initial Setup

• Install the AWS CLI
• Login with an account that has an IAM Policy that gives it access to the Route53 Service
• Get the HostedZoneID for the domain you want to update from the AWS console here: https://console.aws.amazon.com/route53/home#hosted-zones:

The CLI expects the change to be submitted via a JSON-formatted configuration file. I've inclu

ffjia

#!/usr/bin/env bash

set -o errexit
set -o nounset
set -o pipefail

IAM_GROUP=${1:-admins}
EKS_ROLE_ARN=${2:-arn:aws:iam::111122223333:role/eks-node-role}
RBAC_GROUP=${3:-system:masters}

ffjia

wget http://stedolan.github.io/jq/download/linux64/jq 
aws ec2 describe-instances --filters "Name=tag:Name,Values=$NAME" \
  "Name=instance-state-name,Values=running" \
  |  jq -r \
  ".Reservations[] | .Instances[] | .InstanceId" \

aws ec2 describe-volumes --filters \
  "Name=status,Values=available" \
  | jq -r ".Volumes[] | .VolumeId" \

ffjia

How to setup AWS lambda function to talk to the internet and VPC

I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.

So it might be really unintuitive at first but lambda functions have three states.

1. No VPC, where it can talk openly to the web, but can't talk to any of your AWS services.
2. VPC, the default setting where the lambda function can talk to your AWS services but can't talk to the web.
3. VPC with NAT, The best of both worlds, AWS services and web.

ffjia

daemon off;

worker_processes 1;

events { worker_connections 1024; }

http{

sendfile on;

ffjia

set -e

# Stop the docker daemon
/etc/init.d/docker stop

# Configure ECS Agent
# http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html
# http://docs.aws.amazon.com/AmazonECS/latest/developerguide/automated_image_cleanup.html
cat > /etc/ecs/ecs.config << "EOF"
ECS_ENGINE_TASK_CLEANUP_WAIT_DURATION=1h

ffjia

<div>Execution ${execution.id} was <b>${execution.status}</b></div>
<ul>
    <li><a href="${execution.href}">Execution result</a></li>
    <li><a href="${job.href}">Job</a></li>
    <li><a href="${execution.projectHref}">Project: ${execution.project}</a></li>
    <li><a href="${rundeck.href}">Rundeck</a></li>
</ul>
<p>

</p>

ffjia

git branch -m old_branch new_branch         # Rename branch locally    
git push origin :old_branch                 # Delete the old branch    
git push --set-upstream origin new_branch   # Push the new branch, set local branch to track the new remote

ffjia

server {
  server_name  img.l;
  root            /var/www/cache/store/ns365;
  index           index.html;

  # This requests the original file from itself and then resizes the image.
  location ~ /resize/(\d+)x(\d+)/(.*) {
    proxy_pass                  http://img.l/$3;
    image_filter                resize $1 $2;
    image_filter_jpeg_quality   90;

ffjia

#!/bin/sh
# redis-notify.sh

MAIL_FROM="notify@example.net"
MAIL_TO="alert@example.net"

if [ "$#" = "2" ]; then
    mail_subject="Redis Notification"
    mail_body=`cat << EOB
============================================