This Guidance shows how to activate publisher first-party data from Software as a Service (SaaS) environments that support Seller Defined Audiences (SDA). It uses page content without Personally Identifiable Information (PII) to automatically map to industry standard taxonomies, returning the associated SDA identifications for activation through Real-Time Bidding (RTB).

Please note: [Disclaimer]

Architecture Diagram

Download the architecture diagram PDF 
  • Steps
  • Follow the steps in this diagram to deploy this Guidance.

  • Additional Considerations
  • Consider the following key components when deploying this Guidance.

Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

  • This Guidance uses a microservices-based approach so that components operate independently of one another, allowing you to easily integrate and deploy changes. 

    Read the Operational Excellence whitepaper 
  • IAM and AWS KMS are AWS services that you can deploy with this Guidance to protect your resources and data. IAM policies grant least privilege access to data, so that users only have the permissions required to perform a specific task. AWS KMS encrypts data at rest and in transit as an additional layer of protection against unauthorized use.

    Read the Security whitepaper 
  • Scalable services and features included in this Guidance, such as autoscaling for Amazon EKS, help you adapt to changes inherent in dynamic workloads. And the deployment pipeline implements and logs configuration changes, allowing you to roll back to a previous state in the case of a disaster.

    Read the Reliability whitepaper 
  • This Guidance allows you to deploy, update, and scale components individually to meet demand for specific functions, allowing you to experiment with this Guidance and optimize it based on your data. 

    Read the Performance Efficiency whitepaper 
  • We recommend using AWS pricing models to help reduce cost. For example, Amazon EC2 Spot Instances offer scale and cost savings for up to a 90% discount when compared to Amazon EC2 On-Demand Instances. And, Amazon EKS and DynamoDB scale based on demand, so you only pay for the resources actually used. 

    Read the Cost Optimization whitepaper 
  • By extensively using serverless services, you maximize overall resource usage because compute is used only as needed. This also reduces the overall energy required to operate your workloads. And to minimize the amount of hardware needed to provision this Guidance, AWS Graviton processors  maximize performance for workloads. 

    Read the Sustainability whitepaper 

Implementation Resources

A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.

AWS Architecture
Blog

Title

Subtitle
Text.
 
This post demonstrates how...

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.