Downloaded 29 times
Uploaded byCobus Bernard
AWS DevDay Cologne - CI/CD for modern applications
The document discusses approaches for modern application development including continuous integration, continuous deployment, infrastructure as code, microservices, and serverless technologies. It provides examples of using AWS services like CodePipeline, CodeBuild, CodeDeploy, SAM, and CDK to implement infrastructure as code, continuous integration, and continuous deployment. The document contains diagrams and code samples to illustrate these concepts and services.
More Related Content
Similar to AWS DevDay Cologne - CI/CD for modern applications
![[CPT DevOps Meetup] Developing Modern Applications in the Cloud](https://cdn.slidesharecdn.com/ss_thumbnails/devopsdeveloping-modern-applications-in-the-cloud-no-notes-190718062311-thumbnail.jpg?width=640&height=640&fit=bounds)
![Agility and Control from AWS [FutureStack16]](https://cdn.slidesharecdn.com/ss_thumbnails/agilityandcontroldougleeaws-161201210211-thumbnail.jpg?width=640&height=640&fit=bounds)
More from Cobus Bernard
AWS DevDay Cologne - CI/CD for modern applications
- 1. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. C O L O G N E CI/CD for ModernApplications Cobus Bernard SeniorTechnical Evangelist AmazonWeb Services M A D 1 23.10.19 @cobusbernard In/cobusbernard cobusbernard
- 2. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Development transformation atAmazon: 2001–2002 monolithic application + teams 2001 Lesson learned: decompose for agility 2002 microservices + 2 pizza teams
- 3. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Full ownership Full accountability “DevOps” Focused innovation Two-pizzateams
- 4. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Monolithdevelopment lifecycle monitorreleasetestbuild developers delivery pipelines services
- 5. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Microservicedevelopment lifecycle ??? developers delivery pipelines services
- 6. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Microservicedevelopment lifecycle developers services monitorreleasetestbuild delivery pipelines monitorreleasetestbuild monitorreleasetestbuild monitorreleasetestbuild monitorreleasetestbuild monitorreleasetestbuild
- 7. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. ListenIterate Experiment Innovation Flywheel Experiments power theengine of rapid innovation
- 8. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Whatchangesdoyouneedtomaketoadoptthesebestpractices? Serverless No provisioning/management Automatic scaling Pay for value billing Availability and resiliency Microservices Componentization Business capabilities Products not projects Infrastructure automation DevOps Cultural philosophies Cross-disciplinary teams CI/CD Automation tools DEV OPS Architectural patterns Operational Model Software Delivery
- 9. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Whatis serverless? No infrastructure provisioning, no management Automatic scaling Pay for value Highly available and secure
- 10. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Comparison of operational responsibility AWS Lambda Serverless functions AWS Fargate Serverless containers ECS/EKS Container-management as a service EC2 Infrastructure-as-a-Service More opinionated Less opinionated AWS manages Customer manages • Data source integrations • Physical hardware, software, networking, and facilities • Provisioning • Application code • Container orchestration, provisioning • Cluster scaling • Physical hardware, host OS/kernel, networking, and facilities • Application code • Data source integrations • Security config and updates, network config, management tasks • Container orchestration control plane • Physical hardware software, networking, and facilities • Application code • Data source integrations • Work clusters • Security config and updates, network config, firewall, management tasks • Physical hardware software, networking, and facilities • Application code • Data source integrations • Scaling • Security config and updates, network config, management tasks • Provisioning, managing scaling and patching of servers
- 11. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Approaches tomodern applicationdevelopment • Simplify environment management • Reduce the impact of code changes • Automate operations • Accelerate the delivery of new, high-quality services • Gain insight across resources and applications • Protect customers and the business
- 12. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Approaches tomodern applicationdevelopment • Simplify environment management with serverless technologies • Reduce the impact of code changes with microservice architectures • Automate operations by modeling applications & infrastructure as code • Accelerate the delivery of new, high-quality services with CI/CD • Gain insight across resources and applications by enabling observability • Protect customers and the business with end-to-end security & compliance
- 13. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Approaches tomodern applicationdevelopment • Simplify environment management with serverless technologies • Reduce the impact of code changes with microservice architectures • Automate operations by modeling applications & infrastructure as code • Accelerate the delivery of new, high-quality services with CI/CD • Gain insight across resources and applications by enabling observability • Protect customers and the business with end-to-end security & compliance
- 14. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Approaches tomodern applicationdevelopment • Simplify environment management with serverless technologies • Reduce the impact of code changes with microservice architectures • Automate operations by modeling applications & infrastructure as code • Accelerate the delivery of new, high-quality services with CI/CD • Gain insight across resources and applications by enabling observability • Protect customers and the business with end-to-end security & compliance
- 15. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Releaseprocess stages Source Build Test Production
- 16. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Releaseprocess stages Source Build Test Production • Integration tests with other systems • Load testing • UI tests • Security testing • Check-in source code such as .java files • Peer review new code • Compile code • Unit tests • Style checkers • Create container images and function deployment packages • Deployment to production environments • Monitor code in production to quickly detect errors
- 17. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Releaseprocess stages Source Build Test Production
- 18. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Releaseprocess stages Source Build Test Production
- 19. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications
- 20. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Infrastructure as code
- 21. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Infrastructure ascode Declarative I tell you what I need I tell you what to do Imperative
- 22. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Infrastructure ascode goals 1. Make infrastructure changes repeatable and predictable 2. Release infrastructure changes using the same tools as code changes 3. Replicate production environment in a staging environment to enable continuous testing
- 23. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Releaseinfrastructure-as-code “Master” branch Prepare template Create & execute change set Create & execute change set
- 24. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Model function environments withAWS ServerlessApplication Model (SAM) • Open source framework for building serverless applications on AWS • Shorthand syntax to express functions, APIs, databases, and event source mappings • Transforms and expands SAM syntax into AWS CloudFormation syntax on deployment • Supports all AWS CloudFormation resource types https://aws.amazon.com/serverless/sam/
- 25. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. SAMtemplate AWSTemplateFormatVersion: '2010-09-09’ Transform: AWS::Serverless-2016-10-31 Resources: GetFunction: Type: AWS::Serverless::Function Properties: Handler: index.get Runtime: nodejs8.10 CodeUri: src/ Policies: - DynamoDBReadPolicy: TableName: !Ref MyTable Events: GetResource: Type: Api Properties: Path: /resource/{resourceId} Method: get MyTable: Type: AWS::Serverless::SimpleTable Just 20 lines to create: • Lambda function • IAM role • API Gateway • DynamoDB table
- 26. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. UseSAMCLIto packageand deploySAMtemplates pip install --user aws-sam-cli sam logs sam validate sam local sam init sam build sam package sam deploy sam publish New
- 27. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Model container environments withAWS Cloud Development Kit(CDK) • Open source framework to define cloud infrastructure • JavaScript, TypeScript, and Python, (Java, and C# in developer preview) • Provides library of higher-level resource types (“construct” classes) that have AWS best practices built in by default • Provisions resources with CloudFormation • Supports all CloudFormation resource types AWS CDK https://awslabs.github.io/aws-cdk
- 28. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CDKtemplate import ec2 = require('@aws-cdk/aws-ec2'); import ecs = require('@aws-cdk/aws-ecs'); import cdk = require('@aws-cdk/cdk'); class BonjourFargate extends cdk.Stack { constructor(parent: cdk.App, name: string, props?: cdk.StackProps) { super(parent, name, props); const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 2 }); const cluster = new ecs.Cluster(this, 'Cluster', { vpc }); new ecs.LoadBalancedFargateService( this, "FargateService", { cluster, image: ecs.DockerHub.image("amazon/amazon-ecs-sample"), }); } } const app = new cdk.App(); new BonjourFargate(app, 'Bonjour'); app.run();
- 29. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. import ec2 = require('@aws-cdk/aws-ec2'); import ecs = require('@aws-cdk/aws-ecs'); import cdk = require('@aws-cdk/cdk'); class BonjourFargate extends cdk.Stack { constructor(parent: cdk.App, name: string, props?: cdk.StackProps) { super(parent, name, props); const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 2 }); const cluster = new ecs.Cluster(this, 'Cluster', { vpc }); new ecs.LoadBalancedFargateService( this, "FargateService", { cluster, image: ecs.DockerHub.image("amazon/amazon-ecs-sample"), }); } } const app = new cdk.App(); new BonjourFargate(app, 'Bonjour'); app.run(); CDKtemplate
- 30. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CDKtemplate import ec2 = require('@aws-cdk/aws-ec2'); import ecs = require('@aws-cdk/aws-ecs'); import cdk = require('@aws-cdk/cdk'); class BonjourFargate extends cdk.Stack { constructor(parent: cdk.App, name: string, props?: cdk.StackProps) { super(parent, name, props); const vpc = new ec2.VpcNetwork(this, 'MyVpc', { maxAZs: 2 }); const cluster = new ecs.Cluster(this, 'Cluster', { vpc }); new ecs.LoadBalancedFargateService( this, "FargateService", { cluster, image: ecs.DockerHub.image("amazon/amazon-ecs-sample"), }); } } const app = new cdk.App(); new BonjourFargate(app, 'Bonjour'); app.run();
- 31. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. UseCDKCLItosynthesizeand deployCDKtemplates npm install -g aws-cdk cdk init app --language typescript cdk synth cdk diff cdk deploy Cdk destroy
- 32. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Infrastructure as code
- 33. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Continuous integration
- 34. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Continuous integration goals Source Build Test Production
- 35. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Continuous integration goals 1. Automatically kick off a new release when new code is checked in 2. Build and test code in a consistent, repeatable environment 3. Continually have an artifact ready for deployment 4. Continually close feedback loop when build fails
- 36. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodePipeline • Continuous delivery service for fast and reliable application updates • Model and visualize your software release process • Builds, tests, and deploys your code every time there is a code change • Integrates with third-party tools and AWS
- 37. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodePipeline:Supported sources Pick branch AWS CodeCommit GitHub Pick object or folder Amazon S3 Pick Docker tag Amazon ECR Automatically kick off release and pull latest source code
- 38. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodePipeline: ECRsource action Source code: “master” branch ECR repository: “release” tag
- 39. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodePipeline:Supported triggers Automatically kick off release Amazon CloudWatch Events • Scheduled (nightly release) • AWS Health events (Fargate platform retirement) Available in CloudWatch Events console, API, SDK, CLI, and AWS CloudFormation Webhooks • DockerHub • Quay • Artifactory Available in CodePipelineAPI, SDK, CLI, and CloudFormation
- 40. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeBuild • Fully managed build service that compiles source code, runs tests, and produces software packages • Scales continuously and processes multiple builds concurrently • No build servers to manage • Pay by the minute, only for the compute resources you use • Monitor builds through CloudWatch Events
- 41. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeBuild • Each build runs in a new Docker container for a consistent, immutable environment • Docker and AWS CLI are installed in every official CodeBuild image • Provide custom build environments suited to your needs through the use of Docker images
- 42. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeBuild: Lambda buildspec version: 0.2 phases: build: commands: - npm ci - npm test - > aws cloudformation package --template-file template.yaml --output-template packaged.yaml --s3-bucket $BUCKET artifacts: type: zip files: - packaged.yaml
- 43. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeBuild: Lambda buildspec usingSAMCLI version: 0.2 phases: install: commands: - pip install --upgrade awscli aws-sam-cli build: commands: - sam build - sam package --s3-bucket $BUCKET --output-template-file packaged.yaml artifacts: type: zip files: - packaged.yaml
- 44. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeBuild: Docker buildspec version: 0.2 phases: build: commands: - $(aws ecr get-login --no-include-email) - docker build -t $IMAGE_REPO_NAME:$IMAGE_TAG . - docker tag $IMAGE_REPO_NAME:$IMAGE_TAG $ECR_REPO:$IMAGE_TAG - docker push $ECR_REPO:$IMAGE_TAG
- 45. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Continuous integration
- 46. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Continuous deployment
- 47. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Continuous deployment goals Source Build Test Production
- 48. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Continuous deployment goals 1. Automatically deploy new changes to staging environments for testing 2. Deploy to production safely without impacting customers 3. Deliver to customers faster: Increase deployment frequency, and reduce change lead time and change failure rate
- 49. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. AWSCodeDeploy • Automates code deployments to any instance and Lambda • Handles the complexity of updating your applications • Avoid downtime during application deployment • Roll back automatically if failure detected • Deploy to Amazon EC2, Lambda, or on-premises servers
- 50. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-Lambda deployments • Shifts traffic using Lambda function weighted aliases • Choose canary (“shift 10% of traffic for 10 minutes, then shift rest”) or linear (“shift 10% more traffic every 10 minutes”) • Validation “hooks” enable testing at each stage of the deployment • Fast rollback in seconds if case of hook failure or CloudWatch alarms • Monitor deployment status and history via console, API, Amazon Simple Notification Service (Amazon SNS) notifications, and CloudWatch Events
- 51. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy – Lambda deployments Enable in your serverless application template Resources: GetFunction: Type: AWS::Serverless::Function Properties: DeploymentPreference: Type: Canary10Percent10Minutes Alarms: - !Ref ErrorsAlarm Hooks: PreTraffic: !Ref PreTrafficHook Canary10Percent30Minutes Canary10Percent5Minutes Canary10Percent10Minutes Canary10Percent15Minutes Linear10PercentEvery10Minutes Linear10PercentEvery1Minute Linear10PercentEvery2Minutes Linear10PercentEvery3Minutes AllAtOnce
- 52. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy – Lambda canary deployment API Gateway Lambda function weighted alias “live” v1 Lambda function code 100%
- 53. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy – Lambda canary deployment API Gateway Lambda function weighted alias “live” v1 code100% Run PreTraffic hook against v2 code before it receives traffic v2 code0%
- 54. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy – Lambda canary deployment API Gateway Lambda function weighted alias “live” v1 code90% Wait for 10 minutes, roll back in case of alarm v2 code10%
- 55. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy – Lambda canary deployment API Gateway Lambda function weighted alias “live” v1 code0% Run PostTraffic hook and complete deployment v2 code100%
- 56. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployments • Provisions “green” tasks, then flips traffic at the load balancer • Validation “hooks” enable testing at each stage of the deployment • Fast rollback to “blue” tasks in seconds if case of hook failure or CloudWatch alarms • Monitor deployment status and history via console, API, Amazon SNS notifications, and CloudWatch Events • Use “CodeDeploy-ECS” deploy action in CodePipeline or “aws ecs deploy” command in Jenkins
- 57. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS appspec version: 1.0 Resources: - TargetService: Type: AWS::ECS::Service Properties: - TaskDefinition: "my_task_definition:8" LoadBalancerInfos: - ContainerName: "SampleApp" ContainerPort: 80 Hooks: - BeforeInstall: "LambdaFunctionToExecuteAnythingBeforeNewRevisionInstalltion" - AfterInstall: "LambdaFunctionToExecuteAnythingAfterNewRevisionInstallation" - AfterAllowTestTraffic: "LambdaFunctionToValidateAfterTestTrafficShift" - BeforeAllowTraffic: "LambdaFunctionToValidateBeforeTrafficShift" - AfterAllowTraffic: "LambdaFunctionToValidateAfterTrafficShift"
- 58. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment 100% Prod traffic
- 59. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment Target group 2 100% Prod traffic Test traffic listener (port 9000)
- 60. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment Green tasks: v2 code 100% Prod traffic Provision green tasks
- 61. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment 100% Test traffic 100% Prod traffic Run hook against test endpoint before green tasks receive prod traffic
- 62. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment 100% Prod traffic Flip traffic to green tasks, rollback in case of alarm 0% Prod traffic
- 63. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CodeDeploy-ECS blue-green deployment 100% Prod traffic Drain blue tasks 100% Prod traffic
- 64. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Pillarsof releasingmodern applications Continuous deployment
- 65. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved.
- 66. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CapitalOne–CreditOffersAPICI/CDpipeline Continuous Improvement, Continuous Delivery! GitHub LGTM Bot Jenkins AWS SAM DeploymentType: dev: AllAtOnce qa: AllAtOnce qaw: AllAtOnce prod: Canary10Percent10Minutes prodw: Canary10Percent10Minutes canary5xxGetProductsAlarm: Type: AWS::CloudFormation::Alarm Properties: AlarmActions: - !FindInMap: - params - AdminSNSTopic - !Ref Environment AlarmDescription: 500 error from product listing Lambda. ComparisonOperator: GreatherThanOrEqualTothreshold Period: 300 Statistic: Sum Threshold: 1 EvaluationPeriod: 1 AWS CodeDeploy S3 Bucket (Versioning) Lambda function
- 67. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. CapitalOne–BenefitsfromtakingtheAPIserverless Performance gains From the time the request is received by lambda to the time to send the response back 70% Cost savings By removing EC2, ELB and RDS from our solution 90% Increase in team velocity Reduce investment in team’s time on DevOps and dedicate back to feature development! 30%
- 68. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. C O L O G N E https://github.com/cobusbernard/aws-containers-for-beginners
- 69. © 2019, AmazonWeb Services, Inc. or its affiliates. All rights reserved. Takeaways 1. Manage your infrastructure as code 2. Frequently build and integrate your code to get a first feedback 3. Continuously release in production using canary releases with monitoring and automated rollbacks 4. Use canary releases to get both technical and business feedback
- 70. Thank you! © 2019,Amazon Web Services, Inc. or its affiliates. All rights reserved. Cobus Bernard SeniorTechnical Evangelist Amazon Web Services C O L O G N E @cobusbernard In/cobusbernard cobusbernard
Editor's Notes
- #3 (micro)service evolution at amazon
- #4 Smal teams, 5-7 people, reducing the number of communication paths
- #5 In the old monolithic model, you might have something that looks like this This was certainly the case for Amazon where we had a big team of developers clobbering away at a big monolithic app, throwing it over the fence to QA, release and operations teams who shepherded it out to production… slowly and infrequently.
- #6 Going back to how we organize ourselves around microservices, we created the small DevOps teams to support them. Each team was now able to create software that is specific to the microservice they were responsible. Essentially we unbottlenecked the development and unbottlenecked the architecture, but we still had a release bottleneck.
- #7 The solution is self-service tools and automation….enabling each one of the DevOps teams to own and manage their own release process.
- #8 So, first things first - why do we need to accelerate innovation? There is no historical precedent for the pace of change that we’re seeing, and it’s disrupting almost every industry. Companies are becoming increasingly global, products and services are becoming completely digital Customers expectations are getting higher as they gain the power of information and choice Businesses have to be agile to constantly adapt to this change, and continuously innovate in order to not be left behind. Rapid innovation is changing what it means to be competitive Competitors can rise from obscurity to dominance in a matter of months, leaving incumbents scrambling The imperative is not just to innovate, but to innovate as quickly as possible. <!> Leaders need to differentiate their current revenue-generating products through continual, incremental innovation. At the same time, <!> they need to create differentiation by exploring and incubating innovation in new areas. And that means that competing today requires true business agility. The goal is to empower your teams to experiment, and take measured risks. Let your builders build. At Amazon, we think of builders as people who reinvent customer experiences. Launching a minimal viable product -or actually, a minimal valuable product - accelerates learning MVPs can be rough and incomplete, but good enough to test assumptions. Customers will tell you whether or not your MVP actually solves their problem, or enhances their lives, And the process of experimenting, listening and iterating turns uncertainty into discovery about what will work.
- #9 OPTIONAL SLIDE For AWS, giving developers operational responsibilities has greatly enhanced the quality of our services, both from a customer and a technology point of view. At Amazon, our philosophy is you build it, you run it. This brings developers into contact with the day-to-day operation of their software, and it also brings them into day-to-day contact with the customer. This customer feedback loop is essential for improving the quality of the service. These three approaches satisfy all of our modern application development best practices.
- #10 These are the tenets that define serverless as an operational model (unless you know better ones): No infrastructure to provision or manage (no servers to provision, operate, patch, etc.) Automatically scales by unit of consumption (scales by unit of work/consumption rather than by server unit) Pay for value billing model (if you value consistent throughput or execution duration you only pay for that unit rather than by server unit) Built-in availability and fault tolerance (no need to architect for availability because it is built into the service) When we say serverless, we mean it’s the removal of the undifferentiated heavy lifting that is server operations. This is an important distinction for customers because it allows customers to focus on the building of the application rather than the management and scaling of the infrastructure to support the application.
- #14 To reduce operational responsibility and development complexity
- #15 This is the focus of this session
- #17 OPTIONAL SLIDE
- #22 There are different approaches for IaC, but it is important to use one with declarative syntax, like CloudFormation or Terraform How (Declarative) vs. What (Imperative) Programing in many cases Imperative SQL Select Declarative
- #25 Manage Serverless Build CF Deploy
- #27 Build and publish are the newest commands added to the SAM CLI Logs
- #28 The AWS CDK is an infrastructure modeling framework that allows you to define your cloud resources using an imperative programming interface. The CDK is currently in developer preview. We look forward to community feedback and collaboration.
- #29 CDK is most useful to create high level structures, for example a VPC including your standard configurations for subnets, gateways, NAT, routing, security groups.
- #31 OPTIONAL: a live demo with the CDK with this sample code
- #32 Applets are YAML files that directly instantiate constructs, without writing any code.
- #33 To configure AWS CodePipeline pipelines with the CDK. When you add a microservice, you need to create a new pipeline, similar to your other ones. With CDK you can use an higher level class instead of copying and pasting lots of YAML code.
- #34 Constructs are the building blocks of AWS CDK applications. Constructs can have child constructs, which in turn can have child constructs, forming a hierarchical tree structure. The AWS CDK includes two different levels of constructs: CloudFormation Resource These constructs are low-level constructs that provide a direct, one-to-one, mapping to an AWS CloudFormation resource, as listed in the AWS CloudFormation topic AWS Resource Types Reference. All CloudFormation Resource members are found in the @aws-cdk/resources package. AWS Construct Library These constructs have been handwritten by AWS and come with convenient defaults and additional knowledge about the inner workings of the AWS resources they represent. In general, you will be able to express your intent without worrying about the details too much, and the correct resources will automatically be defined for you. AWS Construct Library members are found in the @aws-cdk/NAMESPACE packages, where NAMESPACE is the short name for the associated service, such as SQS for the AWS Construct Library for the Amazon SQS service. See the Reference section for descriptions of the AWS CDK packages and constructs.
- #35 In the stack you can use the constructs you defines before, like the pipeline we created in the previous slide.
- #42 ECR is new
- #43 Strat from the code or from the artifact
- #44 https://docs.quay.io – Semaphore with Quay (Key) https://jfrog.com/artifactory/
- #48 Installing AWS CLI and SAM CLI in the build environment Need permissions to CodeDeploy to write into the bucket artifacts: type: zip #Only to tell this is a file (the outcome is yaml) files: - packaged.yaml
- #57 Talk about hooks!
- #58 This is my production 100% of the traffic goes to V1
- #59 PreTraffic hook – a Lambda function that need to call back CodeDeploy to move to the next stage (with the token of the deploy job) Run performance test for 1 hour for example
- #61 Post Traffic hook when all customers are on the version Usage: Tag commit that the deployment was successful and it’s in production DB Changes if needed Cleanups
- #63 New from re:Invent Same call back as in Lambda
- #82 OPTIONAL
- #83 Used to deploy once a week Before they were releasing once per week at 2am on Monday, now they deploy 2 times per day (canary) during working hours.
- #84 Used to deploy once a week Before they were releasing once per week at 2am on Monday, now they deploy 2 times per day (canary) during working hours.
- #85 Cost – This is all multi region (with replication)
- #86 Clone repo Deploy before session (you only want to show the update in the demo) Show that it works Show code Change the code to do something else Commit Show pipeline Show CloudFormation events and wait for CodeDeploy… Show canary/linear deployment on CodeDeploy for a couple of minutes Try to get the result callint the API in the browser or via curl https://t5sjvp3ew4.execute-api.eu-west-1.amazonaws.com/Prod/send/?user=danilop&message=Bonjour