Managed Performance Architects for the Cloud

Talk to an Architect

Trek10 builds, optimizes, and manages high-value, cloud-based solutions with the absolute best DevOps tools and cloud services.

Our focus is on container-based, serverless, and event-driven architectures on AWS. Massive scalability, high uptime, heavy automation, and remarkably low operating costs are our hallmarks.

Let's Get The Job Done

Hear From Our Happy Clients

The team at Trek10 is impressively robust and flexible. From infrastructure design to extremely short crisis response times, I have been consistently impressed with their abilities. They have made BIGWORDS.com better, stronger, and faster.

Trek10 has helped us build one of the most flexible deployment and QA processes around. Thanks!

We feel very secure in the fact that Trek10 is monitoring and managing our entire production environment 24/7. That allows us keep our costs under control and to focus our internal team on value added tasks rather than day to day maintenance.

Read Pro Tips in Our Blog

August 05, 2016

What is Serverless and why Does it Matter?

When you hear “Serverless” I know what you’re thinking… oh boy, another buzzword! I get it. And it’s a pretty confusing one, on two levels. There are still servers! We're just talking about a new abstractoin above the servers, but of course the servers are still hiding down in the stack.

May 02, 2016

DynamoDB Auto Scaling - The Serverless Way

So you’re building your serverless app on AWS for unlimited scalability and true pay-per-use. Your web server is Amazon API Gateway - unlimited scale with zero scaling effort. Your app server is AWS Lambda - ditto, unlimited scale with zero scaling effort. And your database is Amazon DynamoDB - unlimited scale… but not quite zero scaling effort.

April 02, 2016

AWS Assume Made Awesome

Here at Trek10, we work with many clients, and thus work with multiple AWS accounts on a regular (daily) basis. We needed a way to make managing all our different accounts easier. We create a standard Trek10 administrator role in our clients' accounts that we can assume. For security we require that the role assumer have multifactor authentication enabled.

March 21, 2016

SSL Certificates... for Free!

As a follow up to our post HTTPS Everywhere, today we'll discuss some history behind the SSL certificate and why they seem to cost so much money. We will also dive into the current landscape of SSL certificates and how you can obtain free Domain Validation certs through AWS Certificate Manager and Let’s Encrypt.

March 09, 2016

Introducing LambdaClock

CloudWatch Event rules can be scheduled at minimum intervals of 5 minutes. At Trek10, we saw the need for a smaller interval, namely 1 minute. This need arose specifically in the context of handling Auto Scaling within ECS.

February 15, 2016

Using Roles to Secure Your Environment, Part 2

In Part 1, we reviewed a use case for roles in which console users would be required to assume a role for access to the production environment; we have implemented this for some of our more security conscious customers for the benefits we mentioned in Part 1. In Part 2, we will review cross-account roles and some of the different use cases.

February 03, 2016

Ops in a Serverless World

New technology appears and old job functions become obsolete. The practitioners move on to retrain on higher-value tasks and in the end the whole system is more productive. It happened when cars replaced blacksmiths, when the computer replaced armies of human calculators, and it is happening now as cloud services replace low-level hardware babysitting on a large scale.

August 24, 2015

Static Websites for a Better Tomorrow

The bytes that make up the page you are reading right now were delivered by a set of servers close to you. They were not generated by a server running WordPress or Joomla. In fact, the entire Trek10 website has no traditional server backend at all.

May 24, 2016

The Misunderstood t2 Instance Type

Amazon EC2 has over 40 different instance types and keeping track of them all can feel a little daunting. To simplify it, pay attention to something called an “instance family”. This is the prefix before the period in the instance name, for example the m3.large instance is in the family “m3”.