cdk-codepipeline-flutter VS aws-codedeploy-agent

I've been able to gain some experience with the tools while working on a few projects, including cdk-codepipeline-flutter and here is a list of things that I believe could be improved. My main focus here is on CodePipeline, as it serves as the glue between all of the other tools.

In this post, we are going to expand our existing project on Github to be able to build an “apk” file for Android and a zip file for iOS. Before I can show you how this is possible, let’s start with some challenges that I’ve faced 🙂

This is the definition of the CI/CD pipeline, it uses our Github repository as the source of the code and automatically starts after a push to the repository on the main branch. The “Flutter Build Stage” is the one that currently builds the Flutter web application, deploys it and makes it available to the end user. Going forward, to make best use of Flutter, we would need to expand this stage to also be able to build an iOS application, an android application or an application for any other platform supported by Flutter. As a “goal” I would personally also want to extend this stage to be able to publish the apps to the corresponding stores (App Store, Play Store, Windows Store, …) – Thanks to my friends at cosee for the help and guidance around this process!

AWS CodeDeploy is a deployment service that automates application deployments to Amazon EC2 instances, on-premises instances, serverless Lambda functions, or Amazon ECS services. A compute platform is a platform on which CodeDeploy deploys an application. There are three compute platforms:

When we deploy code at Aha! we kick off a number of AWS CodeDeploy tasks running in parallel. Here's some code to simulate deployment:

AWS has a service named CodeDeploy for this. It does exactly what you describe.

AWS CodeDeploy is a fully managed deployment service that automates software deployments to various compute services, such as Amazon Elastic Compute Cloud (EC2), Amazon Elastic Container Service (ECS), AWS Lambda, and your on-premises servers.

AWS's developer suite of products includes the AWS CodeDeploy offering, which can help developers deploy AWS Lambda functions and other compute-related services.

Documentation

AWS? Dude, use CodeDeploy green blue with hooks.

AWS CodeDeploy is a service from Amazon Web Services that automates deployments to any instance. It works with any language, platform, or application. AWS CodeDeploy makes it easier to release new features quickly, avoid downtime during application deployment, and handle the complexity of updating applications. Users can also test and track deployments so they're not left guessing or digging through logs when something goes wrong. Our integration with AWS CodeDeploy can be integrated directly into your CI/CD pipeline to improve your AWS DevOps security.

If you have a BFF, that means you have a front-end. If you have a front-end, you gotta host it somewhere. Amplify is an AWS managed service built for hosting Single Page Applications. It abstracts away all the existing serverless tech you’d traditionally use on AWS into a single place, automating most of it. S3 static asses, cache busting on deploy, and it even abstracts it’s own build pipeline using CodeDeploy sourced right from your code repository. Like AppSync, it creates a CloudFront distribution for you, and optionally provides automatic Route53 creation if you want at full URL.

Once a fresh build passes via CodePipeline, CodeDeploy distributes the functioning package to each instance based on your predefined settings. This makes it easy to coordinate builds and upgrade or patch simultaneously. CodeDeploy is code-agnostic and includes typical old code with ease. Every deployment instance can be readily monitored using the AWS Management Console, and any mistakes or issues may be rolled back through the graphical user interface.