aws / aws/eks-anywhere

Kubernetes API audit logs enabled on EKS-A clusters to be able to debug and log RBAC issues

Open
#6,975 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What would you like to be added**:

Currently, this can be enabled manually following the Log Backend configuration here:

https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/

EKSA Should allow configuring audit logging through EKS-A Cluster configuration file so that, manual modification to the API server config can be avoided.

**Why is this needed**:
Security and audit purposes.

As a EKSA Admin, I want to know who deleted a application pod or retrieved a secret value from Cluster using Audit logs.

Contributor guide

Open the contributing guide

Research direction

Start with the Kubernetes audit logging and Log Backend configuration documentation linked in the issue, then trace how EKS-A cluster configuration reaches the API server configuration. Done means audit logging can be configured through the EKS-A Cluster configuration file without manual API server changes, with logs sufficient to investigate RBAC actions.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
infrastructure, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.