If you’re running a WordPress to Cloud instance you may be affected by the heartdbleed bug. You are not alone (it’s estimated that the bug affects 66% of the Internet), but you need to take action to protect your website. Fortunately, it’s very easy to do with Webmin or command line.
Getting a WordPress-on-S3 website up and running is a piece of pie with our step-by-step guide, but making the website live requires a couple more pieces of the puzzle to fit together.
Today I’m going to talk about configuring DNS and HTTPS for WordPress on S3. DNS stands for Domain Name System and it is the technology that makes it possible to use friendly names for web sites. HTTPS stands for Hypertext Transfer Protocol Secure and it is the technology that makes secure connections possible.
WordPress-on-S3 makes professional website administration as easy as pie.
OblakSoft is pleased to announce availability of the ready-to-run WordPress-on-S3 / Yapixx AMI with enhanced configuration, performance, and website administration features. Now website owners can use Webmin and phpMyAdmin for secure website administration over the Internet, and pre-configure Cloud Storage Connection for the instance.
By popular demand, here is the step-by-step guide for configuring WordPress with Google Cloud Storage.
The slides have notes, they are a little hard to discover with the SlideShare interface, look for a tab below the slide that looks like “Notes on Slide #”.
Now that you use Amazon S3 to store and serve media files in scalable fashion, how would you prevent undesirable hotlinking to your files?
Hotlinking (or direct linking, inline linking) is when other sites link to or embed the image (or other media file, e.g. video) directly without providing a link to the source page. Oftentimes hotlinking happens without meaning any harm: people just want to share a picture with their Facebook friends, or post it to forums they like or etc. Regardless of intention, though, hotlinking may be harmful to your business: the media file gets downloaded from your site and consume the bandwidth that you pay for, but the user doesn’t get to see your page depriving you of ad revenue, etc.
With WordPress-to-Cloud solution all media files are stored in the cloud storage such as Amazon S3. Now it is the cloud storage (and not your web server) that serves the images and other media files. Even though this approach reduces load on your web server and hotlinking is unlikely to cause scalability problems, you are still paying for the bandwidth.
OblakSoft is pleased to announce the release of the 1.1.x version of the WP2Cloud WordPress plugin. This release allows using a Content Distribution Network (CDN), such as Amazon CloudFront, to make content delivery even faster.
The WP2Cloud WordPress plugin now has an option to specify a Content Distribution URL. When the URL is specified, WP2Cloud redirects cloud storage URLs to point to the CDN. The CDN then serves the media files from locations around the world to provide the best performance.
The CDN must be configured correspondingly, so that it uses the cloud storage as the origin. The step-by-step instructions to configure Amazon CloudFront for WordPress on S3 / Yapixx are available here:
WordPress on S3 / Yapixx AMI with CDN support is available for FREE at http://www.oblaksoft.com/downloads/.
WordPress on S3: run a beautiful website on Amazon cloud storage.
WordPress on S3: how it works.
WordPress on S3: run it anywhere.
WordPress on S3: no more backups.
OblakSoft is pleased to announce the release of the 1.0.3 version of the WP2Cloud WordPress plugin. This release addresses media handling issues reported by our early adopters. Thank you all for your feedback!
This release fixes the following nuisances:
The WordPress on S3 / Yapixx AMI is updated and tested with the latest releases of software.
Where to host a dynamic website that stores all its content on Amazon S3? Anywhere you choose to.
OblakSoft is pleased to announce availability of an OVF Virtual Appliance with ready-to-run WordPress on S3: Yapixx. Now WordPress on S3 can run anywhere, not just in Amazon EC2.
The virtual appliance is distributed in the Open Virtualization Format that is supported by most major hypervisor software vendors (such as VMware, VirtualBox, Oracle VM, etc.). The virtual appliance (one-file OVA package) contains the same software components as the corresponding Yapixx Amazon Machine Image (AMI).
How much trouble will it be if your webserver failed? No trouble at all, if your website keeps its content on reliable Amazon S3 storage.
There are a lot of nuances in ensuring proper backups and restores of websites. When was the last backup taken? How much data might have been lost? How long will it take to recover it? When was the last time you tested restore? Do you even have an offsite backup?
Now that you can run dynamic websites off Amazon S3 storage, we’ll demonstrate why you no longer need to worry about backing up and restoring your website data. Losing the webserver is no longer a disaster. Cloud storage offers almost unsurpassable reliability a lot of website owners (small & large) would benefit from. In a way you get an “instantaneous backup” to the cloud. Your data is always safe with the cloud storage. The webserver can simply be replaced in minutes.