Our Bootcamp Accelerator follows a “do it yourself” (DIY) delivery model of our AWS reference architecture for terraform. It includes all configurations and documentation required to get going in a “Cold Start” scenario. You'll receive access to private weekly workshops with our customers. If at any point you need more help or customizations, we offer professional services.
Benefits
There are no long-term commitments.
We eliminate the guesswork of building and owning your AWS cloud infrastructure. Our proven process and pre-existing materials ensure a consistent outcome every time.
Working with us ensures a predictable outcome that is delivered on time and within budget.
By and large, most engineering projects without pre-existing processes and materials fail to be delivered on time. Their scope is grossly underestimated which results in missed deadlines and exploded budgets.
Working with Cloud Posse ensures you avoid the most common pitfalls and achieve the intended outcomes without blowing your budget.
You can hire 2-3 experienced DevOps engineers to build your platform, which may work, but offers zero guarantees other than it will cost 2-3x the cost of hiring Cloud Posse. Plus, when you work with us, we'll rapidly level up your team's skillset set, increasing their value to your company.
What many companies fail to realize is you don't need just “a DevOps Engineer”. You need a combination of various skill sets, many of which companies lack or do not budget for.
- Technical Project Managers with an understanding of managing DevOps teams. DevOps Engineers are frequently excellent at solving problems but need help (moreover, appreciate the help) managing their priorities and someone to run interference if they are heads down fighting fires.
- QA/Release Engineers with a solid grasp of the CI/CD platform and the organization's needs. They should possess knowledge of test automation and their role in delivering a stable software delivery process.
- DevOps/Platform Engineers who understand the tooling and possess a holistic understanding of the entire process, soup to nuts. They need to understand the relationship between their job and the needs of the business and developers.
- Site Reliability Engineers that work with the business to establish SLIs/SLOs and build in the systems to ensure objectives are met.
When you work with Cloud Posse, you get all of that coupled with our proven process and reusable materials, which ensure your success.
Developers are a business' most expensive investment. Empowering developers to work autonomously with self-service infrastructure will pay dividends in productivity and maximize your ROI.
Who It's For
Our Bootcamp Accelerator is ideal for early-stage, angel-funded, or bootstrapped companies with technical founders and a capable team knowledgeable of Terraform. You know what you need, you just want to get there faster. You know how important it is to lay the proper foundation early if you want to move quickly.
Everything we deliver leverages the same components that power billion-dollar startups and enterprises. This is why we know it will scale for your team, but it's not a fit for everyone and could be intense.
You probably have these needs:
Needs
If you are an enterprise, you need to leverage AWS Organizations, Organizational Units (OUs), and member accounts to segment workloads. This is standard in every one of our engagements as part of our Reference Architecture.
Operating Multiple Organizations
It's not uncommon for enterprises to manage more than one top-level AWS root account.
If you currently operate multiple organizations, we can help! We have implemented multiple patterns over the years. Here are some examples:
Due to acquisitions
Enterprises frequently acquire other companies operating in AWS. Simply adopting the member accounts of the acquired company can be a disruptive operation. Furthermore, acquired companies sometimes operate independently for some time after acquisition.
Due to security segmentation
We've seen some organizations use separate organizations for the SecOps, ensuring that they are fully autonomous.
Due to stage segmentation
We've helped customers who use a dedicated AWS organization per stage (dev, staging, production). This is ideal from an isolation perspective. It means that changes made in the root “dev” organization cannot affect anything production-facing.
To scale the adoption and maintenance of your AWS organization with Infrastructure as Code, the business needs to adopt the pattern of building a reusable catalog of services, and landing zones that provision a baseline of services and guardrails so that teams can operate autonomously following established best practices.
A well-designed service catalog can be centrally managed, and changes can be pushed out to consumers of the service catalog in an automated fashion.
Our Reference Architecture implements the most comprehensive Service Catalog for services on AWS using terraform. Not only that, all of our services are Open Source and licensed under APACHE2.
If you need to get something up fast (e.g., within 2-4) weeks, our Bootcamp or Jumpstart accelerators are ideal, depending on your level of experience and budget. These solutions leverage our proven reference architecture for terraform, but to deliver them quickly are delivered prebaked with all of our standard recommendations, and you can customize anything before going into production, or leverage our professional services as needed to make modifications for you.
This is a phenomenal fit if you've previously used our reference architecture at other companies. You can use the same tooling you're already accustomed to and jump the gun to get up and running quickly. Then hire us if you need any customizations made.
FAQ
It depends. Your best bet is to schedule a discovery call with us so we can go over your specific concerns. Assuming your software runs on Linux and that you're able to make any necessary code changes to ensure your applications are “12 Factor App” compliant, there's a very high likelihood we'll be able to help you out.
Here are some additional resources you can review:
- Our GitHub is where we publish over 140 terraform modules we've written and open-sourced under the Apache 2 software license. Our repos see over 11K unique visitors every single day and have over 5000 stars. We receive dozens of Pull Requests every week.
- Our Reviews are glowing both from our customers and from our community.
- Our Community will tell you how much we've helped them. You can scan through all of our archives to see what they say.
- Our YouTube Channel showcases many of our presentations and webinars
- Our Office Hours Recordings demonstrate our depth of knowledge and commitment to help others.
- Our Service Catalog is what lets us rapidly deploy the applications you see in our demos and is regularly updated.
- Our Work is Cited all over the place.
Chances are we can reuse what you have if it makes sense. This is especially true of any code that is hyperspecific to your applications.
On the other hand, where we can leverage our existing service catalog, it will reduce your tech debt by offloading the ongoing maintenance of those components to the community. We'll also be much better equipped to support any questions you have related to our reusable modules or extend any functionality.
Common examples of reusable building blocks are things like VPCs, Subnets, RDS Postgres/MySQL Databases, Redis/Memcache clusters, ActiveMQ/RabbitMQ clusters, EKS/ECS Clusters, etc. We have over 150+ reusable Terraform modules that are well-maintained, actively tested with terratest, and community-supported.
From time to time we get asked if it's possible to use something other than slack (e.g. MS Teams, discord, etc) to collaborate between our teams.
TL;DR: Unfortunately, we're not able to join other teams. Here's why…
On the backend, we have dozens of engineers (and growing) who we can pull into any channel at a moment's notice. While there is always a lead assigned to your project performing most of the work, at any given time, we'll pull in different people to help with different parts. Think of them as specialists. Also, because we're engaged with a dozen or more customers at any given moment, the logistics of that means we cannot manage conversations across multiple chat platforms.
When companies work with Cloud Posse, you're not getting “a DevOps engineer” (e.g. that's Staff Augmentation), you're getting access to all of our pool of resources which include expertise in DevOps, Release Management/Engineering, SRE, Security & Compliance, etc. One or two engineers cannot possess all that expertise and be specialists (e.g. “Jack of all trades, master of none”). This is also why it's so much more valuable hiring Cloud Posse because for barely the cost of a fully-loaded DevOps engineer, you're buying access to a full team and all the pre-existing materials that have cost millions of dollars to produce.
The great thing about our Engagement Workbook process is it helps us identify upfront customers who are a good fit for how we operate. It's why we're so successful because we have standardized our engagement model. The more variables we introduce, the greater the risks and the more we diverge from what we know works.
There are many excellent alternatives to Amazon Web Services (AWS)! Cloud platforms like GCP and Azure have significant differentiators that make sense for specific businesses. We genuinely wish we could claim we are experts on all of them, but maintaining hundreds of modules simply for AWS has taught us it's extremely difficult to claim mastery of more than one cloud platform.
That's why we specialize in AWS.
You have a couple of options:
- If you want to be on AWS and eventually a platform like GCP/Azure, then we're still an excellent investment to start with.
- We understand if you can't operate on AWS (e.g. many e-commerce companies do not use Amazon on principle). You'll probably be better serviced by a company specializing in one of those platforms.
What's It's Not
It's not a walk in the park nor a class on how to learn terraform for beginners. It may be overkill if you only have a single app with only a few backing services and no plans to scale up to dozens of services and backing services.
It's currently unavailable for resale to other agencies or professional services companies, but if you're interested please let us know.
Differentiators
We specialize in Terraform. We've written more Open Source modules than any other company out there.
Terraform makes a lot of sense because it's arguably the most established language for Infrastructure as Code. That means as a business you'll find the most talent that knows how it works. There's tons of documentation on how to use it. A considerable community surrounds it. HashiCorp (NASDAQ: HCP) is a public company behind Terraform, so it's here to stay, reducing some of the risks in adopting the language.
There are a lot of alternatives to Terraform these days. Make sure you pick what makes the most sense for your company.
Terraform Alternatives
- Pulumi
- CDK
- CDK TF
- Cloudformation
- Serverless Framework (specifically for lambda-style applications; not a complete replacement for terraform, but an excellent choice for companies doing a lot of serverless development)
We are a Professional Services company that specializes in delivering Open Source solutions. Most of our deliverables are Open Source and licensed under APACHE2.
This means that as customers invest in Cloud Posse, they are investing in Open Source as a whole. They are advancing the industry and contributing back. Rather than invest in closed-source, which dies a slow painful death within the confines of a private GitHub, the code customers pay us to develop lives on. It continuously receives updates and contributions from our vast community of 6000+ people.
Cloud Posse is a DevOps Accelerator. We help companies implement their AWS architectures the right way using Terraform. A “DevOps Accelerator” is a subcategory of Professional Services. It means that the provider has a proven, systematic, and repeatable process to help companies achieve a certain level of organizational “DevOps” maturity.
Our process consists of our project plan that takes a company through its journey of migrating or replatforming on AWS. It's repeatable because we use our reference architecture and our open source to continually iterate on the same, effective solution, ensuring we are successful every time.
We specialize on Amazon Web Services (AWS), which says a lot. There are hundreds of services offered by AWS, which is why we have so much Terraform. Staying on top of it is difficult enough[1]https://aws.amazon.com/new/; new services and features are released daily.
Companies that specialize in multiple platforms (e.g. AWS, Azure, GCP, et al) are spreading themselves thin. In order to maintain a repeatable, cohesive solution, specialization is a requirement. That's why as a DevOps Accelerator, we've deliberately decided to only specialize in Amazon, which has allowed us to go deep and develop a mastery of provisioning AWS services with Terraform.
References
| ↑1 | https://aws.amazon.com/new/ |
|---|