This Guidance demonstrates how to import first party data from third party sources to Amazon Simple Storage Service (Amazon S3), and then upload and query your data directly to Amazon Marketing Cloud (AMC).
Data is stored in an Amazon Simple Storage Service (Amazon S3) bucket to be normalized and transformed for ingestion into Amazon Marketing Cloud (AMC).
An AMC Data Uploader can create a dataset schema, transform, and normalize your data, and upload directly to AMC using the AMC API.
Data can now be queried within the AMC UI and the AMC API.
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 provides multiple ways to connect and import your data. Each connector has its own method for responding to incidents and events that are sheltered from each other, allowing you to safely operate the Guidance and respond to incidents and events.
AWS Identity and Access Management (IAM) policies are created using the least-privilege access so that every policy is restricted to the specific resource and operation. Amazon S3 bucket policies are used to ensure only the relevant services and entities can access the data stored. The data at rest in Amazon S3 is encrypted using Amazon S3 managed keys (SSE-S3). Data transferred externally is encrypted using SSL.
This Guidance demonstrates how to connect data between multiple systems using Amazon S3, a highly available global service resilient to failures. Each connector that is used as part of this Guidance implements its own unique architecture and changes to each connector are kept separate. Amazon S3 uses AWS CloudTrail and Amazon CloudWatch to monitor access and relevant alarms, logs, and metrics. Data stored in Amazon S3 can be backed up using lifecycle policies, versioning, or replicated to other Amazon S3 buckets.
Amazon S3 is a cost-effective storage solution requiring the least level of effort to operate. The Guidance will help you experiment and test each connector to determine the best method for bringing your data into Amazon Marketing Cloud. All levels of traffic and access patterns are supported with this Guidance to meet the needs of your workloads.
The services selected for this Guidance are a cost-effective solution that require the least amount of management using serverless and managed services. Data is only transferred into Amazon S3 or to the Amazon Marketing Cloud in the same region.
With Amazon S3, this Guidance only uses the minimal number of services, allowing you to select other connectors to build your own data pipelines. IAM and Amazon S3 policies provide least-privilege access. You configure Amazon S3 lifecycle management rules based on your requirements.
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.
Amazon Marketing Cloud Uploader from AWS
Deploy this solution to easily upload first-party signals into Amazon Marketing Cloud (AMC) for evaluating and planning advertising campaigns.
Audience Uploader from AWS Clean Rooms
Deploy this solution to upload outputs more easily from AWS Clean Rooms into third-party advertising platforms.
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.