Skip to content

Latest commit

 

History

History
149 lines (86 loc) · 6.02 KB

README.md

File metadata and controls

149 lines (86 loc) · 6.02 KB

aws-fargate

Overview

This repo includes a complete AWS - ECS fargate Infrastructure stack that enables a PaaS workflow with GitOps / ChatOps features and supports ECS, Fargate, Aurora, SQS, Redis, and Autoscaling via CDK.

Table of contents


Prerequisites


Demo

You can run and deploy the AWS-ECS-Fargate Workflow directly on our Platform, kindly follow the steps below to get started 🚀

Latest Version

The AWS - ECS Fargate Workflow is running on the latest version.

Getting Started

git clone https://github.com/workflows-sh/aws-ecs-fargate

cd aws-ecs-fargate

Set Up your Account on CTO.ai

Before you can deploy this Workflow, you need to Setup your account on CTO.ai

Create Secrets from Settings

Secrets are encrypted environment variables that CTO.ai utilizes within your workflow to build and run your application and deployments. Follow this guide to create secrets from settings., and also generate your Github token

Create your Sample - App

You need to build and run your Sample-app. Your sample App can be a Node.js HTTP server with a Dockerfile and ops.yml file.


Usage

Follow the following steps below to configure and deploy your AWS - ECS Fargate Workflow using the Ops CLI commands.

Build Pipelines

In your application, build your Docker image, from your Dockerfile, and your ops.yml file located in the specified path you created in your source directory using the ops build . command.

Run Pipelines

Next, create the running containers from the image, and start it using ops run .

Set up your Infrastructure

Next, set up your AWS infrastructure to build, and run your AWS-ECS-Fargate workflow using the ops run -b . the command will provision your AWS ECS and Fargate stack using CloudFormation.


Build and Publish Services

After building pipelines and setting up your infrastructure, you can enable service previews on your application by building your services using ops build .

Publish Services

Next, publish your service workflow using ops publish . to run your microservice web application over HTTP.


Trigger your Pipelines and Services

When you are done building and publishing your Pipelines and Services, you can trigger them using GitHub Event Triggers. Trigger your pipelines and services using event triggers like pull_request_merged create.tag


Getting help

CTO.ai AWS-ECS-Fargate Workflow is an open-source project and is supported by the community. You can buy a supported version of CTO AWS-ECS Fargate at CTO.ai

Learn more about CTO.ai community support channels here

Reporting bugs and Contributing

Feel free to submit PRs or to fill issues. Every kind of help is appreciated.

Kindly check our Contributing guide on how to propose bugfixes and improvements, and submitting pull requests to the project.

Learn more

  • Read the manual on our Docs

Other questions?

Check out our FAQ, send us an email, or open an issue with your question. We'd love to hear from you!

License

© CTO.ai, Inc., 2023

Distributed under MIT License (The MIT License).

See LICENSE for more information.