terraform-provider-compose2ecs - A terraform plugin containing a datasource that can transform a docker compose file into an ecs task defnition

  •        5

A terraform plugin containing a datasource that can transform a docker compose file into an ecs task definition. Download and install the plugin, either by putting the binary next to your terraform binary or by addding it to your ~/.terraformrc as documented here.

https://github.com/jritsema/terraform-provider-compose2ecs

Tags
Implementation
License
Platform

   




Related Projects

terraform-ecs - AWS ECS terraform module

  •    HCL

This repository contains the Terraform modules for creating a production ready ECS in AWS. To understand ECS it is good to state the obvious differences against the competitors like Kubernetes or DC/OS Mesos. The mayor differences are that ECS can not be run on-prem and that it lacks advanced features. These two differences can either been seen as weakness or as strengths.

infrastructure-as-code-talk - Sample code for the talk "Infrastructure-as-code: running microservices on AWS with Docker, ECS, and Terraform"

  •    HCL

Note: This repo is for demonstration purposes only and should NOT be used to run anything important. For production-ready version of this code and many other types of infrastructure, check out Gruntwork. The docker-compose.yml file mounts rails-frontend and sinatra-backend folders as volumes in each Docker image, so any changes you make to the apps on your host OS will automatically be reflected in the running Docker container. This lets you do iterative "make-a-change-and-refresh" style development.

ecs-deploy - Simple shell script for initiating blue-green deployments on Amazon EC2 Container Service (ECS)

  •    Shell

This script uses the Task Definition and Service entities in Amazon's ECS to instigate an automatic blue/green deployment. Remember that in the EC2 Container Service, the relationship between the group of containers which together provide a useful application (e.g. a database, web frontend, and perhaps some for maintenance/cron) is specified in a Task Definition. The Task Definition then acts a sort of template for actually running the containers in that group. That resulting group of containers is known as a Task. Due to the way docker implements networking, generally you can only run one Task per Task Definition per Container Instance (the virtual machines providing the cluster infrastructure).

terraform-provider-oci - Terraform Oracle Cloud Infrastructure provider

  •    Go

The OCI Terraform Provider is now available for automatic download through the Terraform Provider Registry. For more information on how to get started view the documentation and setup guide. Note: You may use any version 1.8 or above to build the provider. However, the goimports, go vet, and gofmt code checks will only pass when using version 1.11.

terraform-provider-helm - Terraform Helm provider

  •    Go

This is a Helm provider for Terraform. The provider manages the installed Charts in your Kubernetes cluster, in the same way of Helm does, through Terraform. It will also install Tiller automatically if it is not already present.


terraform-provider-aws - Terraform AWS provider

  •    Go

If you're building the provider, follow the instructions to install it as a plugin. After placing it into your plugins directory, run terraform init to initialize it. Documentation about the provider specific configuration options can be found on the provider's website. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.11+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

terraform-provider-azurerm - Terraform provider for Azure Resource Manager

  •    Go

Further usage documentation is available on the Terraform website. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.11+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

terraform-provider-google - Terraform Google Cloud Platform provider

  •    Go

See the Google Provider documentation to get started using the Google provider. We recently introduced the google-beta provider. See Provider Versions for more details on how to use google-beta.

terraform-provider-kubernetes - Terraform Kubernetes provider

  •    Go

In order to prevent breaking changes and migration of user-created resources, resources included in this provider will be limited to v1 APIs and not alpha or beta. You can find v1 resources in the Kubernetes API documentation for the appropriate version of Kubernetes. If you wish to work on the provider, you'll first need Go installed on your machine (version 1.9+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

amazon-ecs-cli - A custom Amazon ECS CLI that eases up the cluster setup process, enables users to run their applications locally or on ECS using the same Docker Compose file format and familiar Compose commands

  •    Go

The Amazon ECS Command Line Interface (CLI) is a command line interface for Amazon EC2 Container Service (Amazon ECS) that provides high-level commands to simplify creating, updating, and monitoring clusters and tasks from a local development environment. The Amazon ECS CLI supports Docker Compose, a popular open-source tool for defining and running multi-container applications. Use the CLI as part of your everyday development and testing cycle as an alternative to the AWS Management Console.For more information about Amazon ECS, see the Amazon ECS Developer Guide. For information about installing and using the Amazon ECS CLI, see the ECS Command Line Interface.

stack - A set of Terraform modules for configuring production infrastructure with AWS

  •    HCL

The Segment Stack is a set of Terraform modules for configuring production infrastructure with AWS, Docker, and ECS. It's a more 'curated' set of defaults for configuring your AWS environment, while still allowing you to fully customize it. To get more background on the Segment Stack you can read this blog post about its history.

terraform-inventory - Terraform State → Ansible Dynamic Inventory

  •    Go

This is a little Go app which generates a dynamic Ansible inventory from a Terraform state file. It allows one to spawn a bunch of instances with Terraform, then (re-)provision them with Ansible. It's very simple to add support for new providers. See pull requests with the provider label for examples.

tack - Terraform module for creating Kubernetes cluster running on Container Linux by CoreOS in an AWS VPC

  •    HCL

Opinionated Terraform module for creating a Highly Available Kubernetes cluster running on Container Linux by CoreOS (any channel) in an AWS Virtual Private Cloud VPC. With prerequisites installed make all will simply spin up a default cluster; and, since it is based on Terraform, customization is much easier than CloudFormation.The default configuration includes Kubernetes add-ons: DNS, Dashboard and UI.

kitchen-terraform - Test Kitchen plugins for testing Terraform configurations

  •    Ruby

Kitchen-Terraform enables verification of Terraform state. Kitchen-Terraform provides a set of Test Kitchen plugins which enable a system to use Test Kitchen to converge a Terraform configuration and verify the resulting Terraform state with InSpec controls.

infrastructure-as-code-tutorial - Infrastructure As Code Tutorial

  •    

This tutorial is intended to show what the Infrastructure as Code (IaC) is, why we need it, and how it can help you manage your infrastructure more efficiently. It is practice-based, meaning I don't give much theory on what Infrastructure as Code is in the beginning of the tutorial, but instead let you feel it through the practice first. At the end of the tutorial, I summarize some of the key points about Infrastructure as Code based on what you learn through the labs.

kapitan - Generic templated configuration management for Kubernetes, Terraform and other things

  •    Python

Kapitan is a tool to manage complex deployments using jsonnet and jinja2. Use Kapitan to manage your Kubernetes manifests, your documentation, your Terraform configuration or even simplify your scripts.

terraform-up-and-running-code - Code samples for the book "Terraform: Up & Running" by Yevgeniy Brikman

  •    HCL

This repo contains the code samples for the book Terraform: Up and Running by Yevgeniy Brikman. All the code is in the code folder. It is organized by language (terraform, bash, ruby, etc) and within each language, by chapter. Since this code comes from a book about Terraform, the vast majority of the code consists of Terraform examples in the code/terraform folder.

terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform)

  •    Go

CLI tool to generate tf and tfstate files from existing infrastructure (reverse Terraform). Terraformer use terraform providers and built for easy to add new supported resources. For upgrade resources with new fields you need upgrade only terraform providers.

terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules

  •    Go

Terragrunt is a thin wrapper for Terraform that provides extra tools for keeping your Terraform configurations DRY, working with multiple Terraform modules, and managing remote state. Install Terraform.

awesome-terraform - Curated list of resources on HashiCorp's Terraform

  •    

Terraform enables you to safely and predictably create, change, and improve production infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned. For more Community Modules not listed here please see the Terraform Module Registry.