Tag Archives: AWS

Securely Connect to Your AWS Cloud Resources

When using ElasticBox, you bring your own cloud. To deliver the absolute best experience of deploying applications on any cloud, we are working very closely with all the cloud providers that we support – Google Cloud Platform, Amazon Web Services, Microsoft Azure, OpenStack, CloudStack, and VMware. One of the topics that often comes up is security. Today, we’re adding enhanced security for our AWS support.

Our friends at Amazon have built comprehensive Identity and Access Management (AWS IAM) features, which enable enterprises to grant and control secure access to specific AWS resources. Read More

Aladdin’s LAMP Stack: Where App Dreams Come True

What if a little genie told you that Aladdin’s magic LAMP is the stuff of app dreams. LAMP what? Well, the acronym stands for Linux the base OS, Apache the web server, MySQL the database, and PHP the scripting language respectively. It’s a popular mix of technology to build high performance websites and web applications.

Now you’re thinking what ElasticBox has to do with it. It’s simple. We help you put together a LAMP Stack environment in no time so you can be on your way to build out your application. Read More

ElasticBox Supports AWS Elastic Load Balancer

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 ElasticBox, 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 supported AWS services: EC2, RDS (MySQL and Oracle), ElastiCache, and S3 Block Storage.

Our philosophy at ElasticBox is steer away from a common denominator approach to cloud provider support. Whether it is AWS, VMware, GCE, OpenStack or Azure, our focus is to provide rich and in-depth support for the services that differentiate each of these cloud providers.

Someone’s Infrastructure is Someone Else’s Service

These days where everything is offered up “as a service,” we run the risk of turning “as a service” into a meaningless marketing tag. Most everyday someone out there comes up with a new “as a service” offering forcing even the government to officiate guidelines for IaaS, PaaS, and SaaS. In this blog, I’d like to explore the true meaning of Infrastructure as a Service (IaaS) and see what it means for us as enterprises and developers.

What does IaaS mean?

As defined by the government, Infrastructure as a Service allows consumers to provision processing, storage, network, and other fundamental computing resources on demand. To these provisioned resources, consumers can deploy and run arbitrary software including operating systems and applications. Without having to manage or worry about the underlying cloud infrastructure, consumers can control operating systems, storage, their deployed applications, and even in some limited way control networking components like host firewalls.

Before Amazon’s EC2 offering, many hosting companies like Rackspace had already offered compute resources on demand. But what’s so different about the AWS offering that triggered a whole IT revolution?

Why’s Amazon IaaS Strategy Successful?

I believe the difference is rooted in Amazon’s service centered culture as revealed in Steve Yegge’s post and most recently in Brad Stone’s book, The Everything Store. Jeff Bezos’ crusade to be efficient has a tremendous impact on how individuals and teams communicate at Amazon where everything is an interface. Even meetings are conducted on a very well defined contract (no PowerPoint presentations but a 7-page write-up instead). So how does this approach make AWS the market leader in cloud computing? The answer lies in how Amazon’s internal organization is designed upon Service Oriented Architecture principles. At Amazon, every team communicates using well-defined interfaces that are abstracted from the implementation. As a result, today we’re all just one more team within Amazon—this is not just great customer support, but goes beyond where we’re all in the same boat as Amazon consuming the same service as them.

How to be Service Oriented Like Netflix?

With its service-oriented philosophy, AWS has liberated us from mundane infrastructure details and forced us to focus on what really matters. This trend could not be better represented than by Netflix, a company that realized the potential of shifting its focus to its core business so successfully that it’s become the canonical example of the potential of cloud computing.

In reality, it’s not important whether your strategy is IaaS, PaaS, or SaaS. What matters is that you’re able to change the mental model and operate as a service organization requires. The amount of commitment to this philosophy will determine the right strategy for you. The less you care about implementation details, the higher in the services stack is your insertion point. I personally believe the higher you start, the higher you reach.

What do Services in Context Mean for You?

At ElasticBox, we build the tools that allow enterprises and individuals to truly operate as a service. We help shift focus from implementing interfaces to collaborating with interfaces and from merely controlling interfaces to using them in context. This means anything can be a service whether it’s a platform or a low-level infrastructure resource, as long as its function is well defined through an interface, and it abstracts users from its implementation. How these services should be used is not determined by control, but by context ultimately powering the user to make their own decisions.