 |
||
| Evaluate Deploying Containerized Apps on AWS | ||
|
Containerization offers many opportunities for flexibility and modernization when it comes to applications and there have never been more ways to achieve those goals on AWS than there are now. Whether you are looking for platform independence by deploying your own containerization infrastructure on AWS using a well known Kubernetes distribution, you have elected for the ease of management of docker’s swarm mode, or you’re looking to go native using Elastic Container Service (ECS), Elastic Kubernetes Service (EKS), or need help with evaluating the options, Uturn’s Containerization Build Lab can provide the expertise your team needs to make a decision and help them learn, understand, and operationalize your final selection. |
||
| How the Uturn Containerization Build Lab Works | ||
|
All containerization build labs are 4-10 week engagement that culminate with the delivery of a preliminary AWS infrastructure that is usable by your team for containerized workloads. All specialized labs will result in your team having the pipelines, schedulers, and workload definitions needed to run applications and APIs that have been successfully containerized. ECS Build Labs The ECS build lab is a 4-6 week engagement that results in your team building an ECS cluster, creating services and tasks, and configuring the underlying infrastructure. The ECS cluster will be the target scheduler for the containerized workloads and will be produced in a templated fashion allowing your team to modify, extend, or duplicate the infrastructure necessary to run your workloads on Elastic Container Service. EKS Build Labs The EKS build lab is a 4-6 week engagement that results in your team building an EKS cluster, creating services and pods, and configuring the underlying infrastructure. The EKS cluster will be the target scheduler for the containerized workloads and will be produced in a templated fashion allowing your team to modify, extend, or duplicate the infrastructure necessary to run your workloads on Elastic Kubernetes Service and for your team to be able to interact with it using standard Kubernetes tooling such as kubectl, helm, and others. Bring-Your-Own (BYO) Containerization Build Labs The BYO build lab is a 4-6 week engagement that results in your team building a cluster using the scheduler of your choice, configuring it for application deployment, and configuring the underlying infrastructure. This non-AWS-native cluster will be the target scheduler for the containerized workloads and will be produced in a templated fashion allowing your team to modify, extend, or duplicate the infrastructure necessary to run your workloads in AWS and for your team to be able to interact with the scheduler using its correlating tooling. Scheduler Evaluation Build Labs A Scheduler Evaluation Build Lab has the longest timeline of all the Containerization Build Labs at 6-10 weeks, with preliminary time dedicated to making a determination of what scheduler is the right one for your organization, whether that is one of the native AWS schedulers or you decide that third-party/BYO is the right path, which will then lead into the the standard build lab based on the decision made by you and your team. Methodology and Planning Leading up to any of these engagements, you will have an assigned project manager and Senior Architect, and through a series of planning meetings we step through your use cases, assess your current state, propose an architecture, and ensure that the team is ready to build. The result of build week is a pilot implementation of your application, built using AWS services alongside tools or SaaS offerings that are already in your arsenal.
Containerization Build Lab Deliverables When the lab is complete, you will have a pilot version of your application with the following attributes:
|
||
|
