Serverless AWS CMS

“In an age of Serverless applications and the continued rise of the Cloud, Content Management Systems (CMS) continued to be dominated by expensive legacy SaaS applications and aging open source projects.”

-- Joaquin Lippincott, CEO Metal Toad

Aging Content Management Systems (CMS) are moving into an era of increased security risk, forcing many organizations to rethink their CMS technology.  At the same time, the value brought to organizations by CMS technology has decreased significantly, with the biggest value in marketing now being found in Customer Relationship Management (CRM) systems.

New “Headless CMS” options offer substantial opportunities for cost reduction. However, the market is full of middlemen who markup underlying cloud technologies and lock in long-term licensing contracts that simply trade one paradigm for another similar one.  By going direct to the cloud — using Amazon Web Services (AWS) — CMS Product Owners, CIOs, and CMOs can reduce risk, reduce costs, and expand opportunities for new feature development.

An AWS Headless CMS is built on two primary components:

  1. AWS Services
  2. React JS

AWS Services

While there is no limit to the number or types of AWS Services that could be integrated the core of CMS is contained in AWS Amplify, a service that allows developers to quickly and seamlessly stitch together other AWS services. All of the branded headless or serverless CMS options that are available are built on some type of cloud infrastructure, and in some cases they plug directly into Amplify.  

The mapping of services to function are roughly:

With over 240 Products/Services there are literally hundreds of other integrations possible.

React JS

React is a JavaScript framework that is generally advised for building out of the front-end of other headless CMS options.  Each of the contributions to the UI layer are called Components while NPM Packages cover even broader areas like system interoperability.  These elements collectively can create rich interfaces that previously required large layers of server-side infrastructure (traditional CMS) to support.  By completely decoupling the two layers, speed of development and ease of maintenance are radically simplified, which positively impact both cost and time to market.

FREE DOWNLOAD: AWS Headless CMS White Paper

Have questions?