[AWS] 07 - CI/CD by CodePipelines

前情回顾

Bitbucket方式，需要配置aws key这些个。直接在aws codepipeline如何？

Ref: https://bitbucket.org/bitbucketpipelines/workspace/projects/TAT [bitbucket提供的模板]

image: atlassian/default-image:2

pipelines:
  default:
    - step:
        name: Build artifact
        script:
          - mkdir artifact
          - echo "Pipelines is awesome!" > artifact/index.html
        artifacts:
          - artifact/*
    - step:
        name: Deploy to S3
        deployment: production
        script:
          - pipe: atlassian/aws-s3-deploy:0.3.8
            variables:
              AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
              AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
              AWS_DEFAULT_REGION: 'us-east-1'
              S3_BUCKET: 'bbci-example-s3-deploy'
              LOCAL_PATH: 'artifact'
              ACL: 'public-read'

CodePipeline

背景摘要

Zappa与CodeDeploy的竞争关系

Ref: More than 'Hello World in Lambda': Build and Deploy Python Flask APIs in AWS Lambda via CDK

Continuous Delivery: Zappa was built with CI/CD pipelines in mind. So, instead of using Zappa to deploy the application directly, you can also use it to generate a CloudFormation template and zipped code package for your own DIY deployment.

As a DevOps-minded engineer, I love that this option, but as a lazy programmer, I love the full functionality of Zappa even more.

For my CI/CD pipelines, I just install Zappa as a dependency in my CI service (e.g. AWS CodePipeline/CodeBuild) and call zappa deploy in my deployment scripts. This works like a charm.