Krista Mae Rectra krectra

Amazon Web Services (AWS) & Google Cloud Platform (GCP) explained in simple English

This guide is only representative from my point of view and it may not be accurate and you should go on the official AWS & GCP websites for accurate and detailed information. It's initially inspired by AWS in simple English and GCP for AWS professionals. The idea is to compare both services, give simple one-line explanation and examples with other software that might have similiar capabilities. Comment below for suggestions.

Category	Service	AWS	GCP	Description	It's like
Compute	IaaS	Amazon Elastic Compute Cloud (EC2)	Google Compute Engine	Type-1 virtual servers	VMware ESXi, Citrix XenServer
	PaaS	AWS Elastic Beanstalk	Google App Engine	Running your app on a platform

This file contains links to online materials which I find useful for re-reading from time to time. I had started this initiative back in HP when created email list called Arete among my colleagues and spamming it with some useful materials on a regular basis. Since I left I wanted to continue sharing valuable content, here's why I have continued this here. Use the comments, to add more valuable stuff and never stop learning!

Bash academy - an initiative to promote and educate the bash shell language.

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

Does the design expect failures to happen regularly and handle them gracefully?
Have we kept things as simple as possible?

I like the idea of unifying navigation between tmux panes and vim windows. @mislav did a great job in [this gist][mislav-gist] but it depends on using C-{h,j,k,l} for navigation instead of vim's default C-W {h,j,k,l}.

Tmux's bind-key doesn't support multiple keys: just a single key with a modifier, so if we want to keep using C-w we have to be a bit tricky.

This approach binds C-w to set up keybindings that a) navigate and b) unset themselves. It turns out you can't have a bind-key statement in your .tmux.conf that's too long or tmux will segfault, which is one of the

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

I use tmux splits (panes). Inside one of these panes there's a Vim process, and it has its own splits (windows).

In Vim I have key bindings C-h/j/k/l set to switch windows in the given direction. (Vim default mappings for windows switching are the same, but prefixed with C-W.) I'd like to use the same keystrokes for switching tmux panes.

An extra goal that I've solved with a dirty hack is to toggle between last active panes with C-\.

Here's how it should work:

	#!/bin/bash
	# Nico Snyman, [email protected], 14/05/2015
	# Change an instance type, while keeping snapshots
	# This script will stop an instance identified by instance ID,
	# take snapshots of all atached volumes, and restart it
	# Use:
	# -i instance ID - REQUIRED - stored in instance_id
	# -t instance new instance type - REQUIRED - stored in instance_type
	# -s if set to 0, no snapshot will be taken, dafault is 1
	# (take snapshot of attached volumes) - stored in snapshot

	#!/bin/bash

	# Heavily adapted by Nico
	# Original script:
	# http://www.stardothosting.com/blog/2012/05/automated-amazon-ebs-snapshot-backup-script-with-7-day-retention/

	### ebs-snapshot.sh
	# Usage: $PROGNAME [OPTION] [Args]
	#Take snapshot of AWS volumes marked with a specific tag.
	#

	# Add init.d script to start at boot
	update-rc.d <init.d/name> defaults

	# Remove init.d from starting at boot
	update-rc.d -f <init.d/name> remove