|AWS region code||AWS region name||Number of AZs||AZ names|
|us-east-1||Virginia||4||us-east-1a, us-east-1b, us-east-1c, us-east-1e|
|us-west-1||N. California||2||us-west-1a, us-west-1b|
|us-west-2||Oregon||3||us-west-2a, us-west-2b, us-west-2c|
|eu-west-1||Ireland||3||eu-west-1a, eu-west-1b, eu-west-1c|
|ap-southeast-2||Sydney||2||ap-southeast-2a, ap-southeast-2b, ap-southeast-2c|
|# most credit to the original: https://gist.github.com/brandond/6b4d22eaefbd66895f230f68f27ee586|
|# Tag snapshots based on their associated AMI and volumes based on attached instance.|
|# (AMI:db5|db5) /dev/sda1 (1/4)|
|# (AMI:db5|db5) /dev/sdb (2/4)|
|# Best practice: create IAM user|
|# Simplest privilege to get it to work with reasonable security: use predefined policy "ReadOnlyAccess"|
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
vagrant from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
Creating a VM
vagrant init-- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
vagrant init <boxpath>-- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example,
vagrant init ubuntu/trusty64.
Starting a VM
vagrant up-- starts vagrant environment (also provisions only on the FIRST vagrant up)
Resize a Hard Disk for a Virtual Machine
Our Virtual Machines are provisioned using Vagrant from a Linux base box to run using VirutalBox. If the Hard Disk space runs out and you cannot remove files to free-up space, you can resize the Hard Disk using some VirtualBox and Linux commands.
The following steps assume you've got a set-up like mine, where:
|# Reference: https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/|
|# GitLab uses docker in the background, so we need to specify the|
|# image versions. This is useful because we're freely to use|
|# multiple node versions to work with it. They come from the docker|
|# Uses NodeJS V 9.4.0|
|# And to cache them as well.|