Jump to content

Search the Community

Showing results for tags 'eks'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Welcome New Members !
    • General Discussion
    • Ask a Question
    • Site News
  • DevOps & SRE
    • DevOps & SRE
    • Databases
    • Development
    • CI/CD
    • Docker, Containers & Serverless
    • Infrastructure-as-Code
    • Kubernetes
    • Linux
    • Logging, Monitoring & Observability
    • Security
  • Cloud Providers
    • AWS
    • Azure
    • GCP
    • OpenShift

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL

LinkedIn Profile URL

About Me

Development Experience

Cloud Experience

Current Role



Favourite Tools


  1. In this post, we’ll illustrate an enterprise IT scenario in which VPCs are overseen by a central network team, including configuration of VPC resources such as IP allocation, route policies, internet gateways, NAT gateways, security groups, peering, and on-premises connectivity. The network account, which serves as the owner of the centralized VPC, shares subnets with a participant application account managed by a platform team, both of which are part of the same organization. In this use case, the platform team owns the management of Amazon EKS cluster. We’ll also cover the key considerations of using shared subnets in Amazon EKS... View the full article
  2. The Amazon Elastic Kubernetes Service (Amazon EKS) team is pleased to announce support for Kubernetes version 1.28 for Amazon EKS and Amazon EKS Distro. Amazon EKS Anywhere (release 0.18.0) also supports Kubernetes 1.28. The theme for this version was chosen as a play on words that combines plant and Kubernetes to evoke the image of a garden. Hence, the fitting release name, Planternetes. In their official release announcement, the Kubernetes release team said this of the release, “people behind this release come from a wide range of backgrounds.” View the full article
  3. Today, we are excited to announce that Amazon EMR on EKS now supports managed Apache Flink, available in public preview. With this launch, customers who already use EMR can run their Apache Flink application along with other types of applications on the same Amazon EKS cluster, helping improve resource utilization and simplify infrastructure management. For customers who already run big data frameworks on Amazon EKS, they can now let Amazon EMR automate provisioning and management. View the full article
  4. Amazon GuardDuty announces a new capability in GuardDuty EKS Runtime Monitoring that allows you to selectively configure which Amazon Elastic Kubernetes Service (Amazon EKS) clusters are to be monitored for threat detection. Previously, configurability was at the account level only. With this added cluster-level configurability, customers can now selectively monitor EKS clusters for threat detection or continue to use account level configurability to monitor all EKS clusters in a given account and region. View the full article
  5. We are excited to announce support for Amazon Linux 2023 (AL2023) on Amazon EMR on EKS. Customers can now use AL2023 as the operating system together with Java 17 as Java runtime to run Spark workloads on Amazon EMR on EKS. This provides customers a secure, stable, high-performance environment to develop and run their applications as well as enables them to access the latest enhancements such as kernel, toolchain, glibc, openssl and other system libraries and utilities. View the full article
  6. While AWS ECS and EKS serve a similar purpose, they have several fundamental differences. Here's what you should know. View the full article
  7. This post demonstrates a proof-of-concept implementation that uses Kubernetes to execute code in response to an event. View the full article
  8. We are excited to announce that Amazon EMR on EKS now supports programmatic execution of Jupyter notebooks when running interactive workloads via managed endpoints. Amazon EMR on EKS enables customers to run open-source big data frameworks such as Apache Spark on Amazon EKS. Amazon EMR on EKS customers can setup and use a managed endpoint (available in preview) to run interactive workloads using integrated development environments (IDEs) such as EMR Studio. View the full article
  9. The Amazon GuardDuty EKS Runtime Monitoring eBPF security agent now supports Amazon Elastic Kubernetes Service (Amazon EKS) workloads that use the Bottlerocket operating system, AWS Graviton processors, and AMD64 processors. Additionally, the new agent version (1.2.0) introduces performance enhancements, built-in CPU and memory utilization limits, and support for Amazon EKS 1.27 clusters. If you use GuardDuty EKS Runtime Monitoring with automated agent management then GuardDuty will automatically upgrade the security agent for your Amazon EKS clusters. If you are not using automated agent management, you are responsible for upgrading the agent manually. You can view the current agent version running in your Amazon EKS clusters in the EKS clusters runtime coverage page of the GuardDuty console. If you are not yet using GuardDuty EKS Runtime Monitoring, you can enable the feature for a 30-day free trial with a few steps. View the full article
  10. Amazon Elastic Kubernetes Service (EKS) now allows running more pods per windows node using IPv4 prefix delegation mode for Windows containers. Prefix delegation mode expands the number of secondary IPv4 addresses which could be assigned to the Elastic Network Interface (ENI) by up to 16x. With this feature, customers can run up to 250 pods on a single Windows Server node, depending upon the chosen instance type and size. View the full article
  11. CoStar is well known as a market leader for Commercial Real Estate data, but they also run major home, rental, and apartments websites —including apartments.com—that many have seen advertised by Jeff Goldblum. CoStar’s traditional Commercial Real Estate customers are highly informed users that use large and complex data to make critical business decisions. Successfully helping customers analyze and decide which of the 6 million properties with 130 billion sq. ft. of space to rent, has made CoStar a leader in data and analytics technology. When CoStar began building the next generation of their Apartments and Homes websites, it became clear the user profile and customer demands had important differences from their long running Commercial Real Estate customers. CoStar needed to deliver the same decision-making value to their new customer base, but for magnitudes more customers and data. This initiated CoStar’s migration from their legacy data centers into AWS for speed and elasticity needed to deliver the same value for millions of users accessing hundreds of millions of properties... View the full article
  12. We are excited to announce support for full cluster lifecycle automation through GitOps or Infrastructure as Code (IaC) tools like Terraform for Amazon EKS Anywhere (EKS-A). Previously, the only mechanism for customers to perform full EKS-A cluster lifecycle operations such as provisioning, updates, and deletion was by using an Amazon command-line-interface (CLI) tool “eksctl”. Now, EKS-A supports GitOps and IaC in the EKS-A management cluster so customers can automate EKS-A workload cluster lifecycle operations including cluster creation, update, and deletion. View the full article
  13. Today, we are excited to announce the general availability of the Amazon Elastic Kubernetes Service (EKS) Anywhere Curated Packages, which are software packages that extend the core functionalities of Kubernetes. You can now install the Harbor package as a local container registry, the Emissary-Ingress package as the ingress controller, and the MetalLB package as the service type load balancer. View the full article
  14. Amazon Elastic Kubernetes Service (Amazon EKS) now allows you to more easily run workloads from various Kubernetes namespaces on AWS Fargate serverless compute with a single EKS Fargate Profile. Using Amazon EKS on AWS Fargate enables you to use Kubernetes without having to worry about compute infrastructure configuration and maintenance. Previously, you had to specify all the namespaces at the time you created the EKS Fargate Profile and were limited to a total of 5 namespace selectors or label pairs. View the full article
  15. Amazon Elastic Kubernetes Service (EKS) now makes it easier for customers to understand how their Amazon EC2 costs are driven by individual EKS clusters. Customers who choose to use multiple EKS clusters to segment their workloads to improve their resilience and/or security posture now get breakdowns of their EC2 costs by EKS cluster using AWS Cost and Usage reporting with minimal additional effort. View the full article
  16. You can now use Amazon EKS and Amazon EKS Distro to run Kubernetes version 1.23. Highlights of Kubernetes version 1.23 release include graduation of PodSecurity and Ephemeral containers to beta, and graduation of HorizontalPodAutoscaler to GA. Additionally, Kubernetes version 1.23 turns on CSI migration feature for Amazon EBS by default. You can find more details about Kubernetes 1.23 release in the EKS blog post, EKS release notes, and in the Kubernetes project release notes. Support for version 1.23 will be available in Amazon EKS Anywhere in the next couple of weeks. View the full article
  17. We are happy to announce the general availability of Amazon EKS Anywhere on Bare Metal. We released Amazon EKS Anywhere in 2021 with support to run on-premises Kubernetes clusters using VMware and today you can use EKS Anywhere to provision clusters without virtualization. The new functionality adds support for managing the full hardware lifecycle to boot, provision, and operate clusters. View the full article
  18. Today, we are excited to announce the general availability of Amazon Elastic Kubernetes Service (Amazon EKS) Anywhere on bare metal which gives customers broader choice of infrastructure for running Kubernetes on-premises. As customers modernize their applications, they want to use Kubernetes consistently between their existing on-premises bare metal infrastructure and the cloud. Running Kubernetes on bare metal infrastructure is complex, and customers spend time, effort and money on infrastructure operations instead of focusing on business innovation. View the full article
  19. At one time, all servers were bare metal servers. We have come a long way with virtualization, cloud computing, and more recently with containers and serverless technologies. Despite these innovations, bare metal servers remain popular on premises. Customers run applications on bare metal infrastructure for performance benefits, to gain direct access to underlying hardware resources, to reduce complexity in their infrastructure stack, and to save on licensing and support costs. As customers modernize their applications, they want to use Kubernetes consistently between their existing on premises bare metal infrastructure and the cloud… View the full article
  20. Years before Amazon Elastic Kubernetes Service (EKS) was released, our customers told us they wanted a service that would simplify Kubernetes management. Many of them were running self-managed clusters on Amazon Elastic Computer Cloud (EC2) and were having challenges upgrading, scaling, and maintaining the Kubernetes control plane. When EKS launched in 2018, it aimed to reduce our customers’ operational burden by offering a managed control plane for Kubernetes. This initially included automated upgrades, patching, and backups, which we often refer to as “undifferentiated heavy lifting.” We analyzed volumes of data to create a control plane that would work for the vast majority of our customers. However, as usage of EKS grew, we discovered there were customers who occasionally exceeded the provisioned capacity of the cluster. When this happened, they had to file a ticket with AWS support to have their cluster control plane resized. This was not an ideal user experience. Today, the control plane is scaled automatically when certain metrics are exceeded. At first, we used basic metrics such as CPU/memory for scaling. As we learned how the control plane behaved under different conditions, we adjusted our metrics to make scaling more responsive. Now we use a variety of metrics to scale the control plane, including the number of worker nodes and the size of the etcd database. These enhancements are a great example of the flywheel effect where AWS releases a feature in response to customer feedback, solicits feedback from end users about its impact, and uses that feedback to continue improving the customer experience... View the full article
  21. It’s every on-call’s nightmare—awakened by a text at 3 a.m. from your alert system that says there’s a problem with the cluster. You need to quickly determine if the issue is with the Amazon EKS managed control plane or the new custom application you just rolled out last week. Even though you installed the default dashboards the blogs recommended, you’re still having difficulty understanding the meaning of the metrics you are looking at. If only you had a dashboard that was focused on the most common problems seen in the field—one where you understood what everything means right away, letting you quickly scan for even obscure issues efficiently… View the full article
  22. You can now resolve the private Kubernetes API server endpoint of your Amazon Elastic Kubernetes Service (EKS) cluster in AWS GovCloud (US) regions. This allows you to easily connect to an EKS cluster that is only accessible within a VPC, including when using AWS services such as AWS Direct Connect and VPC peering. View the full article
  23. Amazon Elastic Kubernetes Service (EKS) Anywhere now allows you to enable Amazon-curated software packages that extend the core functionalities of Kubernetes on your EKS Anywhere clusters. You can install the Harbor package as a local container registry starting today, with the Emissary-Ingress package and the support for service type load balancing through MetalLB coming in the next few months. More curated packages may be added over time based on customer demand. View the full article
  24. Thanks to Marc Weaver at Databasable, who helped us curate few interesting observations he made while working with these services.References:https://aws.amazon.com/eks/pricing/ https://aws.amazon.com/ecs/pricing/ https://aws.amazon.com/fargate/faqs/ https://docs.aws.amazon.com/eks/latest/userguide/s.. View the full article
  25. Amazon Elastic Kubernetes Service (Amazon EKS) now allows you to see all standard Kubernetes API resource types running on your Amazon EKS cluster using the AWS Management Console. This makes it easy to visualize and troubleshoot your Kubernetes applications using Amazon EKS. View the full article
  • Member Statistics

    Total Members
    Most Online
    Newest Member
  • Create New...