AWS DevOps Blog

Category: AWS Well-Architected Framework

Announcing the AWS Well-Architected Framework DevOps Guidance

March 26, 2024: The DevOps Guidance is now available in the Lens Catalog of the AWS Well-Architected Tool as the DevOps Lens. This update enables users to self-assess their cloud-based workloads against these best practices and view improvement plans through the tool’s report. Today, Amazon Web Services (AWS) announced the launch of the AWS Well-Architected […]

Reducing Your Organization’s Carbon Footprint with Amazon CodeGuru Profiler

It is crucial to examine every functional area when firms reorient their operations toward sustainable practices. Making informed decisions is necessary to reduce the environmental effect of an IT stack when creating, deploying, and maintaining it. To build a sustainable business for our customers and for the world we all share, we have deployed data […]

CI/CD Platform with Gitlab and AWS

Choosing a Well-Architected CI/CD approach: Open Source on AWS

Introduction When building a CI/CD platform, it is important to make an informed decision regarding every underlying tool. This post explores evaluating the criteria for selecting each tool focusing on a balance between meeting functional and non-functional requirements, and maximizing value. Your first decision: source code management. Source code is potentially your most valuable asset, […]

The 3 hexagons of the well architected logo appear to the right of the words AWS Well-Architected.

Choosing a Well-Architected CI/CD approach: Open-source software and AWS Services

Take a Well-Architected approach to make an informed decision when choosing to implement CI/CD using open-source tools on AWS services, using managed AWS services, or a combination of both.

We will look at key considerations for evaluating open-source software and AWS Services using the perspectives of a startup company, and a mature company, as examples. These will give you two very different points of view that you can use to compare to your own organization. To make this investigation easier we will use Continuous Integration (CI) and Continuous Delivery (CD) capabilities as the target of our investigation.

In our next two blog posts we will follow two AWS customers Iponweb and BigHat Biosciences as they share their CI/CD journeys, their perspective, the decisions they made, and why.

To end the series, we will explore an example reference architecture showing the benefits AWS provides regardless of your emphasis on open source tools or managed AWS services.

Choosing a CI/CD approach: Open Source on AWS, an Iponweb story

Iponweb is a global leader in building programmatic and real-time advertising technology and infrastructure for some of the world’s biggest digital media buyers and sellers. The company develops client-facing products and internal development tools that must be platform agnostic to support spanning across multiple cloud services. In this post, we explore how Iponweb applied key […]