MattHealy

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.

---

Index:

MattHealy

If you use Amazon AWS for nearly anything, then you are probably familiar with KMS, the Amazon Key Management Service.

KMS is a service which allows API-level access to cryptographic primitives without the expense and complexity of a full-fledged HSM or CloudHSM implementation. There are trade-offs in that the key material does reside on servers rather than tamper-proof devices, but these risks should be acceptable to a wide range of customers based on the care Amazon has put into the product. You should perform your own diligence on whether KMS is appropriate for your environment. If the security profile is not adequate, you should consider a stronger product such as CloudHSM or managing your own HSM solutions.

The goal here is to provide some introductory code on how to perform envelope encrypt a message using the AWS KMS API.

KMS allows you to encrypt messages of up to 4kb in size directly using the encrypt()/decrypt() API. To exceed these limitations, you must use a technique called "envelope encryptio

MattHealy

sub AmazonSignURL() {

   my ($url,$expiresin,$key,$secret) = @_;

   use Digest::SHA qw(hmac_sha1_base64);
   use URI::Escape;

   my $expires = time() + $expiresin;

   my $path = $url;

MattHealy

#!/usr/bin/env python

#remove public read right for all keys within a directory

#usage: remove_public.py bucketName folderName

import sys
import boto

from boto import connect_s3

MattHealy

#!/usr/bin/env python
import json
import redis

keys = []

r = redis.StrictRedis(host = 'localhost')
for key in r.keys():
    keys.append(key)

MattHealy

#!/usr/bin/env python

# set SSE on all existing objects

#usage: encrypt_all_objects.py bucketname

import sys
import boto

from boto import connect_s3

MattHealy

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.

MattHealy

#!/bin/bash

oldconfigname="$1"
newconfigname="$2"
ami="$3"

KEYNAME="my_keypair_name"
ASGROUP="my_autoscaling_group_name"
SECURITYGROUP="sg-1234"
INSTANCETYPE="t2.micro"

MattHealy

# This file is:  ~/.ssh/config

# You may have other (non-CodeCommit) SSH credentials stored in this
# config file – in addition to the CodeCommit settings shown below.

# NOTE: Make sure to run [ chmod 600 ~/.ssh/config ] after creating this file!

# Credentials for Account1
Host awscc-account1                                 # 'awscc-account1' is a name you pick
  Hostname git-codecommit.us-east-1.amazonaws.com   # This points to CodeCommit in the 'US East' region

MattHealy

switch() {
    export AWS_DEFAULT_PROFILE=$1
    PS1="\h:\W \u\$ ($1)$ "
}