Landing Zone

Google Cloud landing zone platform to run scalable, production-ready enterprise workloads.

A modular and scalable configuration that enables organizations to adopt Google Cloud for their business needs. A landing zone is a prerequisite to deploying enterprise workloads in a cloud environment.

Service Interfaces 🔩

• Add or update Terraform backend

• Add or update Kubernetes networking resources

• Add or update identity group

• Add or update folder

Response Times 🕙

• Responsible team: Platform - Google Cloud Landing Zone

• Response time for incidents: 60 minutes

• Response time for other incidents: 120 minutes

• Response time for support: 60 minutes

• Response time for feedback: 30 minutes

Roadmap 🗺️

• Link to the roadmap: GitHub Project

Communication Channels 🗨️

Possible incident

Contact exclusively via:

• Discord: Platform - Google Cloud Landing Zone

• Phone number:

Support or provide feedback

Contact via any of these:

• Discord: Platform - Google Cloud Landing Zone

• Email address: [e-mail]

• Phone number:

• Office hours (EST): Weekdays 5:00PM - 10:00PM Weekends 8:00AM - 5:00PM

Platform Modules 🏗️

Audit Logging

This repository manages centralized audit logging resources. Google Cloud services write audit logs that record administrative activities and access within your Google Cloud resources. Audit logs help you answer "who did what, where, and when?" within your Google Cloud organization.

Resource Hierarchy and IAM

This repository manages a resource hierarchy and IAM. Metaphorically speaking, the Google Cloud resource hierarchy resembles the file system found in traditional operating systems to organize and manage entities hierarchically. Identity and Access Management (IAM) lets administrators authorize who can take action on specific resources, giving you complete control and visibility to manage Google Cloud resources centrally.

Kitchen-Terraform Testing Resources

This repository manages a project for Kitchen-Terraform to test Terraform child modules. It also creates any required infrastructure to run the tests. Kitchen-Terraform provides a set of Test Kitchen plugins that enable the use of Test Kitchen to converge a Terraform configuration and verify the resulting infrastructure systems with InSpec controls.

Networking

This repository manages network resources like VPC, subnet, DNS, and NAT that can be shared across an organization.

Terraform Backend

This repository manages the Terraform backend for state management. Terraform uses persisted state data to keep track of the resources it manages. Most non-trivial Terraform configurations use a backend to store state remotely. This lets multiple people access the state data and work together on that collection of infrastructure resources. Terraform uses persisted state data to keep track of the resources it manages. Most non-trivial Terraform configurations use a backend to store state remotely. This lets multiple people access the state data and work together on that collection of infrastructure resources.

Workload Identity

This repository configures workload identity federation. With workload identity federation, you can use Identity and Access Management (IAM) to grant external identities IAM roles, including the ability to impersonate service accounts. This lets you access resources directly using a short-lived access token and eliminates the maintenance and security burden associated with service account keys.