workshop about AWS SAM and IaaC concepts

• Log in to AWS console here and generate Access and Secret Keys for CLI access. How to generate them? This way
• Install the AWS CLI -> here
• Configure the AWS CLI this is how using Access and Secret Key generated earlier on. Remember to use eu-west-1 (Ireland) region!. If you already have some account configured locally please create a separate profile.

$ aws configure
AWS Access Key ID [None]: AKIAIOSFODNN7EXAMPLE
AWS Secret Access Key [None]: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Default region name [None]: eu-west-1
Default output format [None]: json

• Test is AWS CLI is working fine and has access to your account:

aws lambda list-functions

You should receive an empty list

You need to have Docker installed and running to be able to run serverless projects and functions locally with the AWS SAM CLI. If you are only planning to use AWS SAM for templates transformations and deployments there is no need for docker. Nevertheless, I will quickly show You how to use mentioned AWS SAM functionality.

• Install it: this is how
• check if it works

sam --version

1. Single lambda (SAM local example)
2. Single lambda with API gateway (SAM local + Cloud)
3. S3 -> Lambda -> DynamoDB & SQS (Cloud)
4. Termination protection and Drift detection
5. Nested applications