I am working mostly on AWS infrastructure services, such as EC2, EKS, RDS, CloudFormation, IAM, and CloudWatch. I have around one year of experience with Kubernetes and have been using AWS services continuously for three years. My responsibilities include working on server storage, containerization, monitoring, and access policies.
We use EKS in our company to run containerized applications. I work in the container ecosystem team, and we manage EKS clusters for our developer teams so they don't have to. We provide them with the necessary tools to run on top of the cluster. EKS helps us simplify and speed up cluster management. We don't have to take care of cluster updates; we just initiate the update, and AWS handles it. The same goes for some of the AWS-managed add-ons.
For EKS, we deployed a Django application. The application built the whole image and stored it in ECR (Elastic Container Registry). We stored the code repository in GitHub, but the image was in ECR. We also had another repository for the Kubernetes manifest files. So we were deploying it in a different image, and the code was in a different image. We had a whole pipeline for deployment, from CodePipeline to ECR, and then from ECR to Kubernetes. I work with different AWS solutions, such as Elastic Beanstalk, AWS Lambda, DynamoDB, and VPC. I use services like EC2, S3, and VPC every day, so I'm not including those. I've also used API Gateway, and currently, I also use AWS Bedrock.
I used Amazon EKS for my personal learning purposes. I used the solution to learn how to initiate and upgrade the Kubernetes cluster for testing in my own lab.
The use case for Amazon EKS is for a payment gateway corporation whose applications run on microservices. Their software team develops cloud-native applications. They use Amazon's public cloud for these applications but find it expensive. They want a less expensive solution for their customers. We suggest using Amazon EKS open-source solutions. By using these solutions on-premises, they don't have to pay Amazon.
I use the solution for its microservices. I used the product in some of my personal projects for deploying applications. From an organizational standpoint, the product is useful for its microservices.
We use Amazon EKS as an APM tool for the environment while migrating the monolithic architecture to microservices architecture. It helps us to test product functionality in a particular environment.
The solution can be described as a microservice, and it is also a fully containerized platform. The solution can be described as a stateless service. Amazon EKS can be a great solution for deployments since it supports autoscaling and keeps scaling as well. In my company, we only pay for the resources we use, and owing to such a concept, we use the solution in our company.
It's a great service because we can do a lot of things using it. It's easy to create clusters and services in pods there. So, the main purpose is to create clusters and services and define some pods there.
Specialist Data Analysis vehicle safety at Cubeware
Real User
2022-10-27T13:01:20Z
Oct 27, 2022
Our primary case is using Amazon EKS with all of our data in our MapReduce, map clusters, and our data clusters. And from there, we just input the information using Python and do our analysis using that.
Solution Architect Grade I at a tech services company with 5,001-10,000 employees
Real User
2022-09-08T13:19:00Z
Sep 8, 2022
Our client is doing some image analysis, and we need a robust system that won't go down during the image rotation, so we are using Amazon EKS. With this solution, our services will not go down during their work, and data will remain safe and available to the user.
Our client in the healthcare industry has multiple clinics and patients who use the solution to interact with their portal and insert patient details. Patient information is managed via databases created in the solution.
Cloud Architect & Devops engineer at KdmConsulting
Real User
2022-07-09T03:27:16Z
Jul 9, 2022
We use this solution for containerization and push containers into the EKS or CI/CD pipeline in the DevOps pipeline. It's very easy and well-managed for autoscale as we can manage our node groups. In addition, we can tailor autoscaling to our needs.
Solutions Architect at a financial services firm with 1,001-5,000 employees
Real User
Top 10
2022-04-25T09:35:43Z
Apr 25, 2022
Amazon EKS is basically a model provided by Amazon that allows you to create and deploy multiple microservices and manage containers. Once the Kubernetes is installed, we can directly create the container, set up ports, and set up new services. We currently have Java containers running. We have more than 500 people using this solution. We are on version 21.
Solution Architect / Head of DevOps Engineer at a tech services company with 201-500 employees
Real User
2021-06-23T00:52:03Z
Jun 23, 2021
Amazon Elastic Kubernetes Service (EKS) solution integrates AWS cloud with Kubernetes. Kubernetes is an open-source container technology that is popular right now. It has the ability to replicate applications for scaling.
Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.
EKS is the best place to run Kubernetes for several reasons. First, you can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage...
I am working mostly on AWS infrastructure services, such as EC2, EKS, RDS, CloudFormation, IAM, and CloudWatch. I have around one year of experience with Kubernetes and have been using AWS services continuously for three years. My responsibilities include working on server storage, containerization, monitoring, and access policies.
We use EKS in our company to run containerized applications. I work in the container ecosystem team, and we manage EKS clusters for our developer teams so they don't have to. We provide them with the necessary tools to run on top of the cluster. EKS helps us simplify and speed up cluster management. We don't have to take care of cluster updates; we just initiate the update, and AWS handles it. The same goes for some of the AWS-managed add-ons.
For EKS, we deployed a Django application. The application built the whole image and stored it in ECR (Elastic Container Registry). We stored the code repository in GitHub, but the image was in ECR. We also had another repository for the Kubernetes manifest files. So we were deploying it in a different image, and the code was in a different image. We had a whole pipeline for deployment, from CodePipeline to ECR, and then from ECR to Kubernetes. I work with different AWS solutions, such as Elastic Beanstalk, AWS Lambda, DynamoDB, and VPC. I use services like EC2, S3, and VPC every day, so I'm not including those. I've also used API Gateway, and currently, I also use AWS Bedrock.
I used Amazon EKS for my personal learning purposes. I used the solution to learn how to initiate and upgrade the Kubernetes cluster for testing in my own lab.
The use case for Amazon EKS is for a payment gateway corporation whose applications run on microservices. Their software team develops cloud-native applications. They use Amazon's public cloud for these applications but find it expensive. They want a less expensive solution for their customers. We suggest using Amazon EKS open-source solutions. By using these solutions on-premises, they don't have to pay Amazon.
We use Amazon EKS to manage containerization within our microservices environment.
I use the solution for its microservices. I used the product in some of my personal projects for deploying applications. From an organizational standpoint, the product is useful for its microservices.
We use Amazon EKS as an APM tool for the environment while migrating the monolithic architecture to microservices architecture. It helps us to test product functionality in a particular environment.
The solution can be described as a microservice, and it is also a fully containerized platform. The solution can be described as a stateless service. Amazon EKS can be a great solution for deployments since it supports autoscaling and keeps scaling as well. In my company, we only pay for the resources we use, and owing to such a concept, we use the solution in our company.
It's a great service because we can do a lot of things using it. It's easy to create clusters and services in pods there. So, the main purpose is to create clusters and services and define some pods there.
The main use case is Cloud and IT applications.
We deploy different solutions on the EKS cluster for our clients to use.
I use EKS as an application management system and a second application server. It's connected to Amazon RDS.
I have clients that run on Kubernetes engines.
The product helps to create a new environment fast.
We run all our microservices across the globe with Amazon EKS. We also use it for development, testing, and maintenance.
I use Amazon EKS for telco event monitoring.
It's mainly deployed on a public cloud.
We just implemented the acquisition project for our cloud application environment, and we implemented Amazon EKS.
Our primary case is using Amazon EKS with all of our data in our MapReduce, map clusters, and our data clusters. And from there, we just input the information using Python and do our analysis using that.
Our client is doing some image analysis, and we need a robust system that won't go down during the image rotation, so we are using Amazon EKS. With this solution, our services will not go down during their work, and data will remain safe and available to the user.
Our client in the healthcare industry has multiple clinics and patients who use the solution to interact with their portal and insert patient details. Patient information is managed via databases created in the solution.
We use this solution for containerization and push containers into the EKS or CI/CD pipeline in the DevOps pipeline. It's very easy and well-managed for autoscale as we can manage our node groups. In addition, we can tailor autoscaling to our needs.
Amazon EKS is basically a model provided by Amazon that allows you to create and deploy multiple microservices and manage containers. Once the Kubernetes is installed, we can directly create the container, set up ports, and set up new services. We currently have Java containers running. We have more than 500 people using this solution. We are on version 21.
I have tried to host the enterprise content management application of IBM FileNet on Amazon EKS. That's the main use case.
We use Amazon Elastic Kubernetes Service (EKS) to manage our containers and to run and scale Kubernetes applications in the cloud.
Amazon Elastic Kubernetes Service (EKS) solution integrates AWS cloud with Kubernetes. Kubernetes is an open-source container technology that is popular right now. It has the ability to replicate applications for scaling.