Download to read offline
![CodeBuild - Options. - Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables - S3 artifact - No Artifacts (think about CodePipeline) - [CodePipeline virtual artifacts] * - zip - folder](https://image.slidesharecdn.com/15-180817103703/75/Aws-Deployment-Tools-Overview-Details-Implementation-14-2048.jpg)
Aws Deployment Tools - Overview, Details, Implementation
- 1. AWS Deployment Tools- Overview, Details, Implementation Serkan Capkan
- 2. • Toolset overview ○CodeCommit ○ CodeBuild ○ CodeDeploy ○ CodePipeline ○ --CodeStar ○ -- Cloud9 ○ -- X-Ray • Implementation AGENDA AWS Deployment Tools - Overview, Details, Implementation.
- 3.
- 5. CodeCommit. ● a versioncontrol service hosted by Amazon Web Services (~gitlab,bitbucket,github ...) ● branch, PR, review, compare, visualizer...
- 6. CodeCommit. extras; ● IAM Support ●sns / lambda (commit, pr, pr comment)
- 7. CodeCommit. ● direct CodePipelineintegration * ● everything is under one account ● IAM support (everything is under one account) ● SNS support advantages
- 8. CodeCommit. ● already havegithub, gitlab, bitbucket ? ● region? disadvantages
- 10. CodeBuild. “AWS CodeBuild isa fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy” Usage; - build - test - ./do_whatever_you_want.sh
- 11. CodeBuild - Options. -Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables
- 12. CodeBuild - Options. -Source Provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables *
- 13. CodeBuild - Options. -Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables - aws managed docker images - python - golang - php etc - custom images - ECR - others * can be customized during pre_build phase
- 14. CodeBuild - Options. -Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables - S3 artifact - No Artifacts (think about CodePipeline) - [CodePipeline virtual artifacts] * - zip - folder
- 15. CodeBuild - Options. -Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables
- 16. CodeBuild - Options. -Source provider - Environment - Build specifications - Artifacts - Service Role - VPC - Environment variables buildspec_build.yml buildspec_test.yml
- 17.
- 18. CodeBuild - pros& cons. ?
- 19. CodeBuild - logs& triggers.
- 20. CodeDeploy. “AWS CodeDeploy isa deployment service that automates application deployments to Amazon EC2 instances, on-premises instances, or serverless Lambda functions.” - ec2 instances - on-promise - lambda
- 21. CodeDeploy - deploymenttypes. In-place deployment (ec2, on-promise) Blue/green deployment (ec2, lambda) - Canary - Linear - All-at-once
- 22. CodeDeploy - lambdadeployment.
- 23. CodeDeploy - options. -deployment configuration - triggers - alarms - rollback
- 24.
- 25. CodeDeploy - ec2/on-promisedepl. deploy-agent. - win / linux application - https 443 - ruby
- 26. - Deployment Type -In-place deployment - blue/green deployment - Environment Configuration - Deployment Configuration - Triggers / Alarms / Rollback CodeDeploy - ec2/on-promise depl. options.
- 27. CodeDeploy - AppSpecfile.
- 28. CodeDeploy - pros& cons.
- 29. CodePipeline. “AWS CodePipeline isa continuous delivery service you can use to model, visualize, and automate the steps required to release your software” - glue for other AWS and 3rd party deployment and testing tools - UI with some* buttons - multiple stages / actions - trigger + actions structure
- 30. CodePipeline - Options. -Source Provider (Trigger)
- 31. CodePipeline - Options. -Build Provider * Artifact is required
- 32. CodePipeline - Options. -Deployment Provider
- 33.
- 34.
- 35.
- 36. CodePipeline - pros& cons. + flexible + supports 3rd party tools + supports lambda functions - UI is not developer friendly - not easy to change branch - opinionated deployment strategy
- 37.
- 38. CodePipeline Real Life Implementation. AccountStrategy - administrative isolation - limited visibility and discoverability - isolation in order to minimize blast radius
- 39. CodePipeline Real Life Implementation. -Source Step * both repos trigger CodePipeline 1 2
- 40. CodePipeline Real Life Implementation. -Build Step buildspec_build.yml codepipeline configuration
- 41. CodePipeline Real Life Implementation. -Deploy Step * no need to any artifact
- 42. CodePipeline Real Life Implementation. -Branch Strategy (Requirement) -- Deploy any branch* to Acceptance Manually -- Deploy Master branch to Pre-Production Automatically -- Deploy Master branch to Production Manually
- 43. CodePipeline Real Life Implementation. -Branch Strategy (Requirement) 1. get CodePipeline configuration 2. change current branch to desired branch 3. change CodePipeline configuration
- 44. Final Words. ● It’snice to be able to have workflow elements under one provider, AWS. ● There is no installation, servers, maintenance on all these services, it just works! ● It’s cheap, price wise, really cheap comparing with having a CI/CD server and maintaining it. ● CodePipeline is quite flexible, considering the dashboard as a tool for developers, it can be improved with more functionality ● It’s not possible to deploy a specific branch from web interface ● CodeDeploy support is very limited
- 45. DESIGN OPERATEBUILD Standardisation FlexibilityDiversity wishes, demands, budget sizing, contract procedures, templates CD, SLA MANAGEDPUBLIC CLOUD. SENTIA / we’re hiring !