SteveMarshall

Notes of Scale Summit 2015 what's changed since last year.

Things last year:
- “Big Data is a thing”; Big Data is now pointless
- “Is CouchDB dead?” npm were? Fairly sure couchdb is now dead, despite more funding
- Under still going: Mongo, Riak. Mongo's not dead? Guardian, GDS, MOJ. Mongo on the rise again? Mongo *might* be dead; we don't know.
- Websockets were "standard" but weren't really… except for certain browsers, proxies, etc.
- HTML5 video still doesn't really work
- Flash is still dying… Unless you count CVEs. Lots of flash-based ads.
- WebGL has taken hold? Still true, apparently.

ripienaar

  ["update-puppet.sh", "run-puppet.sh"].each |$file| {
    file{"/usr/local/bin/${file}":
      owner  => "root",
      group  => "root",
      mode   => "0700",
      source => "puppet:///modules/puppet/${file}"
    }
  }

ripienaar

create_resources("mail::domain", $domains)

lemonhall

Backend Architectures

Twitter

ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats

• Scaling Twitter: Making Twitter 10000 Percent Faster
• Scaling Twitter
• Blaine Cook on Scaling Twitter - YouTube

cktricky

#!/usr/bin/env ruby

require 'aws-sdk'

sts = Aws::STS::Client.new(
  region: 'us-east-1',
  access_key_id: "<insert access key id>",
  secret_access_key: "<secret>"
)

aaronjensen

#!/usr/bin/env ruby
Dir.chdir File.join(__FILE__, "../..")

unless ENV['EDITOR']
  puts "No EDITOR found. Try:"
  puts "export EDITOR=vim"
  exit 1
end

unless ARGV.count == 2

agussman

External Resources

• linuxacademy.com (Training)
• Acloud.guru (training)
• Read the top-level Documentation and FAQs for all the major AWS resources (EC2, S3, RDS, Auto Scaling, etc). The answers to the "nit-picky" questions can be found here. It's also helpful to go deeper on VPCs and networking-related concepts.
  • VPC http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html
  • VPC Security http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Security.html
  • VPC Route Tables http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Route_Tables.html
• Everyone says read the white papers. The ones I read were:
  • Security Best Practices https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf
• Cloud Best Practices https://d0.awsstatic.com/whitepapers/AWS_Cloud_Best_Practices.pdf

gene1wood

#!/usr/bin/python

# Source : https://s3.amazonaws.com/awsiammedia/public/sample/SAMLAPICLIADFS/samlapi_formauth.py
# Referenced from : https://aws.amazon.com/blogs/security/how-to-implement-a-general-solution-for-federated-apicli-access-using-saml-2-0/

import sys
import boto.sts
import boto.s3
import requests
import getpass

gene1wood

import boto3

def role_arn_to_session(**args):
    """
    Usage :
        session = role_arn_to_session(
            RoleArn='arn:aws:iam::012345678901:role/example-role',
            RoleSessionName='ExampleSessionName')
        client = session.client('sqs')
    """

jareware

⇐ back to the gist-blog at jrw.fi

Simple, semi-anonymous backups with S3 and curl

Backing stuff up is a bit of a hassle, to set up and to maintain. While full-blown backup suites such as duplicity or CrashPlan will do all kinds of clever things for you (and I'd recommend either for more complex setups), sometimes you just want to put that daily database dump somewhere off-site and be done with it. This is what I've done, with an Amazon S3 bucket and curl. Hold onto your hats, there's some Bucket Policy acrobatics ahead.

There's also a tl;dr at the very end if you just want the delicious copy-pasta.

Bucket setup