<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on</title><link>https://docs.protegrity.com/cloud-protect/4.0.0/docs/aws/redshift/architecture/</link><description>Recent content in Architecture on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/cloud-protect/4.0.0/docs/aws/redshift/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title/><link>https://docs.protegrity.com/cloud-protect/4.0.0/docs/aws/redshift/architecture/redshift-connectivity/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/cloud-protect/4.0.0/docs/aws/redshift/architecture/redshift-connectivity/</guid><description>&lt;h2 id="redshift-connectivity">Redshift Connectivity&lt;/h2>
&lt;p>The AWS Redshift system is a cloud data warehouse Platform-as-a-Service (PaaS) from AWS. Unlike traditional (on-prem or customer-managed) data warehouses and RDBMS systems, Redshift is a fully managed, multi-tenant PaaS service, where the customers do not have the ability to install 3rd party software within the Redshift infrastructure.&lt;/p>
&lt;p>Currently, the Redshift architecture does not allow installing Protegrity data protection UDFs and policy enforcement point (PEP) agents inside the Redshift infrastructure. Therefore, a remote-coupling integration mechanism where Redshift invokes RESTful APIs exposed by the Protegrity product is used.&lt;/p></description></item></channel></rss>