What is Amazon EKS?
Who uses Amazon EKS?
Amazon EKS Integrations
Here are some stack decisions, common use cases and reviews by companies and developers who chose Amazon EKS in their tech stack.
Dear Community Members,
I hope this message finds you well.
I am reaching out to seek guidance and recommendations regarding tools that are best suited for managing Amazon EKS cluster resources. Specifically, I am exploring options that enable effective deployment and customization of resources within an EKS environment.
My objective is to provide my team with the necessary access and capabilities to deploy and customize resources within the AWS EKS cluster. I am keen to learn from the community's expertise and experiences in this area.
Could you kindly share your insights, suggestions, and experiences with tools or platforms that have proven effective for managing AWS EKS cluster resources? Any recommendations or best practices regarding access control and resource management within EKS would be greatly appreciated.
Your valuable input will not only assist in streamlining our resource management processes but will also contribute to our team's efficiency and effectiveness within the EKS environment.
Thank you in advance for your contributions and support.
We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.
We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.
We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.
You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?
We began our hosting journey, as many do, on Heroku because they make it easy to deploy your application and automate some of the routine tasks associated with deployments, etc. However, as our team grew and our product matured, our needs have outgrown Heroku. I will dive into the history and reasons for this in a future blog post.
We decided to migrate our infrastructure to Kubernetes running on Amazon EKS. Although Google Kubernetes Engine has a slightly more mature Kubernetes offering and is more user-friendly; we decided to go with EKS because we already using other AWS services (including a previous migration from Heroku Postgres to AWS RDS). We are still in the process of moving our main website workloads to EKS, however we have successfully migrate all our staging and testing PR apps to run in a staging cluster. We developed a Slack chatops application (also running in the cluster) which automates all the common tasks of spinning up and managing a production-like cluster for a pull request. This allows our engineering team to iterate quickly and safely test code in a full production environment. Helm plays a central role when deploying our staging apps into the cluster. We use CircleCI to build docker containers for each PR push, which are then published to Amazon EC2 Container Service (ECR). An upgrade-operator
process watches the ECR repository for new containers and then uses Helm to rollout updates to the staging environments. All this happens automatically and makes it really easy for developers to get code onto servers quickly. The immutable and isolated nature of our staging environments means that we can do anything we want in that environment and quickly re-create or restore the environment to start over.
The next step in our journey is to migrate our production workloads to an EKS cluster and build out the CD workflows to get our containers promoted to that cluster after our QA testing is complete in our staging environments.
Blog Posts
Rafay Systems
Amazon EKS's Features
- Managed Kubernetes Control Plane - Amazon EKS provides a scalable and highly-available control plane that runs across multiple AWS availability zones.
- Security and Networking - Amazon EKS makes it easy to provide security for your Kubernetes clusters, with advanced features and integrations to AWS services and technology partner solutions.
- Logging - Amazon EKS is integrated with Amazon CloudWatch Logs and AWS CloudTrail to provide visibility and audit history tracking of your cluster and user activity.
- Certified Conformant - Amazon EKS runs upstream Kubernetes and is certified Kubernetes conformant, so you can use all the existing plugins and tooling from the Kubernetes community.