Aspera Infrastructure Automation, Built to Scale

Running Aspera in the cloud is increasingly becoming our customers’ preferred deployment method. While there is always a pendulum swing between on-premises and cloud, the flexibility of public cloud infrastructure has taken hold of the Aspera ecosystem. You may have business drivers demanding the flexibility of multi-cloud deployments – don’t let the technical details bog you down. Our favorite Infrastructure as Code (IaC) tool, Terraform, lets you deploy and maintain new cloud environments easily. 

Spinning up a cluster in AWS London for a short production? No problem. Have a customer leveraging GCP that you need to share data with? Easy. These are the kinds of things we help our customers with every day. Point, click, deploy. 

We have been maintaining a terraform repo for Aspera Cloud Infrastructure for over five years now. This includes support for AWS, GCP, Azure, and more recently OCI. With each new deployment comes new learnings and best practices.   

In recent years we’ve honed in on cost savings, with the overall increase in transfer comes the need for more compute, storage, and egress. Our code deploys fully elastic compute clusters, with configurable node sizes that automatically scale up and down to meet demand. 

As we’ve expanded our usage over the years, we’ve found that the features in IBM HCP Terraform are a must. The ability to create and publish modules in a private registry with automated integration testing is key. Policy enforcement and drift detection enable our customers to satisfy internal security and audit requirements.  And the ephemeral workspaces feature simply enables us to work and innovate faster. 

If you’re a Terraform shop and haven’t looked at IBM HCP Terraform, let’s talk.