Skip to content
Nubent

/Glossary · DevOps

What is CI/CD?

CI/CD is the set of continuous integration and continuous delivery or deployment practices that automates building, testing and releasing every code change. It lets you ship small changes to production frequently and reliably.

How a CI/CD pipeline works

Continuous integration runs builds, tests and static analysis on every pull request, so bugs surface minutes after the code is written. Continuous delivery keeps every version ready for production, and continuous deployment releases it automatically once all checks pass.

On AWS, a typical pipeline uses GitHub Actions or CodePipeline with CodeBuild, pushes images to Amazon ECR and deploys to ECS, EKS or Lambda. Authentication uses OIDC and short-lived IAM roles, with no keys stored in the repository or in CI system variables.

When to invest in CI/CD

As soon as your first service reaches production. If every deployment needs manual commands, coordination over chat or one specific person, the risk of error and the time lost grow with every release. A basic pipeline is a small investment that pays for itself quickly.

It is also worth revisiting when pipelines take too long, fail intermittently or every team maintains a different one. A slow pipeline pushes people to batch large changes, which are exactly the riskiest to deploy and the hardest to roll back.

Best practices and common mistakes

Keep changes small, promote the same image or artifact through every environment, and roll out progressively with blue/green or canary strategies, which ECS, Lambda and CodeDeploy support. Add automatic rollback based on CloudWatch alarms so catching a failure doesn't depend on someone noticing it.

Common mistakes: rebuilding the artifact for each environment, storing long-lived credentials in CI, skipping tests to go faster, and not versioning the pipeline definition. Another problem is deploying infrastructure and application in no particular order, which causes failures that are hard to reproduce.

/FAQ

Questions about CI/CD

Another question? Write to hello@nubent.com and an engineer will answer.

What is the difference between continuous delivery and continuous deployment?

With continuous delivery every change is ready for production, but someone approves the final step. With continuous deployment that step is automatic too: if all tests and checks pass, the change reaches production with no manual intervention.

Should you use GitHub Actions or AWS CodePipeline?

If your code already lives on GitHub, GitHub Actions with OIDC into AWS is usually the simplest choice. CodePipeline fits when you want everything inside AWS, with IAM permissions and auditing in CloudTrail. Both can coexist depending on the workload.

How does a pipeline authenticate to AWS securely?

With OpenID Connect: the CI system gets a signed token and assumes an IAM role with scoped permissions and temporary credentials. That way there are no static access keys to rotate or to leak from the repository.

Next step

What should we build next on AWS?

30 minutes with an engineer. Concrete next steps, whether or not you work with us.