Local SSD

Related topics

• Local SSD is part of Compute Engine From the official documentation: “Compute Engine automatically encrypts your data when it is written to Local SSD disks.”
• Local SSD is an alternative to Persistent Disk From the official documentation: “When local SSDs are provided to the cluster, both HDFS and scratch data, such as shuffle outputs, use the local SSDs instead of the boot persistent disk.”
• customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Persistent Disk is part of Compute Engine From the official documentation: “Compute Engine offers different types of persistent disks.”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Compute Engine works with Persistent Disk From the official documentation: “Add a persistent disk to Compute Engine”
• Cloud Storage is an alternative to Persistent Disk From the official documentation: “Both Persistent Disk and Cloud Storage can both be used to store files but are very different offerings.”
• customer-managed encryption keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
• Dataflow depends on Compute Engine From the official documentation: “When you run your pipeline on the Dataflow service, Dataflow creates Compute Engine instances to run your pipeline code.”
• Dataflow works with Persistent Disk From the official documentation: “By default, Dataflow selects the machine type for the worker VMs that run your job, along with the size and type of Persistent Disk.”
• customer-managed encryption keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• customer-managed encryption keys works with Dataflow From the official documentation: “This sample shows how to use encryption keys managed by the customer, with a Dataflow pipeline.”
• customer-managed encryption keys secures Dataflow From the official documentation: “You can either create CMEKs manually to protect your Dataflow resources or use Cloud KMS Autokey.”
• customer-managed encryption keys secures Persistent Disk From the official documentation: “To rotate the CMEK that's protecting a disk or snapshot, you can use either the gcloud CLI or REST; you can't use the Google Cloud console or the Terraform provider for Google Cloud.”