Get Started with Google Cloud — selected guide
How to classify and redact sensitive data
Twelve practical entries spanning docs, networking, storage, IAM, cost, data, workflows, and APIs
Twelve 2018–2022 introductions use small tasks to explain networking, persistent storage, access control, BigQuery queries and cost limits, object versions, sensitive-data inspection, workflow orchestration, and speech transcription.
Google Cloud Tech 10 of 12
In this collection Browse 12 summaries 10 of 12
This Node.js example sends text to the Data Loss Prevention (DLP) API to find potentially sensitive information. Despite the title, it detects a name and email address; it does not redact them. 00:01–02:45(opens in a new tab)
Key Points Covered
- The setup enables the API and gives a service account the Cloud DLP User role. The local sample uses that account's credentials to authenticate its requests. 00:01–02:06(opens in a new tab)
- The Node.js path clones sample code, installs the client library, and supplies a project ID through an environment variable. 01:03–02:06(opens in a new tab)
- Running
inspectString.jsprints findings to the console. The result identifies potentially sensitive text rather than returning a version with that text removed or masked. 02:06–02:45(opens in a new tab)
Full video: https://www.youtube.com/watch?v=LxDHd0MsFXI(opens in a new tab)