Store Consent Data via AWS instead of Cloudflare

Consent Pro
,
1

We don’t have a sufficient agreement with Cloudflare to support storing PII. Is it possible to use AWS instead?

I want to verify that this new architecture is possible before requesting help:

Frontend: Finsweet sends the consent payload to an AWS API Gateway endpoint

Backend: AWS Lambda function receives the payload

Storage: Lambda writes the log to DynamoDB or S3

2

Hey @ed.pirone!

Consent Pro is built specifically for Cloudflare Workers architecture and doesn’t currently support AWS integration (API Gateway/Lambda/DynamoDB) out of the box.

The standard consent storage approach uses:

  1. Frontend: Consent Pro sends data to Cloudflare Worker endpoint
  2. Backend: Cloudflare Worker processes consent data
  3. Storage: Data stored in Cloudflare KV namespace

Your AWS architecture would require custom development since the consent storage endpoint is hardcoded for the Cloudflare Workers setup. :thinking:

You might consider if Cloudflare’s compliance agreements could work for your needs - many GDPR-compliant organizations use this approach. If AWS is mandatory, you’d need custom development to modify the consent destination, handle AWS authentication, and ensure compatibility with Lambda.

This isn’t a simple configuration change but an architectural modification requiring development expertise. :flexed_biceps: