Cascade CMS Chronicles: 8.6 User Publishing to Amazon S3

By Bradley Wagner — Wednesday, October 18th, 2017 at 11:00am
Blog cover image

Each year, the amount of content published online increases, forcing web admins to find new, more efficient ways to store, access, and deliver content on their sites. Amazon’s Simple Storage Service (S3) helps with scalable and reliable data storage that reduces latency for users.

For the non-technical types, latency is the time between when pages are requested and when they actually show up. This is important because if pages take too long to load (more than 2-3 seconds according to Wired magazine), users disappear.

How does this work?

Cascade 8.6 allows users to publish to Amazon’s S3 through a new transport type. This change empowers users statically host entire websites using nothing but Cascade, S3, and CloudFront. That means no servers, instant scalability and world-class security all in one.

Want to see what’s possible with Cascade 8.6 and Amazon S3? Check out this sample site built using nothing but these components.

S3 can be combined with Amazon’s CloudFront, a high-performing content delivery network, that pushes content to users through a global network of geographically distributed servers. The sheer volume and location of the servers ensure a consistent and reliable experience for visitors.

This is key. As the amount and type (static v. dynamic) of content stored on sites increases, CDNs like CloudFront will become more popular.

The benefits of using S3 and CloudFront extends beyond site speed and reliability. When combined, these features allow users to create fully-functional, HTTPS-enabled sites. As you may know, Google’s Search preferences sites that with the HTTPS designation over those that do not. More on that here.

How do I publish to Amazon’s S3 in Cascade 8.6?

Once you upgrade to Cascade 8.6 and have an Amazon S3 account secured, publishing content to this destination is easy. Follow the simple 8 steps below to start taking advantage of this new functionality.

  1. Navigate to Manage Site > Transports.
  2. Navigate to the container in which the new Transport will be stored, or create a new container using Add > Container.
  3. Click Add > Transport.
  4. Select Amazon S3 and click Choose.
  5. In the Name field, enter the name for your Transport.
  6. In the Parent Container field, select a container for the Transport, if desired.
  7. Under Amazon S3 Transport Settings, configure the following fields:
    • AWS User Access Key ID
    • AWS User Secret Key
    • S3 Bucket Name - Name of an S3 bucket to which the AWS Access Key user above has write access.
    • Base Path - Optional, assets will be published in this folder within your S3 bucket.
  8. Click Submit.

Upgrade to Cascade 8.6

Get Amazon S3

For more on new, and recent, improvements to Cascade CMS, follow our new blog series, Cascade CMS Chronicles. Subscribe now and you’ll receive the latest posts delivered directly to your inbox.

What features do you want to see in Cascade CMS? Share your ideas below or in one of our client community channels.

  • Cascade Exchange: collection of example sites, code, videos and tutorials for Cascade CMS users
  • Help Forum: database of FAQs and answers with input from active users and our product team
  • Idea Exchange: customer forum where users can share what they are doing with the product and make suggestions about changes they’d like to see
Community Slack Feedback Channel: share your thoughts in real time by joining our feedback Slack channel

Subscribe to our blog via RSS Download RSS

Hannon Hill Corporation

3423 Piedmont Road NE, Suite 520
Atlanta, GA 30305

Phone: 678.904.6900
Toll Free: 1.800.407.3540
Fax: 678.904.6901

info@hannonhill.com

GSA Contract Holder

JOIN OUR MAILING LIST

CONTACT US