amazon-eks-ami
amazon-eks-ami copied to clipboard
awslabs
Packer configuration for building a custom EKS AMI
**Description of changes:** I would like to be able to migrate workloads away from a node gracefully in case of instance storage drive failure. Raid10 would provide redundancy and trade...
**Issue #, if available:** #1984 **Description of changes:** By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your...
**Issue #, if available:** This is to fix an issue when applying EKS scripts on top of CIS_Amazon_Linux_2023_Benchmark_Level_1 AMI **Description of changes:** adding remote folder to shell provisioners scripts on...
**What happened**: There is a bug when you have enabled FIPS on the image, in a region with FIPS endpoints, and have VPC endpoints enabled. The issue is that the...
**Issue #, if available:** https://github.com/awslabs/amazon-eks-ami/issues/1554 **Description of changes:** I corrected `generate-version-info.sh` script so that it does not fail when Packer uses hardened AMIs. Refer to https://github.com/awslabs/amazon-eks-ami/issues/1554 for more info. By...
**Issue #, if available:** Discussed in #1317 **Description of changes:** This allows authenticated `public.ecr.aws` pulls, to avoid the bandwidth limits for anonymous requests. By submitting this pull request, I confirm...
**Issue #, if available:** N/A **Description of changes:** Added a GitHub Action that will summarize issues via: - `/summarize` - *Will summarize the issue in which the command is being...
**Issue #, if available:** N/A **Description of changes:** In the past, a few users have experienced major issues caused by changing kernel parameters from Amazon Linux upstream that were not...
* Added fallback for `ss` from netstat[1]. * Added fallback for `ip addr show` from ifconfig[1]. * Added `nstat` to track network stats such as Reverse Path filters. [1] ifconfig,...
**Description of changes:** This adds an additional check for comment authors that requires them to have either an `admin` or `maintain` role to use the bot. By submitting this pull...