Today, we officially pushed to production our newest supported cloud service: AWS Elastic Load Balancer.

The AWS Elastic Load Balancer, which automatically distributes incoming application traffic to the right set of EC2 instances, plays a vital role maintaining business continuity. Enterprises that often experience sudden surges in traffic, such as in media and marketing, rely on AWS Elastic Load Balancing to ensure greater levels of application fault tolerance.

With Cloud Application Manager, users compose their applications by stacking together Boxes. At the time of deploying to a cloud provider such as AWS, the user can select from a set of provider-specific services that enhance the deployment.

Users now have the option to add AWS Elastic Load Balancer capabilities at the time of deploying their Box. We support the load balancing of applications using HTTP, HTTPS, TCP and SSL protocols and provide the ability to specify the certificates necessary for secure protocols. In addition to creating brand new load balancers at the time of deployment, we also support the reuse of existing load balancers that are associated with the user’s AWS account. This allows businesses to repurpose their existing infrastructure configurations.

With the addition of Elastic Load Balancer, we have expanded our current list of...

Read on...

People are right to be wary of any vendor claiming to be the “top performing!” or “fastest!” cloud provider. Most folks know that ANYTHING can look spectacular – or unspectacular for that matter – if you stack the deck just right. But at the same time, cloud shoppers have a deep hunger for legitimate information on realistic performance expectations. Cloud performance has a direct impact on what you spend on compute resources, how you decide the right host for your workload, and how you choose to scale when the need arises. In this blog post, we’ll summarize some recent findings and put them in context.

With the launch of our new Hyperscale instances, we approached an independent analytics company, CloudHarmony, and asked them to conduct an extended performance test that compared CenturyLink Cloud Hyperscale servers to the very best equivalent servers offered by AWS and Rackspace. CloudHarmony is a well-respected shop that collects data from dozens of benchmarks and shares the results publicly for anyone to dissect.  After running a variety of benchmarks over a long period of time (to ensure that the test gave an accurate look over an extended window), they shared their findings with the world. See the...

Read on...

Are you building your cloud application directly on the Infrastructure-as-a-Service (IaaS) provider vs. using a Platform-as-a-Service (PaaS)? In recent conversations with dozens of cloud application developers I’ve found many developers are still choosing to build their application using services offered by the IaaS (Infrastructure-as-a-Service) provider, e.g., Amazon (AWS), Rackspace or other IaaS providers vs. using a PaaS between the application and the infrastructure. In nearly every instance I find the primary reason for selecting an IaaS first was that the development team didn’t fully understand the benefits of a PaaS or didn’t know how to evaluate one.

We recommend to our clients that they select their PaaS first and then select the IaaS provider that best supports their selected PaaS. By developing your application using a PaaS, you can lower the total cost of ownership of your application by 30% or more. With the right PaaS, you also gain the freedom to change cloud infrastructure providers over-time and avoid infrastructure vendor lock-in by making your application portable to any IaaS provider.

We see five primary reasons for using a PaaS:

Reduced Operations Cost – we generally find that 30% or greater of development time can be consumed in DevOps functions. A PaaS will...

Read on...

When CenturyLink acquired Tier 3 in November, our newly integrated cloud team promised customers big things – faster innovation and access to more capabilities, to name a few.  The team has delivered in the first 140 days: new services and an expanded footprint.  Our Cloud SVP Andrew Higginbotham shares the results here by the numbers.

Another benefit?  Scale.  That leads to lower costs, which CenturyLink can pass along to customers.  Today, we’re pleased to announce a major price reduction for CenturyLink Public Cloud services. 

For our clients, and businesses considering cloud, here’s what you need to know about these changes:

Read on...

IT teams spend a good deal of time thinking about disaster recovery – and rightly so.  Unexpected downtime is hugely expensive, from a loss of productivity, to an immediate loss of revenue, to long-term damage to the corporate brand.

For disaster recovery of virtual machines already in the public cloud, CenturyLink Cloud’s premium storage option offers a simple, elegant option for enterprises.  Just click a button, and you have an RTO of 8 hours, and RPO of 24 hours in the event of a declared disaster.

What about protecting on-premise VMs?  This is a perfect workload for public clouds like CenturyLink Cloud.  Traditional DR systems are simply too hard to get up and running.  Too often, these products:

To help customers protect on-premise VMs, we’re excited to launch Safehaven for CenturyLink Cloud. ...

Read on...

A dangerous bug was identified in a popular SSL/TLS library that powers many of the web servers in the internet. This bug – called Heartbleed – allows attackers to retrieve data stored in a server’s memory and access sensitive information.

CenturyLink Cloud wants you to be aware of one impacted area which was identified through our comprehensive assessment: OpenVPN software. The Linux distribution used for OpenVPN does not yet have an updated, patched package available to remediate this vulnerability. We are actively pursuing other solutions and will have an update on this issue shortly. [Please see update and action items below]

As this issue is related to OpenVPN client software, we believe it is important to detail what type of communication between users/machines may be affected by this vulnerability.

  Control Portal system is *NOT affected, so there is no need to change your password to the web site.

  Site to site VPN tunnels from customer premise equipment to CenturyLink Cloud data centers are *NOT affected.

  Site to site VPN tunnels between customer servers in a particular CenturyLink Cloud data center to other customer servers in a remote CenturyLink Cloud  data center are *NOT affected.

 ...

Read on...

Recent history has shown that after a cloud provider is acquired, the pace of innovation slows and there’s a loss of focus (and staff). If you don’t believe me, check out the release notes (if you can find them!) of some recently acquired cloud companies. It’s not pretty. I’m here to say that we’re different.

140 days ago, the acquisition of Tier 3 by CenturyLink was described as a "transformational deal for the industry." Instead of randomizing Engineering post-acquisition with unnecessary process, and haphazard integrations with legacy and redundant products, we’ve actually accelerated pace of development on our go-forward platform, CenturyLink Cloud. In the past four months, we’ve maintained our software release cadence, grown our team, expanded our data center footprint, actively integrated with our parent company, and solidified a game-changing vision that has retained and attracted a phenomenal set of customers.

We update our cloud platform every month with new, meaningful capabilities. Only a very small subset of cloud providers can make that claim. In the past 140 days, we’ve shipped over 1,200 features, enhancements, and fixes. This includes a new high performance server class, faster virtual machine provisioning, new reseller services, a major user interface redesign, a compelling monitoring/alerting service,...

Read on...

The CenturyLink Cloud team has brought two new data centers online.  Customers can now deploy virtual resources in Santa Clara, CA (UC1) and Sterling, VA (VA1) sites.  This brings our total count of federated data centers to 11 - six in the US, two in Canada, two in the UK, and one in mainland Europe.  Expect more investment in this footprint in the months to come.

There is something special about these new sites, our first new locations since the acquisition.

When CenturyLink acquired Tier 3, it was a big investment for the parent company.

The message to the market was clear: Cloud is CenturyLink’s growth engine for the future.  We’re investing in a cloud-first platform that can solve enterprise IT jobs better than any other provider.

How do we solve them better?

By offering a superior breadth of managed services and infrastructure…with unmatched integration between products.

These new locations are a major milestone towards this vision.  Three reasons why:

Read on...

CenturyLink the Cloud Development Center contributes ElasticLINQ to the community

Today I’m pleased to announce that the developers of the CenturyLink Cloud Development Center are contributing ElasticLINQ to the community. ElasticLINQ is a tool for those who wish to find and retrieve documents from Elasticsearch and easily convert those documents into .NET classes.

ElasticLINQ will help developers ease the transition from relational databases to distributed NoSQL systems. Using the same query language for SQL and NoSQL makes the transition simpler. This code was created by .NET devs for .NET devs and today we’ve made it available on GitHub under the Apache 2 license.

Who might use it? Any company looking to write for or port software into a distributed cloud environment could benefit from these technologies.  A typical use case is devs who are using Elasticsearch as a full-featured search system for an existing NoSQL database (such as a document storage system like Couchbase).  They will use ElasticLINQ to give them LINQ syntax to query documents stored in Elasticsearch.

This is a familiar use case for our CenturyLink Cloud engineering team here in Seattle.  ElasticLINQ was one of the outputs of our efforts to transition from MS SQL Server. Our team uses Couchbase and...

Read on...

Elasticity and quick provisioning are hallmarks of any good cloud platform. Cloud customers have gotten used to rapidly acquiring right-sized resources that fit a given workload. No longer do developers have to build the biggest (physical) server possible just to avoid requests to resize later on. Rather, provision for what you need now, and adjust the capacity as the usage dictates. But how do you know when it’s time to size up?

The CenturyLink Cloud engineering team just released a monitoring and alert service (alongside our powerful server UI redesign) that gives you the data you need! We designed this feature with three things in mind:

 1. Offer a simple, straightforward toolset that users can understand and take advantage of quickly.

 2. Deliver reliable, accurate statistics that reflect the current state of a server.

 3. Provide multiple ways to identify that an alert was fired.

Together, these three principles kept us focused on delivering a service that met market need. Let’s take a look at how the new monitoring and alert service applies each principles.

Simple Setup

It’s easy to get lost in a sea of rarely-used options offered by a monitoring platform. Instead, we focused on ease of setup, a common theme...

Read on...

Today, we announced the availability of Hyperscale instances, a new service that combines our high-end compute with 100% flash storage.  Before we jump into how customers can use the service, let’s take a minute to think about the characteristics of applications and architectures deployed today. 

Here are 5 key attributes we’ve noticed:

Now, think about most applications running in enterprise data centers.  In all 5 cases, it’s almost the exact opposite.

That’s NoSQL vs. relational databases in a nutshell.  The folks at MongoDB sum it up pretty well:

If you’re a CIO, it’s simple.  The more relational systems you have, the slower you can respond to the market.  Relational databases will always have their place.  But most of the innovation happening in the next 5 years will be on NoSQL platforms.

Of course, the public cloud is...

Read on...

Multitenancy – the concept of using a single (software) platform to serve multiple customers – is a key aspect of nearly every cloud computing platform. Pooling resources results in lower costs for all parties, greater efficiencies, and faster innovation for customers. Are there risks and tradeoffs with this model? Sure, but every technology paradigm has them.

 In this blog post, we’ll look at some core principles for successful multitenancy, see how the CenturyLink Cloud provides tenant isolation, and review the ways that CenturyLink Cloud customers create isolation within their own account. The goal is to simply help customers understand what to look for when assessing multi-tenant environments to run their workloads, SaaS applications, and more.

Core Principles

Any service provider delivering a multi-tenant environment must adhere to these six commandments:

 1. Thou shalt isolate tenants within their own network. This one applies mainly to infrastructure-as-a-service (IaaS) providers who promise secure computing environments. Software-as-a-Service (SaaS) customers on a platform like Salesforce.com don’t have this issue as customers do not have access to low level network traffic. When granting virtual machine access to users, the service provider has to ensure that there’s no opportunity to intercept network traffic from other customers.

 2. Thou shalt not...

Read on...