cloudposse / terraform-aws-cicd

Terraform Module for CI/CD with AWS Code Pipeline and Code Build

Terraform module to create AWS CodePipeline with CodeBuild for CI/CD

This module supports three use-cases:

1. GitHub -> S3 (build artifact) -> Elastic Beanstalk (running application stack). The module gets the code from a GitHub repository (public or private), builds it by executing the buildspec.yml file from the repository, pushes the built artifact to an S3 bucket, and deploys the artifact to Elastic Beanstalk running one of the supported stacks (e.g. Java, Go, Node, IIS, Python, Ruby, etc.).

   • http://docs.aws.amazon.com/codebuild/latest/userguide/sample-maven-5m.html
   • http://docs.aws.amazon.com/codebuild/latest/userguide/sample-nodejs-hw.html
   • http://docs.aws.amazon.com/codebuild/latest/userguide/sample-go-hw.html

2. GitHub -> ECR (Docker image) -> Elastic Beanstalk (running Docker stack). The module gets the code from a GitHub repository, builds a Docker image from it by executing the buildspec.yml and Dockerfile files from the repository, pushes the Docker image to an ECR repository, and deploys the Docker image to Elastic Beanstalk running Docker stack.

   • http://docs.aws.amazon.com/codebuild/latest/userguide/sample-docker.html

3. GitHub -> ECR (Docker image). The module gets the code from a GitHub repository, builds a Docker image from it by executing the buildspec.yml and Dockerfile files from the repository, and pushes the Docker image to an ECR repository. This is used when we want to build a Docker image from the code and push it to ECR without deploying to Elastic Beanstalk. To activate this mode, don't specify the app and env attributes for the module.

   • http://docs.aws.amazon.com/codebuild/latest/userguide/sample-docker.html

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Usage

Include this repository as a module in your existing terraform code:

module "build" {
  source = "cloudposse/cicd/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"
  namespace           = "eg"
  stage               = "staging"
  name                = "app"

  # Enable the pipeline creation
  enabled             = true

  # Elastic Beanstalk
  elastic_beanstalk_application_name = "<(Optional) Elastic Beanstalk application name>"
  elastic_beanstalk_environment_name = "<(Optional) Elastic Beanstalk environment name>"

  # Application repository on GitHub
  github_oauth_token  = "(Required) <GitHub Oauth Token with permissions to access private repositories>"
  repo_owner          = "<GitHub Organization or Person name>"
  repo_name           = "<GitHub repository name of the application to be built and deployed to Elastic Beanstalk>"
  branch              = "<Branch of the GitHub repository>"

  # http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
  # http://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html
  build_image         = "aws/codebuild/standard:2.0"
  build_compute_type  = "BUILD_GENERAL1_SMALL"

  # These attributes are optional, used as ENV variables when building Docker images and pushing them to ECR
  # For more info:
  # http://docs.aws.amazon.com/codebuild/latest/userguide/sample-docker.html
  # https://www.terraform.io/docs/providers/aws/r/codebuild_project.html
  privileged_mode     = true
  region              = "us-east-1"
  aws_account_id      = "xxxxxxxxxx"
  image_repo_name     = "ecr-repo-name"
  image_tag           = "latest"

  # Optional extra environment variables
  environment_variables = [{
    name  = "JENKINS_URL"
    value = "https://jenkins.example.com"
  },
  {
    name  = "COMPANY_NAME"
    value = "Amazon"
  },
  {
    name = "TIME_ZONE"
    value = "Pacific/Auckland"
  }]
}

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

Examples

Example: GitHub, NodeJS, S3 and EB

This is an example to build a Node app, store the build artifact to an S3 bucket, and then deploy it to Elastic Beanstalk running Node stack

buildspec.yml file

version: 0.2

phases:
  install:
    commands:
      - echo Starting installation ...
  pre_build:
    commands:
      - echo Installing NPM dependencies...
      - npm install
  build:
    commands:
      - echo Build started on `date`
  post_build:
    commands:
      - echo Build completed on `date`
artifacts:
  files:
    - node_modules/**/*
    - public/**/*
    - routes/**/*
    - views/**/*
    - app.js

Example: GitHub, NodeJS, Docker, ECR and EB

This is an example to build a Docker image for a Node app, push the Docker image to an ECR repository, and then deploy it to Elastic Beanstalk running Docker stack

buildspec.yml file

version: 0.2

phases:
  pre_build:
    commands:
      - echo Logging in to Amazon ECR...
      - $(aws ecr get-login --region $AWS_REGION)
  build:
    commands:
      - echo Build started on `date`
      - echo Building the Docker image...
      - docker build -t $IMAGE_REPO_NAME .
      - docker tag $IMAGE_REPO_NAME:$IMAGE_TAG $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$IMAGE_REPO_NAME:$IMAGE_TAG
  post_build:
    commands:
      - echo Build completed on `date`
      - echo Pushing the Docker image to ECR...
      - docker push $AWS_ACCOUNT_ID.dkr.ecr.$AWS_REGION.amazonaws.com/$IMAGE_REPO_NAME:$IMAGE_TAG
artifacts:
  files:
    - '**/*'

Dockerfile

FROM node:latest

WORKDIR /usr/src/app

COPY package.json package-lock.json ./
RUN npm install
COPY . .

EXPOSE 8081
CMD [ "npm", "start" ]

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Requirements

Name	Version
terraform	>= 1.3
aws	>= 5.0
random	>= 2.1

Providers

Name	Version
aws	>= 5.0
random	>= 2.1

Modules

Name	Source	Version
codebuild	cloudposse/codebuild/aws	2.0.1
github_webhook	cloudposse/repository-webhooks/github	0.12.1
this	cloudposse/label/null	0.25.0

Resources

Name	Type
aws_codepipeline.default	resource
aws_codepipeline_webhook.default	resource
aws_iam_policy.codebuild	resource
aws_iam_policy.default	resource
aws_iam_policy.s3	resource
aws_iam_role.default	resource
aws_iam_role_policy_attachment.codebuild	resource
aws_iam_role_policy_attachment.codebuild_s3	resource
aws_iam_role_policy_attachment.default	resource
aws_iam_role_policy_attachment.s3	resource
aws_s3_bucket.default	resource
random_password.webhook_secret	resource
aws_caller_identity.default	data source
aws_iam_policy_document.assume	data source
aws_iam_policy_document.codebuild	data source
aws_iam_policy_document.default	data source
aws_iam_policy_document.s3	data source
aws_region.default	data source
aws_s3_bucket.website	data source

Inputs

Name	Description	Type	Default	Required
access_log_bucket_name	Name of the S3 bucket where s3 access log will be sent to	string	""	no
additional_tag_map	Additional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id. This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration.	map(string)	{}	no
attributes	ID element. Additional attributes (e.g. workers or cluster) to add to id, in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the delimiter and treated as a single ID element.	list(string)	[]	no
aws_account_id	AWS Account ID. Used as CodeBuild ENV variable when building Docker images. For more info	string	""	no
branch	Branch of the GitHub repository, e.g. master	string	n/a	yes
build_compute_type	CodeBuild instance size. Possible values are: BUILD_GENERAL1_SMALL BUILD_GENERAL1_MEDIUM BUILD_GENERAL1_LARGE	string	"BUILD_GENERAL1_SMALL"	no
build_image	Docker image for build environment, e.g. aws/codebuild/standard:2.0 or aws/codebuild/eb-nodejs-6.10.0-amazonlinux-64:4.0.0	string	"aws/codebuild/standard:2.0"	no
buildspec	Declaration to use for building the project. For more info	string	""	no
cache_type	The type of storage that will be used for the AWS CodeBuild project cache. Valid values: NO_CACHE, LOCAL, and S3. Defaults to S3 to keep same behavior as before upgrading codebuild module to 0.18+ version. If cache_type is S3, it will create an S3 bucket for storing codebuild cache inside	string	"S3"	no
codebuild_cache_bucket_suffix_enabled	The cache bucket generates a random 13 character string to generate a unique bucket name. If set to false it uses terraform-null-label's id value	bool	true	no
context	Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as null to use default value. Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged.	any	{ "additional_tag_map": {}, "attributes": [], "delimiter": null, "descriptor_formats": {}, "enabled": true, "environment": null, "id_length_limit": null, "label_key_case": null, "label_order": [], "label_value_case": null, "labels_as_tags": [ "unset" ], "name": null, "namespace": null, "regex_replace_chars": null, "stage": null, "tags": {}, "tenant": null }	no
delimiter	Delimiter to be used between ID elements. Defaults to - (hyphen). Set to "" to use no delimiter at all.	string	null	no
descriptor_formats	Describe additional descriptors to be output in the descriptors output map. Map of maps. Keys are names of descriptors. Values are maps of the form {<br> format = string<br> labels = list(string)<br>} (Type is any so the map values can later be enhanced to provide additional options.) format is a Terraform format string to be passed to the format() function. labels is a list of labels, in order, to pass to format() function. Label values will be normalized before being passed to format() so they will be identical to how they appear in id. Default is {} (descriptors output will be empty).	any	{}	no
elastic_beanstalk_application_name	Elastic Beanstalk application name. If not provided or set to empty string, the Deploy stage of the pipeline will not be created	string	""	no
elastic_beanstalk_environment_name	Elastic Beanstalk environment name. If not provided or set to empty string, the Deploy stage of the pipeline will not be created	string	""	no
enabled	Set to false to prevent the module from creating any resources	bool	null	no
environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	string	null	no
environment_variables	A list of maps, that contain the keys 'name', 'value', and 'type' to be used as additional environment variables for the build. Valid types are 'PLAINTEXT', 'PARAMETER_STORE', or 'SECRETS_MANAGER'	list(object( { name = string value = string type = string }))	[ { "name": "NO_ADDITIONAL_BUILD_VARS", "type": "PLAINTEXT", "value": "TRUE" } ]	no
force_destroy	Force destroy the CI/CD S3 bucket even if it's not empty	bool	false	no
github_oauth_token	GitHub Oauth Token	string	n/a	yes
github_webhook_events	A list of events which should trigger the webhook. See a list of available events	list(string)	[ "push" ]	no
github_webhooks_token	GitHub OAuth Token with permissions to create webhooks. If not provided, can be sourced from the GITHUB_TOKEN environment variable	string	""	no
id_length_limit	Limit id to this many characters (minimum 6). Set to 0 for unlimited length. Set to null for keep the existing setting, which defaults to 0. Does not affect id_full.	number	null	no
image_repo_name	ECR repository name to store the Docker image built by this module. Used as CodeBuild ENV variable when building Docker images. For more info	string	"UNSET"	no
image_tag	Docker image tag in the ECR repository, e.g. 'latest'. Used as CodeBuild ENV variable when building Docker images. For more info	string	"latest"	no
label_key_case	Controls the letter case of the tags keys (label names) for tags generated by this module. Does not affect keys of tags passed in via the tags input. Possible values: lower, title, upper. Default value: title.	string	null	no
label_order	The order in which the labels (ID elements) appear in the id. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	list(string)	null	no
label_value_case	Controls the letter case of ID elements (labels) as included in id, set as tag values, and output by this module individually. Does not affect values of tags passed in via the tags input. Possible values: lower, title, upper and none (no transformation). Set this to title and set delimiter to "" to yield Pascal Case IDs. Default value: lower.	string	null	no
labels_as_tags	Set of labels (ID elements) to include as tags in the tags output. Default is to include all labels. Tags with empty values will not be included in the tags output. Set to [] to suppress all generated tags. Notes: The value of the name tag, if included, will be the id, not the name. Unlike other null-label inputs, the initial setting of labels_as_tags cannot be changed in later chained modules. Attempts to change it will be silently ignored.	set(string)	[ "default" ]	no
name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a tag. The "name" tag is set to the full id string. There is no tag with the value of the name input.	string	null	no
namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	string	null	no
poll_source_changes	Periodically check the location of your source content and run the pipeline if changes are detected	bool	true	no
privileged_mode	If set to true, enables running the Docker daemon inside a Docker container on the CodeBuild instance. Used when building Docker images	bool	false	no
regex_replace_chars	Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.	string	null	no
region	AWS Region, e.g. us-east-1. Used as CodeBuild ENV variable when building Docker images. For more info	string	""	no
repo_name	GitHub repository name of the application to be built (and deployed to Elastic Beanstalk if configured)	string	n/a	yes
repo_owner	GitHub Organization or Person name	string	n/a	yes
s3_bucket_encryption_enabled	When set to 'true' the 'aws_s3_bucket' resource will have AES256 encryption enabled by default	bool	true	no
stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	string	null	no
tags	Additional tags (e.g. {'BusinessUnit': 'XYZ'}). Neither the tag keys nor the tag values will be modified by this module.	map(string)	{}	no
tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	string	null	no
versioning_enabled	A state of versioning. Versioning is a means of keeping multiple variants of an object in the same bucket	bool	true	no
webhook_authentication	The type of authentication to use. One of IP, GITHUB_HMAC, or UNAUTHENTICATED	string	"GITHUB_HMAC"	no
webhook_enabled	Set to false to prevent the module from creating any webhook resources	bool	false	no
webhook_filter_json_path	The JSON path to filter on	string	"$.ref"	no
webhook_filter_match_equals	The value to match on (e.g. refs/heads/{Branch})	string	"refs/heads/{Branch}"	no
webhook_target_action	The name of the action in a pipeline you want to connect to the webhook. The action must be from the source (first) stage of the pipeline	string	"Source"	no
website_bucket_acl	Canned ACL of the S3 bucket objects that get served as a website, can be private if using CloudFront with OAI	string	"public-read"	no
website_bucket_name	Name of the S3 bucket where the website will be deployed	string	""	no

Outputs

Name	Description
codebuild_badge_url	The URL of the build badge when badge_enabled is enabled
codebuild_cache_bucket_arn	CodeBuild cache S3 bucket ARN
codebuild_cache_bucket_name	CodeBuild cache S3 bucket name
codebuild_project_id	CodeBuild project ID
codebuild_project_name	CodeBuild project name
codebuild_role_arn	CodeBuild IAM Role ARN
codebuild_role_id	CodeBuild IAM Role ID
codepipeline_arn	CodePipeline ARN
codepipeline_id	CodePipeline ID

Related Projects

Check out these related projects.

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

• Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
• Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
• Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
• Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
• GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Day-2: Your Operational Mastery

• Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
• Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
• Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
• Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
• Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
• Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
• Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

1. Review our Code of Conduct and Contributor Guidelines.
2. Fork the repo on GitHub
3. Clone the project to your own machine
4. Commit changes to your own branch
5. Push your work back up to your fork
6. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

📰 Newsletter

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Complete license is available in the LICENSE file.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

---

Copyright © 2017-2024 Cloud Posse, LLC

terraform-aws-cicd's Issues

aws_iam_policy_document is missing the logs:PutRetentionPolicy

When deploying my docker image to my elastic beanstalk I received this error in the pipeline UI:

Deployment failed. The provided role does not have sufficient permissions: Failed to deploy application. Service:AWSLogs, Message:User: arn:aws:sts::xxxxx:assumed-role/xxxx-development-app/xxxxx is not authorized to perform: logs:PutRetentionPolicy on resource: arn:aws:logs:us-east-1:xxxx:log-group:/aws/elasticbeanstalk/xxxxx-dev-node-demo/var/log/nginx/error.log:log-stream:

Noise is generated in terraform plan for OAuthToken

Using terraform-aws-cicd and getting the source code from the private repo in GitHub,
and everything is applied already
whenever one executes plan, terraform wants to change OAuthToken every time

Output of terraform plan

  ~ module.build_frontend.aws_codepipeline.source_build
      stage.0.action.0.configuration.%:          "4" => "5"
      stage.0.action.0.configuration.OAuthToken: "" => "deadbeefdeadbeefdeadbeefdeadbeefdeadbeef"

Usage

module "build_frontend" {
    source              = "github.com/cloudposse/terraform-aws-cicd?ref=master"
    namespace           = "${var.namespace}"
    name                = "${var.frontend}"
    stage               = "${var.stage}"
    enabled             = "true"
    github_oauth_token  = "${var.github_oauth_token}"
    repo_owner          = "${var.github_group}"
    repo_name           = "${var.github_project_frontend}"
    branch              = "${var.github_branch_frontend}"
    build_image         = "aws/codebuild/nodejs:8.11.0"
    build_compute_type  = "BUILD_GENERAL1_SMALL"
    aws_region          = "${var.aws_region}"
    aws_account_id      = "${var.aws_account_id}"
}

Probably a reason for this is OAuthToken can be only set, not read in AWS CodePipeline.
Are there any approaches to this to have "clean" plan without any changes?

From https://www.terraform.io/docs/providers/aws/r/codepipeline.html:

NOTE on aws_codepipeline: - the GITHUB_TOKEN environment variable must be set if the GitHub provider is specified.

Tried that, nothing happens...

Passing build environment variables does not work

With Terraform v0.11.11 when setting environment_variables this error is thrown:
"environment.0.environment_variable.6.value": required field is not set
I think in build module you should do concact with var.environment_variables since this way you are inserting list inside a list.

    environment_variable = [{
      "name"  = "AWS_REGION"
      "value" = "${signum(length(var.aws_region)) == 1 ? var.aws_region : data.aws_region.default.name}"
    },
      {
        "name"  = "AWS_ACCOUNT_ID"
        "value" = "${signum(length(var.aws_account_id)) == 1 ? var.aws_account_id : data.aws_caller_identity.default.account_id}"
      },
      {
        "name"  = "IMAGE_REPO_NAME"
        "value" = "${signum(length(var.image_repo_name)) == 1 ? var.image_repo_name : "UNSET"}"
      },
      {
        "name"  = "IMAGE_TAG"
        "value" = "${signum(length(var.image_tag)) == 1 ? var.image_tag : "latest"}"
      },
      {
        "name"  = "STAGE"
        "value" = "${signum(length(var.stage)) == 1 ? var.stage : "UNSET"}"
      },
      {
        "name"  = "GITHUB_TOKEN"
        "value" = "${signum(length(var.github_token)) == 1 ? var.github_token : "UNSET"}"
      },
      "${var.environment_variables}",
    ]

Note: I did tried it with a list but still not working with different error, it seems concact is not returning list(propably problem with Terraform interpolation)

Possibility to enable badges for CodeBuild

The module outputs the param codebuild_badge_url (as documented in the Outputs section of README) but seems like there is no input variable called badge_enabled. Seems like a simple fix and would be greatly appreciated if this could be added. Thanks

No outputs?

Don't you think at least name would be appropriate?

Is github_oauth_token required?

Hi, I have a github project that can be cloned without needing a github token, but if I remove github_oauth_token from my terraform I get the following error:

Error: module "build": missing required argument "github_oauth_token"

If I set it to "" I get this:

* aws_codebuild_project.default: [ERROR] Error updating CodeBuild project (arn:aws:codebuild:eu-west-1:***): InvalidParameter: 1 validation error(s) found.
- missing required field, UpdateProjectInput.Environment.EnvironmentVariables[5].Value.

The README says it's both optional and required so not sure what I should be using. Is an oauth token always required?

Thanks :)

Need to add environment_variables to build

As a user, I would like to be able to pass in an environment_variables variable that can be utilized by the aws_codebuild module.

Required IAM PassRole for CodeBuild Project

Using 0.11 branch , latest tag 0.6.0;
Terraform 0.11.14
AWS provider 2.24

Start getting an error while applying module to create codebuild project:

        * module.build_ms_email.module.build.aws_codebuild_project.default: 1 error occurred:
        * aws_codebuild_project.default: Error creating CodeBuild project: AccessDeniedException: User: arn:aws:sts::ACCOUNTHERE:assumed-role/Playground/1566405491326350000 is not authorized to perform: iam:PassRole on resource: arn:aws:iam::ACCOUNTHERE:role/sweet-integration-microservice-email-build
        status code: 400, request id: edfdb965-1e8b-48d5-982f-ff2b7f52e43a

Had nothing similar last week, have terraform policy without IAM PassRole allow for my Playground role.

Error: cache location is required when cache type is "S3"

Found a bug? Maybe our Slack Community can help.

Describe the Bug

Terraform plan is failing on Terraform v1.0.0 with Error: cache location is required when cache type is "S3"

Expected Behavior

It should not be failing to create the CodeBuild resource

Steps to Reproduce

1.) I initialize a module:

module "build" {
  source     = "cloudposse/cicd/aws"
  attributes = (concat(var.attributes, ["codepipeline"]))
  namespace  = var.namespace
  stage      = var.stage
  name       = var.name
  enabled    = var.codepipeline_enabled

  # Application repository on GitHub
  github_oauth_token = var.codepipeline_github_token
  repo_owner         = var.codepipeline_repo_owner
  repo_name          = var.codepipeline_repo_name
  branch             = var.codepipeline_branch
}

2.) I commit and push.

3.) Terraform Cloud gives this error:

│ Error: cache location is required when cache type is "S3"
│ 
│   with module.landing_page.module.build.module.codebuild.aws_codebuild_project.default[0],
│   on .terraform/modules/landing_page.build.codebuild/main.tf line 265, in resource "aws_codebuild_project" "default":
│  265: resource "aws_codebuild_project" "default" {
│ 
╵

Environment (please complete the following information):

Using Terraform v1.0.0 in Terraform Cloud

Add support for VPC, subnet and security group configuration

https://aws.amazon.com/blogs/devops/access-resources-in-a-vpc-from-aws-codebuild-builds/

Support for label_order

Would be nice to see support for the label_order variable, to be passed on to the terraform-null-label. In fact, would be sweet to have this in all of the sweetops modules, as the naming convention gets messed up if you mix your own modules with those that doesn't support it (unless using the defaults of course).

Option for deploying to website S3 bucket

Currently there's only a ZIP deployed to the build output bucket. To accept a separate bucket where the extracted files will be deployed after each build.

How to attach aws_lb_target_group to load balancer

I am trying to add some target groups to my load balancer, however I can't see a logical way to do so. I am aware that I could create a listener on the lb using aws_lb_listener.

Is there a way to do so using Terraform? Thanks.

Add Example Usage

what

• Add example invocation

why

• We need this so we can soon enable automated continuous integration testing of module

Dependabot can't parse your main.tf

Dependabot couldn't parse the main.tf found at /main.tf.

The error Dependabot encountered was:

unable to parse HCL: At 9:16: Unknown token: 9:16 IDENT var.enabled

View the update logs.

Dependabot can't parse your context.tf

Dependabot couldn't parse the context.tf found at /context.tf.

The error Dependabot encountered was:

unable to parse HCL: At 25:25: Unknown token: 25:25 IDENT var.enabled

View the update logs.

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Dependabot can't parse your main.tf

Dependabot couldn't parse the main.tf found at /main.tf.

You can mention @dependabot in the comments below to contact the Dependabot team.

Phase context status code: Decrypted Variables Error Message: parameter does not exist: ghp_...

Describe the Bug

[Container] 2022/11/23 03:53:37 Processing environment variables
[Container] 2022/11/23 03:53:37 Decrypting parameter store environment variables
[Container] 2022/11/23 03:53:39 Phase complete: DOWNLOAD_SOURCE State: FAILED
[Container] 2022/11/23 03:53:39 Phase context status code: Decrypted Variables Error Message: parameter does not exist: ghp_...

Expected Behavior

I expected the build to finish without errors.

Steps to Reproduce

Use the following code:

module "build" {
  source = "cloudposse/cicd/aws"
  version = "v0.19.5"
  namespace           = "eg"
  stage               = "staging"
  name                = "backend-app"

  # Enable the pipeline creation
  enabled             = true

  # Elastic Beanstalk
  elastic_beanstalk_application_name = "backend-app"
  elastic_beanstalk_environment_name = "dev"

  # Application repository on GitHub
  github_oauth_token  = "ghp_..."
  repo_owner          = "cloudposse"
  repo_name           = "backend-app"
  branch              = "development"

  # http://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref.html
  # http://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html
  build_image         = "aws/codebuild/standard:2.0"
  build_compute_type  = "BUILD_GENERAL1_SMALL"
}

codestar_connection_arn (Github Version 2) not working.

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature

Cannot use codestar_connection_arn to authenticate to Github as source for CICD static website. Must use (Github Version 1) and manually log in inside console after deployment.

Works perfectly with:
module "ecs_codepipeline" {
source = "cloudposse/ecs-codepipeline/aws"
codestar_connection_arn = var.codestar_connection_arn

A clear and concise description of what the bug is.

Expected Behavior

Doesn't seem to be coded in .terraform

A clear and concise description of what you expected to happen.

Use Case

Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.

Describe Ideal Solution

A clear and concise description of what you want to happen. If you don't know, that's okay.

Alternatives Considered

Explain what alternative solutions or features you've considered.

Additional Context

Add any other context or screenshots about the feature request here.

Use New CodeBuild Local Cache

AWS CI/CD is awesome, with the one drawback of the slow builds when docker image is being built. I saw that AWS recently released this blogpost about the new Local Cache feature.

I think it can be simple and awesome to see it also part of this Terraform module

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update terraform cloudposse/codebuild/aws to v2.0.2
• chore(deps): update terraform cloudposse/repository-webhooks/github to v0.14.0

Detected dependencies

terraform

examples/complete/main.tf

examples/complete/versions.tf

• aws >= 5.0
• random >= 2.1
• hashicorp/terraform >= 1.3

main.tf

• cloudposse/codebuild/aws 2.0.1
• cloudposse/repository-webhooks/github 0.12.1

versions.tf

• aws >= 5.0
• random >= 2.1
• hashicorp/terraform >= 1.3

---

• Check this box to trigger a request for Renovate to run again on this repository

Add support for terraform > v0.12

Describe the Bug

I'm not able to run this module on terraform 0.13.5.

Expected Behavior

The versions.tf file seems to suggest that this should be possible.

Steps to Reproduce

Try running the example module with terraform 0.13.5.

Screenshots

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• OS: Linux
• Version 0.13.5