Skip to content
Modules for managing static assets (CSS, JS, images) in GCP
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Bump versions Jun 7, 2019
examples tf12 syntax Jun 7, 2019
modules Enable custom kms key for encrypting buckets Jun 7, 2019
test Restore correct DNS settings Jun 7, 2019
.gitignore Initial commit. Feb 25, 2019
.pre-commit-config.yaml Initial commit. Feb 25, 2019
CODEOWNERS Initial commit. Feb 25, 2019 [skip ci] Found more links May 9, 2019 Initial commit. Feb 25, 2019
LICENSE.txt Update LICENSE.txt Feb 25, 2019 Initial commit. Feb 25, 2019 Add badge Jun 4, 2019 tf12 syntax Jun 7, 2019 tf12 syntax Jun 7, 2019 Fix resource count issue Jun 7, 2019

Maintained by GitHub tag (latest SemVer) Terraform Version

Static Assets Modules

This repo contains modules for managing static assets (CSS, JS, images) in GCP.


If you want to quickly launch a static website using Google Cloud Storage, you can run the example that is in the root of this repo. Check out the cloud-storage-static-website example documentation for instructions.

What's in this repo

This repo has the following folder structure:

Who maintains this Module?

This Module and its Submodules are maintained by Gruntwork. Read the Gruntwork Philosophy document to learn more about how Gruntwork builds production grade infrastructure code. If you are looking for help or commercial support, send an email to

Gruntwork can help with:

  • Setup, customization, and support for this Module.
  • Modules and submodules for other types of infrastructure, such as VPCs, Docker clusters, databases, and continuous integration.
  • Modules and Submodules that meet compliance requirements, such as HIPAA.
  • Consulting & Training on GCP, AWS, Terraform, and DevOps.

How do I contribute to this Module?

Contributions are very welcome! Check out the Contribution Guidelines for instructions.

How is this Module versioned?

This Module follows the principles of Semantic Versioning. You can find each new release, along with the changelog, in the Releases Page.

During initial development, the major version will be 0 (e.g., 0.x.y), which indicates the code does not yet have a stable API. Once we hit 1.0.0, we will make every effort to maintain a backwards compatible API and use the MAJOR, MINOR, and PATCH versions on each release to indicate any incompatibilities.


Please see LICENSE.txt for details on how the code in this repo is licensed.

You can’t perform that action at this time.