Deployment & CI/CD on 🏠

19. CI/CD (CodeCommit, CodeBuild, CodeDeploy, CodePipeline)

Mon, 01 Jan 0001 00:00:00 +0000

CI/CD (CodeCommit, CodeBuild, CodeDeploy, CodePipeline)#

Manual deployments are slow, inconsistent, and error-prone. When every release requires a developer to SSH into a server, run scripts by hand, or remember the exact sequence of steps, mistakes happen — and scaling that process across teams and environments becomes untenable. AWS provides a suite of managed services — CodeCommit, CodeBuild, CodeDeploy, and CodePipeline — that together let you automate the entire path from a code commit to a production deployment. This is the foundation of a modern CI/CD (Continuous Integration / Continuous Delivery) pipeline on AWS.

20. SAM (Serverless Application Model)

Mon, 01 Jan 0001 00:00:00 +0000

SAM (Serverless Application Model)#

Building serverless applications by hand means writing long, verbose CloudFormation templates just to define a Lambda function with an API Gateway trigger and a DynamoDB table. AWS SAM (Serverless Application Model) solves this by providing a shorthand syntax on top of CloudFormation, specifically designed for serverless resources. A few lines of SAM YAML expand into the dozens of CloudFormation lines you’d otherwise have to maintain. Beyond templating, SAM also ships a CLI that lets you build, test locally, and deploy serverless applications — making the entire development loop faster and safer.

21. CloudFormation

Mon, 01 Jan 0001 00:00:00 +0000

CloudFormation#

AWS CloudFormation lets you define your entire AWS infrastructure as code — VPCs, databases, Lambda functions, IAM roles, and more — in a single declarative template. Instead of clicking through the console or running ad-hoc CLI commands, you describe what you want, and CloudFormation figures out how to create it, in the right order, handling dependencies automatically.

The core problem it solves is repeatability. Without IaC, recreating a production environment in a new region, or letting a teammate spin up an identical dev stack, is error-prone and slow. With CloudFormation, you version-control your infrastructure alongside your application code and deploy it consistently every time.

22. CDK

Mon, 01 Jan 0001 00:00:00 +0000

CDK (Cloud Development Kit)#

The AWS Cloud Development Kit (CDK) is an open-source framework that lets you define cloud infrastructure using familiar programming languages — TypeScript, Python, Java, C#, and Go — instead of writing raw YAML or JSON templates. It solves a real pain point: CloudFormation templates are verbose, hard to reuse, and lack the abstraction tools developers rely on (loops, conditionals, functions, classes). CDK brings those tools back. Under the hood, CDK still generates and deploys CloudFormation — it’s a higher-level abstraction on top of it, not a replacement. 🔗

23. Elastic Beanstalk

Mon, 01 Jan 0001 00:00:00 +0000

Elastic Beanstalk#

Deploying a web application on AWS from scratch means provisioning EC2 instances, configuring load balancers, setting up Auto Scaling groups, managing security groups, and wiring everything together — before writing a single line of application logic. Elastic Beanstalk 🔗 solves this by handling all that infrastructure automatically. You upload your code, choose a platform, and Beanstalk provisions and manages the underlying resources. You retain full access to those resources if you need to customize them, but the heavy lifting is done for you.

24. AppConfig

Mon, 01 Jan 0001 00:00:00 +0000

AppConfig#

Deploying a new version of your application every time you want to change a configuration value — a feature flag, a timeout, a rate limit — is slow, risky, and wasteful. AWS AppConfig 🔗 solves this by letting you deploy configuration changes independently of code, with built-in validation, gradual rollout, and automatic rollback. It’s especially useful for feature flags: you can enable a new feature for 10% of users, watch your error metrics, and expand (or roll back) without touching a deployment pipeline.