staging.cloudposse.co

Terraform/Kubernetes Reference Infrastructure for Cloud Posse Staging Organization in AWS.

NOTE: Before creating the Production infrastructure, you need to provision the Parent ("Root") Organization in AWS (because it creates resources needed for all other accounts). Follow the steps in README first. You need to do it only once.

---

This project is part of our comprehensive "SweetOps" approach towards DevOps.

It's 100% Open Source and licensed under the APACHE2.

Introduction

We use geodesic to define and build world-class cloud infrastructures backed by AWS and powered by Kubernetes.

geodesic exposes many tools that can be used to define and provision AWS and Kubernetes resources.

Here is the list of tools we use to provision cloudposse.co infrastructure:

• aws-vault
• chamber
• terraform
• kops
• kubectl
• helm
• helmfile

Quick Start

Setup AWS Role

NOTE: You need to do it only once.

Configure AWS profile in ~/.aws/config. Make sure to change username (username@cloudposse.co) to your own.

[profile cpco-staging-admin]
region=us-west-2
role_arn=arn:aws:iam::781281608584:role/OrganizationAccountAccessRole
mfa_serial=arn:aws:iam::323330167063:mfa/username@cloudposse.co
source_profile=cpco

Install and setup aws-vault

NOTE: You need to do it only once.

We use aws-vault to store IAM credentials in your operating system's secure keystore and then generates temporary credentials from those to expose to your shell and applications.

Install aws-vault on your local computer first.

On MacOS, you may use homebrew cask

brew cask install aws-vault

Then setup your secret credentials for AWS in aws-vault

aws-vault add --backend file cpco

NOTE: You should set AWS_VAULT_BACKEND=file in your shell rc config (e.g. ~/.bashrc) so it persists.

For more info, see aws-vault

Examples

Build Docker Image

# Initialize the project's build-harness
make init

# Build docker image
make docker/build

Install the wrapper shell

make install

Run the shell

staging.cloudposse.co

Login to AWS with your MFA device

assume-role

Populate chamber secrets

NOTE: You need to do it only once for a given set of secrets. Repeat this step if you want to add new secrets.

Populate chamber secrets for kops project (make sure to change the keys and values to reflect your environment; add new secrets as needed)

chamber write kops <key1> <value1>
chamber write kops <key2> <value2>
...

NOTE: Run chamber list -e kops to list the secrets stored for kops project

Populate chamber secrets for backing-services project (make sure to change the values to reflect your environment; add new secrets as needed)

chamber write backing-services TF_VAR_POSTGRES_ADMIN_NAME admin
chamber write backing-services TF_VAR_POSTGRES_ADMIN_PASSWORD supersecret
chamber write backing-services TF_VAR_POSTGRES_DB_NAME app

NOTE: Run chamber list -e backing-services to list the secrets stored for backing-services project

NOTE: Before provisioning AWS resources with Terraform, you need to create tfstate-backend first (S3 bucket to store Terraform state and DynamoDB table for state locking).

Follow the steps in this README. You need to do it only once.

After tfstate-backend has been provisioned, follow the rest of the instructions in the order shown below.

Provision dns with Terraform

Change directory to dns folder

cd /conf/dns

Run Terraform

init-terraform
terraform plan
terraform apply

For more info, see geodesic-with-terraform

Provision cloudtrail with Terraform

cd /conf/cloudtrail
init-terraform
terraform plan
terraform apply

Provision acm with Terraform

cd /conf/acm
init-terraform
terraform plan
terraform apply

Provision chamber with Terraform

cd /conf/chamber
init-terraform
terraform plan
terraform apply

Makefile Targets

Available targets:

  all                                 Initialize build-harness, install deps, build docker container, install wrapper script and run shell
  build                               Build docker image
  deps                                Install dependencies (if any)
  help                                This help screen
  help/all                            Display help for all targets
  install                             Install wrapper script from geodesic container
  push                                Push docker image to registry
  run                                 Start the geodesic shell by calling wrapper script

Related Projects

Check out these related projects.

• Packages - Cloud Posse installer and distribution of native apps
• Build Harness - Collection of Makefiles to facilitate building Golang projects, Dockerfiles, Helm charts, and more
• terraform-root-modules - Collection of Terraform "root module" invocations for provisioning reference architectures
• root.cloudposse.co - Example Terraform Reference Architecture of a Geodesic Module for a Parent ("Root") Organization in AWS.
• audit.cloudposse.co - Example Terraform Reference Architecture of a Geodesic Module for an Audit Logs Organization in AWS.
• prod.cloudposse.co - Example Terraform Reference Architecture of a Geodesic Module for a Production Organization in AWS.
• dev.cloudposse.co - Example Terraform Reference Architecture of a Geodesic Module for a Development Sandbox Organization in AWS.
• testing.cloudposse.co - Example Terraform Reference Architecture of a Geodesic Module for a Testing Organization in AWS.

References

For additional context, refer to some of these links.

• Cloud Posse Documentation - Complete documentation for the Cloud Posse solution
• Chamber - Chamber is a CRUD tool for managing secrets stored in AWS Systems Manager Parameter Store and exposing those secrets as Environment Variables to processes.
• The Right Way to Store Secrets using Parameter Store - Centrally and securely manage secrets with Amazon EC2 Systems Manager Parameter Store, lots of Terraform code, and chamber. This post has all the information you need to get running with Parameter Store in production.
• external-dns - Frequently asked Questions & Answers

Help

Got a question?

File a GitHub issue, send us an email or join our Slack Community.

Commerical Support

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We provide commercial support for all of our Open Source projects. As a Dedicated Support customer, you have access to our team of subject matter experts at a fraction of the cost of a fulltime engineer.

• Questions. We'll use a Shared Slack channel between your team and ours.
• Troubleshooting. We'll help you triage why things aren't working.
• Code Reviews. We'll review your Pull Requests and provide constructive feedback.
• Bug Fixes. We'll rapidly work to fix any bugs in our projects.
• Build New Terraform Modules. We'll develop original modules to provision infrastructure.
• Cloud Architecture. We'll assist with your cloud strategy and design.
• Implementation. We'll provide hands on support to implement our reference architectures.

Community Forum

Get access to our Open Source Community Forum on Slack. It's FREE to join 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 sweet infrastructure.

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

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

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. 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!

Copyright

Copyright © 2017-2018 Cloud Posse, LLC

License

See LICENSE for full details.

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.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know at hello@cloudposse.com

We're a DevOps Professional Services company based in Los Angeles, CA. We love Open Source Software!

We offer paid support on all of our projects.

Check out our other projects, apply for a job, or hire us to help with your cloud strategy and implementation.