Container Cluster ECS (root360)

Component description

The Container Cluster ECS is a fully managed container environment. With that component you can use container in business critical environments without stress: You deliver the containers, we take care of everything else. The component bases on Amazon Elastic Container Service (Amazon ECS). Prerequisite for using the component are container images, which are deployed in a container registry provided by the customer or root360.

Setup

  • Configuration of a scalable container cluster with 2+ nodes based on AWS ECS as well as network infrastructure, load balancer, etc.

  • Provisioning container deployment for non-disruptive exchange of container instances.

  • Provisioning of a container registry based on AWS ECR.

  • Setup of container services as part of the project, additional container types or services as additional professional services

Ingress Proxy

  • Routing via Traefik as Fargate Container

  • Layer 7 (per domain or per URL)

  • external load balancer (ALB) for SSL connection and certificate management

  • AWS certificates possible at the load balancer (ALB)

  • SSL termination at Traefik

  • automatic discovery management per container type

  • SSL offloading from proxy

  • IP blocking for external as well as internal domains

  • Basic Auth for external as well as internal domains

  • TCP based routing

Traefik replaces our former proxy solution from end of 2021. For migration purposes please contact our Service Team.

Auto Scaling

  • horizontal auto scaling on container type/service level

  • horizontal auto scaling on container cluster level

  • Adaptation and optimization to specific load scenario

Fargate

  • AWS Fargate is a serverless data processing engine for containers (see also https://aws.amazon.com/de/fargate/faqs/)

  • Fargate comes with some limitations and special features: e.g. no Docker CLI for commands like docker exec or docker logs, limited use of persistent storages


Variants

  • Standard: use of EC2 (On Demand or Reserved Instances)

  • Fargate: use of serverless compute for containers (AWS Fargate or AWS Fargate Spot)

  • Combined: use both Standard and Fargate

Container in context of Managed Services

Container have special features due to their ability to encapsulate various components. For that reason we implemented a "shared responsibility" model: You are responsible for everything "inside" the container, while root360 is responsible for everything "outside" the container.

Pricing

For AWS pricing see https://aws.amazon.com/ec2/pricing/.

For root360 Managed Services pricing please contact our Service Team.

Related tutorials

 

root360 Knowledge Base - This portal is hosted by Atlassian (atlassian.com | Privacy Policy)