What's the best way to build a suppression list across FB, Google, and LinkedIn?

cloud_ops_learner_99 · 2026-07-30T04:25:50Z

Hi everyone. I'm a cloud admin trying to help our marketing team with a technical problem. They run campaigns across Facebook, Google Ads, and LinkedIn and need a centralized way to build and manage suppression lists (like for users who've already converted). My first thought was an AWS setup: maybe a Lambda function to process conversion events, store the hashed/canonicalized IDs in a DynamoDB table, and then have separate functions to sync to each platform's API. But I'm nervous about the integration specifics and cost. Could anyone share a simple, real-world Terraform example for the core infrastructure? Like just the VPC, security groups, and Lambda setup? I want to make sure it's secure and doesn't get too expensive. 😅 I'm thinking something like this for a starting point, but I'm probably missing a lot: ```hcl resource "aws_lambda_function" "suppression_processor" { filename = "processor.zip" function_name = "suppression_processor" role = aws_iam_role.lambda_exec.arn handler = "index.handler" runtime = "python3.11" vpc_config { subnet_ids = [aws_subnet.private.id] security_group_ids = [aws_security_group.lambda_sg.id] } } ``` Is this even the right approach? How do you handle the different API formats and authentication securely? Any examples would be a huge help.

Page 3 / 3 Prev

Ad Platform & Tool Reviews

Last Post by crm_pragmatist 2 months ago

31 Posts

28 Users

0 Reactions

181 Views

RSS

crm_pragmatist

(@crm_pragmatist)

Reputable Member

Joined: 4 months ago

Posts: 287

31/07/2026 11:00 am

Your skeleton is okay, but you're worried about the wrong cost. The Lambda bill is nothing. The real expense is your team's hours spent making those three APIs talk.

> but I'm probably missing a lot
You are. The code you write for LinkedIn's 500 errors and Facebook's batch quirks is what matters, not your VPC. Also, strip that vpc_config block. It adds zero security for a function calling public APIs and just adds cost and complexity. Focus your Terraform on the triggers and IAM roles. Get the logic working in a script first, then wrap it.

ReplyQuote

Page 3 / 3 Prev

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed