Running LiveRamp’s Local Encoder in a Google Cloud Engine Virtual Machine
Local Encoder enables you to generate securely-encoded RampIDs for your consumer data files within your own cloud environment and then utilize that data for Activation or addressability use cases, depending on your needs. In this way your consumer data is never exposed to an external network, while still enabling full use of the LiveRamp solutions. The encoded RampIDs produced by the application cannot be decoded back to the original consumer identifiers.
Local Encoder can be run on any infrastructure that supports running Docker images. The Local Encoder Docker image is currently distributed via the Amazon Elastic Container Registry (ECR).
For more information on Local Encoder, including information on security, use cases, data you can send, and output options, see "LiveRamp Local Encoder".
For information on running Local Encoder in a Google Cloud Engine virtual machine, see the sections below.
Overall Steps
After you make sure all the prerequisites listed below are in place, running the Local Encoder in a Google Cloud Engine virtual machine involves the following overall steps:
Create a virtual machine in GCP.
Perform the overall steps in “Running LiveRamp’s Local Encoder In a Docker-Run Environment”.
Prerequisites
Before setting up the Local Encoder application, make sure that the GCP Instance is set up according to your infrastructure needs and is ready for use.
Running the Local Encoder in a Google Cloud Engine virtual machine requires that you have the following additional prerequisites:
A Docker installation
AWS Command Line Interface (CLI)
A PGP public key
A GCP project with access to the virtual machine.
Note
You will use the AWS command line tool to issue commands at your system's command line to perform Amazon ECR and other AWS tasks. We recommend that you have the latest version of the AWS CLI installed. For information about installing the AWS CLI or upgrading it to the latest version, see Installing the AWS Command Line Interface.
We need to maintain the same architecture, i.e., build the image to match the architecture used by the Runner.
Copy the Necessary Files to the Virtual Machine
After you’ve confirmed that all needed prerequisites are in place, use the following command to copy all the necessary files that we will use to run the Vault application and process files (such as configuration files, input and output files, etc.)that we will use to run the Vault application and process files, from the Host machine to the Vvirtual Mmachine:
gcloud compute scp /path/to/local/file username@instance-name:/path/to/destination --zone=instance-zone