diff --git a/dataproc_metastore_service_scheduled_backup/backing_file.tf b/dataproc_metastore_service_scheduled_backup/backing_file.tf
new file mode 100644
index 00000000..c60b1199
--- /dev/null
+++ b/dataproc_metastore_service_scheduled_backup/backing_file.tf
@@ -0,0 +1,15 @@
+# This file has some scaffolding to make sure that names are unique and that
+# a region and zone are selected when you try to create your Terraform resources.
+
+locals {
+ name_suffix = "${random_pet.suffix.id}"
+}
+
+resource "random_pet" "suffix" {
+ length = 2
+}
+
+provider "google" {
+ region = "us-central1"
+ zone = "us-central1-c"
+}
diff --git a/dataproc_metastore_service_scheduled_backup/main.tf b/dataproc_metastore_service_scheduled_backup/main.tf
new file mode 100644
index 00000000..ebba1289
--- /dev/null
+++ b/dataproc_metastore_service_scheduled_backup/main.tf
@@ -0,0 +1,31 @@
+resource "google_dataproc_metastore_service" "backup" {
+ service_id = "backup-${local.name_suffix}"
+ location = "us-central1"
+ port = 9080
+ tier = "DEVELOPER"
+
+ maintenance_window {
+ hour_of_day = 2
+ day_of_week = "SUNDAY"
+ }
+
+ hive_metastore_config {
+ version = "2.3.6"
+ }
+
+ scheduled_backup {
+ enabled = true
+ cron_schedule = "0 0 * * *"
+ time_zone = "UTC"
+ backup_location = "gs://${google_storage_bucket.bucket.name}"
+ }
+
+ labels = {
+ env = "test"
+ }
+}
+
+resource "google_storage_bucket" "bucket" {
+ name = "backup-${local.name_suffix}"
+ location = "us-central1"
+}
diff --git a/dataproc_metastore_service_scheduled_backup/motd b/dataproc_metastore_service_scheduled_backup/motd
new file mode 100644
index 00000000..45a906e8
--- /dev/null
+++ b/dataproc_metastore_service_scheduled_backup/motd
@@ -0,0 +1,7 @@
+===
+
+These examples use real resources that will be billed to the
+Google Cloud Platform project you use - so make sure that you
+run "terraform destroy" before quitting!
+
+===
diff --git a/dataproc_metastore_service_scheduled_backup/tutorial.md b/dataproc_metastore_service_scheduled_backup/tutorial.md
new file mode 100644
index 00000000..9ac7d909
--- /dev/null
+++ b/dataproc_metastore_service_scheduled_backup/tutorial.md
@@ -0,0 +1,79 @@
+# Dataproc Metastore Service Scheduled Backup - Terraform
+
+## Setup
+
+
+
+Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
+
+
+
+Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
+
+## Terraforming!
+
+Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
+to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
+the project name from the environment variable.
+
+```bash
+export GOOGLE_CLOUD_PROJECT={{project-id}}
+```
+
+After that, let's get Terraform started. Run the following to pull in the providers.
+
+```bash
+terraform init
+```
+
+With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
+
+```bash
+terraform apply
+```
+
+Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
+
+```bash
+yes
+```
+
+
+## Post-Apply
+
+### Editing your config
+
+Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
+
+```bash
+terraform plan
+```
+
+So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
+run a 'plan' again.
+
+```bash
+terraform plan
+```
+
+Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
+at the 'yes' prompt.
+
+```bash
+terraform apply
+```
+
+```bash
+yes
+```
+
+## Cleanup
+
+Run the following to remove the resources Terraform provisioned:
+
+```bash
+terraform destroy
+```
+```bash
+yes
+```
diff --git a/integrations_client_advance/backing_file.tf b/integrations_client_advance/backing_file.tf
new file mode 100644
index 00000000..c60b1199
--- /dev/null
+++ b/integrations_client_advance/backing_file.tf
@@ -0,0 +1,15 @@
+# This file has some scaffolding to make sure that names are unique and that
+# a region and zone are selected when you try to create your Terraform resources.
+
+locals {
+ name_suffix = "${random_pet.suffix.id}"
+}
+
+resource "random_pet" "suffix" {
+ length = 2
+}
+
+provider "google" {
+ region = "us-central1"
+ zone = "us-central1-c"
+}
diff --git a/integrations_client_advance/main.tf b/integrations_client_advance/main.tf
new file mode 100644
index 00000000..e4b8e1e8
--- /dev/null
+++ b/integrations_client_advance/main.tf
@@ -0,0 +1,34 @@
+data "google_project" "test_project" {
+}
+
+resource "google_kms_key_ring" "keyring" {
+ name = "my-keyring-${local.name_suffix}"
+ location = "us-central1"
+}
+
+resource "google_kms_crypto_key" "cryptokey" {
+ name = "crypto-key-example"
+ key_ring = google_kms_key_ring.keyring.id
+ rotation_period = "7776000s"
+ depends_on = [google_kms_key_ring.keyring]
+}
+
+resource "google_kms_crypto_key_version" "test_key" {
+ crypto_key = google_kms_crypto_key.cryptokey.id
+ depends_on = [google_kms_crypto_key.cryptokey]
+}
+
+resource "google_integrations_client" "example" {
+ location = "us-central1"
+ create_sample_workflows = true
+ provision_gmek = true
+ run_as_service_account = "radndom-service-account"
+ cloud_kms_config {
+ kms_location = "us-central1"
+ kms_ring = google_kms_key_ring.keyring.id
+ key = google_kms_crypto_key.cryptokey.id
+ key_version = google_kms_crypto_key_version.test_key.id
+ kms_project_id = data.google_project.test_project.id
+ }
+ depends_on = [google_kms_crypto_key_version.test_key]
+}
diff --git a/integrations_client_advance/motd b/integrations_client_advance/motd
new file mode 100644
index 00000000..45a906e8
--- /dev/null
+++ b/integrations_client_advance/motd
@@ -0,0 +1,7 @@
+===
+
+These examples use real resources that will be billed to the
+Google Cloud Platform project you use - so make sure that you
+run "terraform destroy" before quitting!
+
+===
diff --git a/integrations_client_advance/tutorial.md b/integrations_client_advance/tutorial.md
new file mode 100644
index 00000000..021b9f0d
--- /dev/null
+++ b/integrations_client_advance/tutorial.md
@@ -0,0 +1,79 @@
+# Integrations Client Advance - Terraform
+
+## Setup
+
+
+
+Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
+
+
+
+Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
+
+## Terraforming!
+
+Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
+to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
+the project name from the environment variable.
+
+```bash
+export GOOGLE_CLOUD_PROJECT={{project-id}}
+```
+
+After that, let's get Terraform started. Run the following to pull in the providers.
+
+```bash
+terraform init
+```
+
+With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
+
+```bash
+terraform apply
+```
+
+Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
+
+```bash
+yes
+```
+
+
+## Post-Apply
+
+### Editing your config
+
+Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
+
+```bash
+terraform plan
+```
+
+So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
+run a 'plan' again.
+
+```bash
+terraform plan
+```
+
+Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
+at the 'yes' prompt.
+
+```bash
+terraform apply
+```
+
+```bash
+yes
+```
+
+## Cleanup
+
+Run the following to remove the resources Terraform provisioned:
+
+```bash
+terraform destroy
+```
+```bash
+yes
+```
diff --git a/integrations_client_basic/backing_file.tf b/integrations_client_basic/backing_file.tf
new file mode 100644
index 00000000..c60b1199
--- /dev/null
+++ b/integrations_client_basic/backing_file.tf
@@ -0,0 +1,15 @@
+# This file has some scaffolding to make sure that names are unique and that
+# a region and zone are selected when you try to create your Terraform resources.
+
+locals {
+ name_suffix = "${random_pet.suffix.id}"
+}
+
+resource "random_pet" "suffix" {
+ length = 2
+}
+
+provider "google" {
+ region = "us-central1"
+ zone = "us-central1-c"
+}
diff --git a/integrations_client_basic/main.tf b/integrations_client_basic/main.tf
new file mode 100644
index 00000000..3f71ec00
--- /dev/null
+++ b/integrations_client_basic/main.tf
@@ -0,0 +1,3 @@
+resource "google_integrations_client" "example" {
+ location = "us-central1"
+}
diff --git a/integrations_client_basic/motd b/integrations_client_basic/motd
new file mode 100644
index 00000000..45a906e8
--- /dev/null
+++ b/integrations_client_basic/motd
@@ -0,0 +1,7 @@
+===
+
+These examples use real resources that will be billed to the
+Google Cloud Platform project you use - so make sure that you
+run "terraform destroy" before quitting!
+
+===
diff --git a/integrations_client_basic/tutorial.md b/integrations_client_basic/tutorial.md
new file mode 100644
index 00000000..2b049c34
--- /dev/null
+++ b/integrations_client_basic/tutorial.md
@@ -0,0 +1,79 @@
+# Integrations Client Basic - Terraform
+
+## Setup
+
+
+
+Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
+
+
+
+Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
+
+## Terraforming!
+
+Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
+to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
+the project name from the environment variable.
+
+```bash
+export GOOGLE_CLOUD_PROJECT={{project-id}}
+```
+
+After that, let's get Terraform started. Run the following to pull in the providers.
+
+```bash
+terraform init
+```
+
+With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
+
+```bash
+terraform apply
+```
+
+Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
+
+```bash
+yes
+```
+
+
+## Post-Apply
+
+### Editing your config
+
+Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
+
+```bash
+terraform plan
+```
+
+So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
+run a 'plan' again.
+
+```bash
+terraform plan
+```
+
+Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
+at the 'yes' prompt.
+
+```bash
+terraform apply
+```
+
+```bash
+yes
+```
+
+## Cleanup
+
+Run the following to remove the resources Terraform provisioned:
+
+```bash
+terraform destroy
+```
+```bash
+yes
+```
diff --git a/pubsub_topic_ingestion_kinesis/backing_file.tf b/pubsub_topic_ingestion_kinesis/backing_file.tf
new file mode 100644
index 00000000..c60b1199
--- /dev/null
+++ b/pubsub_topic_ingestion_kinesis/backing_file.tf
@@ -0,0 +1,15 @@
+# This file has some scaffolding to make sure that names are unique and that
+# a region and zone are selected when you try to create your Terraform resources.
+
+locals {
+ name_suffix = "${random_pet.suffix.id}"
+}
+
+resource "random_pet" "suffix" {
+ length = 2
+}
+
+provider "google" {
+ region = "us-central1"
+ zone = "us-central1-c"
+}
diff --git a/pubsub_topic_ingestion_kinesis/main.tf b/pubsub_topic_ingestion_kinesis/main.tf
new file mode 100644
index 00000000..5206dfe8
--- /dev/null
+++ b/pubsub_topic_ingestion_kinesis/main.tf
@@ -0,0 +1,13 @@
+resource "google_pubsub_topic" "example" {
+ name = "example-topic-${local.name_suffix}"
+
+ # Outside of automated terraform-provider-google CI tests, these values must be of actual AWS resources for the test to pass.
+ ingestion_data_source_settings {
+ aws_kinesis {
+ stream_arn = "arn:aws:kinesis:us-west-2:111111111111:stream/fake-stream-name"
+ consumer_arn = "arn:aws:kinesis:us-west-2:111111111111:stream/fake-stream-name/consumer/consumer-1:1111111111"
+ aws_role_arn = "arn:aws:iam::111111111111:role/fake-role-name"
+ gcp_service_account = "fake-service-account@fake-gcp-project.iam.gserviceaccount.com"
+ }
+ }
+}
diff --git a/pubsub_topic_ingestion_kinesis/motd b/pubsub_topic_ingestion_kinesis/motd
new file mode 100644
index 00000000..45a906e8
--- /dev/null
+++ b/pubsub_topic_ingestion_kinesis/motd
@@ -0,0 +1,7 @@
+===
+
+These examples use real resources that will be billed to the
+Google Cloud Platform project you use - so make sure that you
+run "terraform destroy" before quitting!
+
+===
diff --git a/pubsub_topic_ingestion_kinesis/tutorial.md b/pubsub_topic_ingestion_kinesis/tutorial.md
new file mode 100644
index 00000000..7368380a
--- /dev/null
+++ b/pubsub_topic_ingestion_kinesis/tutorial.md
@@ -0,0 +1,79 @@
+# Pubsub Topic Ingestion Kinesis - Terraform
+
+## Setup
+
+
+
+Welcome to Terraform in Google Cloud Shell! We need you to let us know what project you'd like to use with Terraform.
+
+
+
+Terraform provisions real GCP resources, so anything you create in this session will be billed against this project.
+
+## Terraforming!
+
+Let's use {{project-id}} with Terraform! Click the Cloud Shell icon below to copy the command
+to your shell, and then run it from the shell by pressing Enter/Return. Terraform will pick up
+the project name from the environment variable.
+
+```bash
+export GOOGLE_CLOUD_PROJECT={{project-id}}
+```
+
+After that, let's get Terraform started. Run the following to pull in the providers.
+
+```bash
+terraform init
+```
+
+With the providers downloaded and a project set, you're ready to use Terraform. Go ahead!
+
+```bash
+terraform apply
+```
+
+Terraform will show you what it plans to do, and prompt you to accept. Type "yes" to accept the plan.
+
+```bash
+yes
+```
+
+
+## Post-Apply
+
+### Editing your config
+
+Now you've provisioned your resources in GCP! If you run a "plan", you should see no changes needed.
+
+```bash
+terraform plan
+```
+
+So let's make a change! Try editing a number, or appending a value to the name in the editor. Then,
+run a 'plan' again.
+
+```bash
+terraform plan
+```
+
+Afterwards you can run an apply, which implicitly does a plan and shows you the intended changes
+at the 'yes' prompt.
+
+```bash
+terraform apply
+```
+
+```bash
+yes
+```
+
+## Cleanup
+
+Run the following to remove the resources Terraform provisioned:
+
+```bash
+terraform destroy
+```
+```bash
+yes
+```