Cost Optimization: Lambda
A few considerations that should not be ignored.
We’re living in unprecedented times at the moment and our country, indeed our world is facing some serious issues and challenges. Obviously, businesses are organisms that are now feeling the pain, and many are reacting. Every organization, now, if a humane one, is:
Trek10 is experiencing this “business ask” through our customer base, and this post has been created to demonstrate how impactful our experts are at reducing an Amazon Web Services bill, while at the same time, maintaining, or even upgrading performance. Like everything Trek10 does, it's through a combination of custom work and deep Amazon Web Services experience. This post digs deeper into the Trek10 ethos and how it is combined with the five pillars of the Amazon Web Services Well Architected Framework. We additionally share a couple of specific examples of how we leverage who we are, some of the tooling that we’ve built, how we operate, and what we believe in, into real cost savings for our customers. One specific example stands out, providing insight into savings just in the last few weeks during the COVID-19 pandemic.
Trek10 has always specialized 100% on Amazon Web Services (AWS), building a globally recognized brand around our expertise on the popular public cloud. We are a group that is mostly known for innovation on the platform. A few examples:
Everything we build is in the spirit of our Trek10 values, with one of those values being: “Be Practical and Efficient.” We are committed to building practical solutions quickly and efficiently, we are also ruthless about costs. We avoid building technical debt on “day one” so that we don’t spend time “figuring out” how and when to cut costs on “day two.” After all, the real value in giving the public cloud your “undifferentiated workloads” is that you can now spend time on innovating and creating new value to the business and customers. Spending too much time on cost optimization is unnecessary. It has to be done for any environment on an ongoing basis, but the more you do it, the higher the opportunity cost for the real stuff: the actual work that makes your business stand out.
While most of our initial engagements when we started the business six years ago were greenfield or new environment builds, over the course of the years, we’ve taken on many legacy systems. (Yes if you have not optimized your AWS environment in the last 12 months, you have a legacy AWS environment.) Once we took on these “legacy” customers, we heard this type of feedback consistently:
When we took on these legacy systems, customers were delighted to learn that we not only had the chops to consult on a more “legacy type of build,” but we could also provide the consulting help they and their teams needed to modernize their infrastructure. Additionally, through our CloudOps practice (Trek10 calls “Managed Services,” CloudOps and is a certified AWS MSP partner), we could become their team to monitor and continually innovate their environment for them.
Inevitably, however, at some point in time after we would begin to engage, and after we fixed some of the egregious mistakes, the most glaring issue became cost and an overall lack of efficiency.
The AWS service provider market, especially when it comes to cost-cutting, is a unique business, mostly made up of consulting partners leveraging third party tooling that isn’t bad, but it’s not optimal either. Sometimes the tooling and what it promises, doesn’t match up to the reality of the workload demands for the business case. The net is that most consulting partners in the ecosystem are relying on tooling that can fail to deliver meaningful insight. Combine that sub-par tooling with a lack of multi-year experience on the AWS platform and the resultant cost-cutting is sub-optimal. Yes, some savings occur, but, oftentimes, overprovisioning for the sake of “playing it safe” is the norm. This is exactly the “value gap” where Trek10 has shown it can help and is helping today. Trek10 takes a custom approach with scripts developed over the years developing on the AWS platform to help provide meaningful insight and results quickly. These scripts and methods cover a variety of AWS products and services, and given these socio-economic times, Trek10 would like to share some recent results with customers for two customers.
Yet another very recent example of an IoT startup customer can be found here via this LinkedIn post, focused on compute by our fellow colleague, Nessan Harpur, providing further insight that Trek10 is attuned to the current economic situation.
The other main driver for providing these cost savings anchors another of our principles: “Don’t be satisfied with the state of the art.” We comprehensively believe that if we are building value for the customer, we are doing the right thing and establishing a long term mutually beneficial relationship. We do not worry if doing something of value to the customer reduces our job or gives us less to do. The simple fact that AWS continues to innovate will give us plenty to do, and we will be ready to provide value to the customer based on that fact alone. Additionally, helping a customer save some money allows them to reinvest in their business, providing more operational capital to use wisely for growth endeavors or investing in productivity or in times like these, marshaling resources to take care of their employees and help the greater good. We instead adopt an “infinite mindset” in understanding what is best for all of us and helping our customers innovate. That produces trust, the most valuable trading currency even also before COVID-19.
Let’s continue to be connected through communication with an “empathy first” and “infinite mindset” approach. We need that now more than ever, even if it’s just business and cloud chatter.
A few considerations that should not be ignored.
But, I thought VPC was free?