setup aws cli in bootstrap

Author: Graham Krizek

.aws/config

@@ -0,0 +1 @@
+[default]

.aws/credentials

@@ -0,0 +1 @@
+[default]

bootstrap

@@ -4,6 +4,9 @@ set -uo pipefail
 
 # Constants
 RUNTIME_PATH="2018-06-01/runtime"
+mkdir -p /tmp/.aws
+mv .aws/config /tmp/.aws/config
+mv .aws/credentials /tmp/.aws/credentials
 
 # Send initialization error to Lambda API
 sendInitError () {
@@ -45,8 +48,16 @@ do
   RESPONSE="$(mktemp)"
   EVENT_DATA=$(curl -sS -LD "$HEADERS" -X GET "http://${AWS_LAMBDA_RUNTIME_API}/${RUNTIME_PATH}/invocation/next")
   REQUEST_ID=$(grep -Fi Lambda-Runtime-Aws-Request-Id "$HEADERS" | tr -d '[:space:]' | cut -d: -f2)
+  #export PYTHONPATH="/var/task/bin/site-packages"
+  # Export some additional context
+  export AWS_LAMBDA_REQUEST_ID=$REQUEST_ID
+  export AWS_LAMBDA_DEADLINE_MS=$(grep -Fi Lambda-Runtime-Deadline-Ms "$HEADERS" | tr -d '[:space:]' | cut -d: -f2)
+  export AWS_LAMBDA_FUNCTION_ARN=$(grep -Fi Lambda-Runtime-Invoked-Function-Arn "$HEADERS" | tr -d '[:space:]' | cut -d: -f2)
+  export AWS_LAMBDA_TRACE_ID=$(grep -Fi Lambda-Runtime-Trace-Id "$HEADERS" | tr -d '[:space:]' | cut -d: -f2)
   # Workaround until this is a layer
   export PATH=$PATH:/var/task/bin
+  export AWS_CONFIG_FILE="/tmp/.aws/config"
+  export AWS_SHARED_CREDENTIALS_FILE="/tmp/.aws/credentials"
   # Execute the user function
   $(echo "$_HANDLER" | cut -d. -f2) "$EVENT_DATA" >&1 2> $RESPONSE | cat
   EXIT_CODE=$?