Amazon S3 - Kentico Integration and Automation

Common Integration Use Cases Between Amazon S3 and Kentico

1. Centralized media asset delivery for Kentico websites

Data flow: Amazon S3 to Kentico

Store website images, PDFs, videos, and downloadable documents in Amazon S3 and surface them in Kentico pages, landing pages, and campaign content. This gives marketing teams a scalable repository for large media files while Kentico focuses on content presentation and personalization.

• Reduces load on the CMS by offloading large files to object storage
• Improves page performance and content delivery at scale
• Supports global distribution of assets for high-traffic campaigns

2. Automated publishing of approved campaign assets

Data flow: Kentico to Amazon S3

When marketing teams approve a campaign asset in Kentico, the file can be automatically published to Amazon S3 for distribution across websites, microsites, partner portals, or external channels. This creates a controlled handoff from content creation to scalable file hosting.

• Speeds up campaign launch cycles
• Ensures only approved assets are distributed
• Creates a consistent source of truth for published files

3. Secure document hosting for gated content and lead generation

Data flow: Amazon S3 to Kentico

Host whitepapers, product brochures, pricing sheets, and technical documents in Amazon S3, then link them to Kentico forms, landing pages, and gated content experiences. Kentico can manage the lead capture workflow while S3 provides reliable file storage and access.

• Supports lead generation campaigns with downloadable assets
• Enables secure, scalable storage for high-demand documents
• Improves operational control over content access and updates

4. Multi-site content distribution across regional or brand portals

Data flow: Bi-directional

Use Amazon S3 as a shared repository for common assets and Kentico to manage localized content experiences across multiple websites or brand portals. Regional teams can pull approved files from S3 while publishing localized pages and metadata in Kentico.

• Reduces duplication of media assets across sites
• Supports brand consistency with localized execution
• Improves governance for enterprise multi-site operations

5. Backup and archival of Kentico content assets

Data flow: Kentico to Amazon S3

Export or archive older campaign files, expired promotional assets, and historical media from Kentico to Amazon S3 for long-term retention. This helps keep the CMS lean while preserving content for compliance, audit, or reuse purposes.

• Low-cost storage for inactive assets
• Improves CMS performance and content manageability
• Supports retention and audit requirements

6. Dynamic content enrichment using S3-hosted media libraries

Data flow: Amazon S3 to Kentico

Maintain a structured media library in Amazon S3 and sync metadata into Kentico so content editors can search, filter, and insert approved assets into pages and campaigns. This is especially useful for large organizations with frequent content updates.

• Improves editor productivity and asset reuse
• Provides better control over versioned media libraries
• Helps teams avoid duplicate or outdated assets

7. Campaign asset lifecycle management

Data flow: Bi-directional

Manage the full lifecycle of campaign assets by creating and approving content in Kentico, storing final files in Amazon S3, and updating Kentico with the live asset locations and status. This enables marketing, web, and operations teams to coordinate on asset readiness, publication, and retirement.

• Improves visibility into asset status across teams
• Supports controlled publishing and retirement workflows
• Reduces manual file handling and broken links