Problem: Eliminate present assumptions that developers have
a pre-created AWS user set up with proper permissions to deploy Lambda functions
a pre-created S3 Bucket
a pre-created Lambda execution role
since this is not necessarily the case, for instance when starting from scratch on a new AWS account.
Bring deployment instructions up to date with AWS interface and terminology.
What's done:
1) Updated CloudFormation template to create an S3 bucket, a Lambda deployment user (AmazonS3FullAccess, AWSLambdaFullAccess) with an access key and a Lambda execution role.
Modified Outputs to supply developer with all necessary parameters:
lambda deployment access key and secret
S3 bucket name
ARN of Lambda execution role
app execution access key and secret
2) Migrated lamduh-maven-plugin to the most recent version (2.0.1)
3) Added to the developer's getting started guide.
Coverage remained the same at 54.615% when pulling 906f69b9bfd10f8191649fd0c91a423950ee60ff on lanami:master into 7e5c26547582cd62d7f2f3ae95f702bee0c22829 on OneBusAway:master.
Coverage remained the same at 54.615% when pulling b3b39def1ca09bd0711558224e80e93a236ece42 on lanami:master into 7e5c26547582cd62d7f2f3ae95f702bee0c22829 on OneBusAway:master.
Coverage remained the same at 54.615% when pulling 5f676409bef5d35e6ff713f94438c43ead98883a on lanami:master into 7e5c26547582cd62d7f2f3ae95f702bee0c22829 on OneBusAway:master.
Problem: Eliminate present assumptions that developers have
What's done: 1) Updated CloudFormation template to create an S3 bucket, a Lambda deployment user (AmazonS3FullAccess, AWSLambdaFullAccess) with an access key and a Lambda execution role. Modified Outputs to supply developer with all necessary parameters:
2) Migrated lamduh-maven-plugin to the most recent version (2.0.1) 3) Added to the developer's getting started guide.