Content Management Using Salesforce on AWS - Technical Architecture Overview

Oct 25, 2026

This document outlines a technical architecture for integrating content management between Salesforce and Amazon Web Services (AWS). It details a 12-step process, focusing on steps 1 through 7, which utilize AWS Lambda, Amazon S3, Amazon SNS, and Amazon Rekognition to automate the ingestion, tagging, and metadata extraction of media files. The workflow begins with a client-side Salesforce Lightning Web Component (LWC) that securely interacts with AWS services, ensuring efficient media processing, object detection, and comprehensive metadata management for both video and image files within a cloud-native ecosystem. This solution is designed for organizations seeking to leverage AI and machine learning capabilities for automated media analysis within their existing Salesforce environments.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages1

Reading Time3 min

AccessFree to download

Architecture Overview

Workflow Steps 1-7

Security and Media Ingestion

Video and Image Processing Logic

FAQs

How do Salesforce users securely upload media files to Amazon S3?

Salesforce users utilize a client-side Lightning Web Component (LWC) that exchanges a JSON Web Token (JWT) for AWS Security Token Service (STS) credentials to gain necessary read/write permissions.

What initiates the media processing workflow after a file is uploaded to Amazon S3?

An Amazon Simple Notification Service (SNS) event is triggered upon file upload, which filters the file suffix to determine the appropriate topic for subsequent media processing.

How are image files processed within this AWS architecture?

An Amazon SNS topic triggers two parallel Lambda functions: one for object tagging using Amazon Rekognition and another for metadata extraction, with both outputs saved to an Amazon S3 bucket.

Oct 25, 2026

Uploaded by นรินทร์