SUS06 - How do you take advantage of development and deployment process to support your sustainability goals?
Best Practices
Best Practices
This question includes the following best practices:
Key Concepts
Sustainability Design Foundations
Sustainable SDLC: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Pipeline efficiency: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Policy-driven engineering: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Operational Sustainability Controls
Automated quality gates: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Environment lifecycle control: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Continuous learning loops: Use this concept to guide architecture and operating decisions for this question area. Define measurable targets, assign clear ownership, and review results regularly against expected business outcomes.
Implementation Approach
1. Embed sustainability in planning
- Define sustainability acceptance criteria for new features
- Add architecture review prompts for efficiency impacts
- Prioritize backlog items that reduce resource intensity
- Assign ownership for sustainability KPIs
2. Optimize build and deployment workflows
- Reduce unnecessary rebuilds and duplicate test runs
- Use ephemeral test environments and auto-cleanup policies
- Deploy incrementally to limit failed-change waste
- Automate policy checks for resource efficiency
3. Operationalize efficient delivery
- Measure pipeline duration and compute consumption
- Right-size CI/CD infrastructure and runners
- Automate rollback to limit prolonged degraded states
- Capture and share reusable deployment patterns
4. Close the improvement loop
- Review sustainability metrics in release retrospectives
- Link incidents and regressions to process improvements
- Train teams on efficient development practices
- Continuously refine standards and guardrails
AWS Services to Consider
AWS CodePipeline
Automates release workflows with built-in stages for quality checks and controlled deployments.
AWS CodeBuild
Runs build and test jobs in isolated environments to validate changes before deployment.
AWS CloudFormation
Defines infrastructure as code so changes are repeatable, reviewable, and easier to roll back when needed.
AWS Lambda
Runs event-driven code without managing servers, ideal for automation and on-demand operational workflows.
Amazon CloudWatch
Collects metrics, logs, alarms, and dashboards so teams can detect issues early and track operational outcomes.
Common Challenges and Solutions
Challenge: Pipelines over-consume compute resources
Solution: Profile CI/CD workloads and remove redundant jobs and oversized runners.
Challenge: Sustainability checks happen too late
Solution: Add automated policy gates and architecture checks early in development workflows.
Challenge: No accountability for efficiency regressions
Solution: Track sustainability KPIs per release and assign remediation owners for regressions.