REST Container

Overview of the REST Container, which is a Kubernetes-based solution to perform security operations using REST APIs in a native cloud environment.

The following sections outline the business problems faced by customers in protecting their data in a native cloud environment. It then lists the Protegrity solution to this business problem using REST APIs in a Kubernetes cluster.

Business Problem

A company faces the following problems in protecting data in a native cloud environment:

  • Protegrity customers are moving to the cloud. This includes data and workloads in support of transactional application and analytical systems.
  • It is impossible to keep up with the continual change in workloads by provisioning Protegrity products manually.
  • Native Cloud capabilities can be used to solve this problem and deliver the agility and scalability required to keep up with the customers’ business.
  • Kubernetes can be configured with Protegrity data security components that can leverage the autoscaling capabilities of Kubernetes to scale.

Protegrity Solution

The Protegrity REST Container provides a robust and scalable REST API designed to simplify integration of Protegrity functions across your systems. Whether you are building custom applications, streamlining workflows, or enabling third-party access, our API offers secure, reliable, and well-documented endpoints to help you achieve your goals efficiently. With support for standard HTTP methods and JSON payloads, developers can quickly get started.

The Protegrity REST Container has the following characteristics:

  • Cloud standard form factor:
    • The delivery form factor for cloud deployments is an SDK and a supporting Dockerfile. Customers can use this Dockerfile to build the REST Container, which is based on the Application Protector form factor that Protegrity have been delivering for several years.
    • The REST Container is a standard Docker Container that is familiar and expected in cloud deployments.
    • The REST Container form factor makes the container a lightweight deployment of Application Protector REST.
  • Support for Dynamic and Static deployment:
    • Dynamic deployment: The dynamic term refers to runtime updates to policy changes are applied to the cluster. Dynamic updates are managed by the Resilient Protector Proxy (RPProxy or RPP). The RPP is connected to the ESA and applies the policy changes to REST containers.
    • Static deployment: This deployment is suitable where a fixed policy configuration is required for the REST container. A secure policy package is created using the ESA API. The policy package is secured using Cloud-based Key Management Solution (KMS). The same policy package is applied to all the REST containers in the cluster.

Understanding the Architecture

Overview of the REST Container architecture.

System Requirements

Overview of the system requirements.

Preparing the Environment

Preparing the environment for deploying the protector.

Installing the Protector

Deploying the REST Container using Static or Dynamic method.

Application Protector API on REST

Describes the AP REST protector APIs that are available for protection and unprotection of data.

Using Samples

Explains details and usage of the components included in the REST-Samples_Linux-ALL-ALL_x86-64_<AP-REST_version>.tgz archive.

Running the Autoscaling Script

Provides an overview on the Autoscaling script.

Upgrading the Protector from Version 9.x to 10.x

Explains how to upgrade the protector from version 9.x to 10.x.

Upgrading the Protector from Version 10.x to 10.y

Explains how to perform rolling upgrades and roll backs for the REST container.

Using Dockerfiles to Build Custom Images

Explains how to use the Dockerfiles to build a custom image for the AP-REST container.

Appendix - Deploying the Helm Charts by Using the Set Argument

You can deploy the Helm charts by using the set argument at runtime instead of manually updating the Helm chart.


Last modified : January 18, 2026