aws sam deploy

Question

Hi dear community,

We're currently facing a problem with deploying lambda function's artefacts together with 3rd party libraries.

Could you please clarify, how to resolve and deploy properly these dependencies using aws-sam-deploy pipe?

* we use the last version of pipe.

variables in BBPL file:

variables:
  AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID_STAGE
  AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY_STAGE
  AWS_DEFAULT_REGION: 'eu-central-1'    
  S3_BUCKET: 'templates-stage' 
  STACK_NAME: 'stackname'                
  SAM_TEMPLATE: 'template.yaml'            
  CAPABILITIES: ['CAPABILITY_IAM', 'CAPABILITY_AUTO_EXPAND']
  DEBUG: 'true'

To reproduce:

add requirements.txt file( with e.g. psycopg2-binary) to your lambda source code. Deploy. In S3 bucket you'll see that the file uploaded to S3 bucket is too small and Lambda is not working.

Best Regards,

Alexey

Soumyadip Nayak · Answer

For those who are yet to find a solution, here is the list of images where you can get SAM preinstalled with the required interpreter Image repositories for AWS SAM

chlitsas · Answer

Hi everyone,

I struggled with the same issue for a while, and came up with the following:

- step:
name: Build & Deploy to Production
script:
- pip install aws-sam-cli   # install sam cli first
      - sam build                 # package the project properly
      - cd .aws-sam/build         # all packages (one folder per function) are located here
      - pipe: atlassian/aws-sam-deploy:0.5.2
variables:
          SOME_VARIABLE: 'some value...'

Long story short, you'll need the three extra commands (the ones with comments next to them) to create the packages before you call sam-deploy.

I checked the current version of the lib (aws-sam-deploy:0.5.2) and I wasn't able to figure out how the commands "sam build" and "sam deploy" are triggered. For that reason I decided to run the build as an extra step and be sure that everything is packaged the way I want. Then it seems that the pipe can do the rest. I'd really appreciate some clarification here from the team that created this one.

I also wanted to raise one question about the solution provided by @Ignas Pbecause I feel there is a week point there. In my opinion the requirement to create the samconfig file on the localhost limits this solution from being dynamic. As an example, when one adds a new lambda function, she has to remember to re-generate this config before she runs the pipeline. Please let me know your thoughts on that there is something I have missed.

Cheers,
Chris

dmytro_zlys8u · Answer

I think, this might be  somehow related to https://github.com/awslabs/aws-sam-cli/issues/978#issue-406800072. `aws-sam-deploy` pipe uses `sam package ---template-file",  and with it somehow packages are properly installed and uploaded.