Steve Coffman StevenACoffman

kubectl -n kube-system create sa tiller
kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
helm init --service-account tiller

You can use CodePipeline and CodeBuild to create a continuous deployment/integration pipeline for serverless applications build on AWS Lambda and Amazon API Gateway. This sample application is written in Go with the Gin framework and uses the eawsy API Gateway proxy shim: https://github.com/eawsy/aws-lambda-go-net

We initially detailed our methodology in this blog post: https://aws.amazon.com/blogs/compute/continuous-deployment-for-serverless-applications/

We have used the shim technology created by eawsy to run Golang applications inside AWS Lambda (https://github.com/eawsy/aws-lambda-go-shim) and created a container that can be used with CodeBuild as part of our original pipeline template.

The container is available on DockerHub and is called sapessi/aws-lambda-go18-codebuild:latest. To use this container, simply change the Image property of the CodeBuild project environment.

The pipeline template, sample app, buildspec and SAM files are attached to this gist.

	func genStruct() gopter.Gen {
	return genStrucType().FlatMap(
	func(arg interface{}) gopter.Gen {
	// typ := arg.(reflect.Type)
	// Q: How to construct a generator?
	return nil
	},
	reflect.TypeOf((interface{})(nil)),
	)
	}


	event_name="ConsoleLogin"
	aws cloudtrail lookup-events --lookup-attributes \
	AttributeKey=EventName,AttributeValue=$event_name --query \
	'Events[*].{Ev:CloudTrailEvent,User:Username}' \|
	jq '.[]\| "Username: " + .User, " " + (.Ev\| fromjson \| "EventTime: " + .eventTime, "SourceIP: " + .sourceIPAddress) '

	for event_name in AuthorizeSecurityGroupEgress AuthorizeSecurityGroupIngress CreatePolicy \
	CreateSecurityGroup DeleteTrail ModifyVpcAttribute PutUserPolicy PutRolePolicy \
	RevokeSecurityGroupEgress RevokeSecurityGroupIngress UpdateTrail; do

	{
	"Version": "2012-10-17",
	"Statement": [
	{
	"Effect": "Allow",
	"Action": [
	"ec2:AttachVolume",
	"ec2:AuthorizeSecurityGroupIngress",
	"ec2:CreateTags",
	"ec2:CreateVolume",

	#!/bin/bash
	rm /tmp/image-pull-secret.yaml
	login_cmd=$(aws ecr get-login)
	username=$(echo $login_cmd \| cut -d " " -f 4)
	password=$(echo $login_cmd \| cut -d " " -f 6)
	endpoint=$(echo $login_cmd \| cut -d " " -f 9)
	auth=$(echo "$username:$password" \| /usr/bin/base64)

	configjson="{ \"auths\": { \"${endpoint}\": { \"auth\": \"${auth}\" } } }"

	image: docker.mydomain.com/build/kube-go-make

	variables:
	DOCKER_TAG: docker.mydomain.com/myapp/home:$CI_COMMIT_REF_SLUG
	DOCKER_HOST: tcp://localhost:2375
	DOCKER_DRIVER: overlay
	PROD_RSYNC_HOST: myprodserver.com
	DOMAIN: mydomain.com
	CHART_DIR: chart

	minikube start --kubernetes-version=v1.7.0 --extra-config=apiserver.Authorization.Mode=RBAC

	kubectl create clusterrolebinding add-on-cluster-admin --clusterrole=cluster-admin --serviceaccount=kube-system:default

	minikube dashboard

	const http = require('http');
	const https = require('https');

	var webhookURLs = {
	// Every minute
	'* * * * *': [
	'http://requestb.in/testing-here'
	],

	// Every half hour

	{
	AWSEBDockerrunVersion: "1",
	Authentication: {
	Bucket: "staffjoy-deploy",
	Key: "docker.cfg"
	},
	Image: {
	Name: "staffjoy/app:TAG",
	Update: "true"
	},