DEV Community

Discussion on: Deploy AWS Lambda functions with aws-sam-cli and Travis-CI: Part 2

Collapse
 
edouardgv profile image
Edouard

Thank you Mike for your detailled and nevertheless clear post.

Just a few changes since you wrote your article:

  • Travis configuration file is .travis.yml and not .travis-ci.yml
  • aws sam cli requires now Python 3.
  • I had to trigger manually a build on the branch in travis console.
  • I found easier to give AWS key id and secret key through (secret) configuration variable provided by travis: there are not printed anywhere anymore. For instance my env part of my .travis-ci.yml looks like this, where AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are set in travis settings of the corresponding repository.
env:
  global:
  - AWS_DEFAULT_REGION: eu-west-3
  - access_key_id: $AWS_ACCESS_KEY_ID
  - secret_access_key: $AWS_SECRET_ACCESS_KEY
Collapse
 
codevbus profile image
Mike Vanbuskirk

Thanks for the updates Edouard. I've been going through older posts and realizing they are a bit out of date :)

I plan to write some new Serverless content like this in the near future.