Get insights into the day-to-day challenges of builders. On this situation, Samia Rabah from our associate DEMICON talks about ECS Wherever to orchestrate containers on-premises and within the cloud.
When you want a video or podcast as a substitute of studying, right here you go.
Do you like listening to a podcast episode over studying a weblog publish? Right here you go!
cloudonaut: You joined DEMICON as a DevOps and Cloud Marketing consultant in July 2022. How has your profession gone up up to now?
Samia Rabah: After graduating with a grasp’s diploma in machine studying, I began my profession as a Python developer. Later, I joined KM.ON as a full stack developer and contributed to one in every of their information science tasks. As a full-stack developer, I got here involved with the cloud and the infinite prospects fascinated me. So I used to be searching for a brand new job the place I might concentrate on my cloud abilities. That’s how I discovered about an open place at DEMICON.
cloudonaut: DEMICON is a remote-first firm, so what did the onboarding course of appear like?
Samia Rabah: The onboarding course of was welcoming and well-structured. For instance, I had distant espresso conferences throughout the first week with a lot of my new colleagues. Additionally, all my {hardware} and credentials arrived even earlier than I began my new place to make sure a seamless begin. Apart from that, I had the chance to satisfy my group and others who have been starting recent at DEMICON in individual.
cloudonaut: In our expertise, being a developer is completely different from being a advisor. How did you get into the function of a advisor at DEMICON?
Samia Rabah: I labored on bettering an inside challenge throughout the first weeks. I additionally ready for and handed the AWS Licensed Developer Affiliate exams. After that, I performed a workshop on the buyer’s website for the primary time. And later, I labored on my first consumer challenge, which is the place I carried out an answer based mostly on ECS Wherever.
cloudonaut: What was the problem you confronted in your first challenge?
Samia Rabah: My buyer was already working a workload consisting of an API and batch processing layer on ECS. The batch processing required GPUs and was subsequently working on costly EC2 cases. The client needed to make use of underutilized on-premises machines to cut back prices as a substitute of working your entire GPU workload on AWS.
cloudonaut: What’s ECS Wherever?
Samia Rabah: The Elastic Container Service (ECS) orchestrates containers on EC2 cases or Fargate. With ECS Wherever, you possibly can run containers on bare-metal or digital machines. All it is advisable to do is set up and configure the SSM and ECS agent.
cloudonaut: May you please share the structure for the API and batch processing workload working on ECS, Fargate, and ECS Wherever?
Samia Rabah: The next determine illustrates the parts of the structure.
- ECS orchestrates the providers, duties, and containers.
- ALB forwards requests to the API service.
- Fargate offers the compute capability for the API service and permits working batch processes within the cloud throughout peak hours.
- ECS Wherever runs containers on on-premises machines.
- EFS is used to load the enter and persist the output of batch jobs.
cloudonaut: How does monitoring and logging work for containers working on-premises?
Samia Rabah: ECS Wherever helps the awslogs log driver. Due to this fact, every container is able to sending its logs to a CloudWatch log group. Doing so is extremely really helpful, as centralized logging is essential for debugging points. Observe that ECS Wherever additionally helps job and job execution roles. Due to this fact, attaching IAM roles to your duties/containers is feasible to grant entry to different AWS providers.
cloudonaut: That sounds nice. Logging and IAM roles are very useful. However, does ECS Wherever include any limitations?
Samia Rabah: Sure. The community mode awsvpc isn’t supported, because the workload is working on-premises. If obligatory, it is advisable to peer your on-premises community along with your VPC. For instance, now we have been utilizing a site-to-site VPN connection. Apart from that, AWS Wherever doesn’t assist Elastic Load Balancing. Additionally, the native integration for EFS volumes isn’t supported. As an alternative, it is advisable to mount the EFS quantity on the on-premises machines and use native container volumes.
cloudonaut: Do you suggest ECS Wherever for different eventualities as effectively?
Samia Rabah: Usually, I’m an enormous fan of ECS Wherever. It labored very effectively and enabled hybrid cloud eventualities. ECS Wherever is an efficient match for batch processing or comparable workloads that don’t require inbound site visitors. I also can think about utilizing ECS Wherever in eventualities the place the entire workload runs exterior of AWS, for instance, to course of information on the edge.
cloudonaut: Thanks rather a lot for sharing your insights into ECS Wherever with us, Samia!
