Not long ago,The Register offered this tongue-in-cheek prediction: “What sector of tech is forecast to grow fatter than the Slovakian economy or Elon Musk’s ego in 2018? The cloud. Global spending on the fluffy white stuff is predicted by mystics at Gartner to reach $175.8bn this year.” This doesn’t appear to have been an exaggeration. Acloud industry insights report from Right Scale indicated that 96% of companies across industries have embraced cloud services, for any number of reasons, including faster, more innovative delivery and cost reductions, among others. And more than half of the companies surveyed were deploying multiple clouds for different reasons as well as any number of hybrid on-premise and cloud mashups that together make up a custom solution to suit each individual company.
In the five or so months since we released the Varnish Plus Cloud product, currently available on Amazon Web Services (AWS) and Microsoft Azure - and coming soon on the Google Cloud Platform - we have had a number of inquiries from customers all over the world asking: What’s the difference between Varnish Plus and Varnish Plus Cloud? Moreover, why should customers choose Varnish Plus Cloud - what benefits does it offer? What makes up a Varnish Plus Cloud subscription, and what does Varnish Software provide as a part of the Cloud instance?
Cloud options make for more convenient and affordable solutions, particularly for small-to-medium businesses that cannot or do not want to invest in and maintain the hardware needed.
In this blog post, I will go over how to configure Varnish Cache to act as a secured gateway for your Amazon Web Services (AWS) S3 content. There are many reasons to use Varnish Cache as an AWS S3 gateway: caching, more efficient bandwidth utilization, centralized access with logging and security, or maybe just composing a virtual site across many different backend pieces, S3 included.