content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
that it has been completed: ```bash kubectl get job busybox -w # will take two and a half minutes kubectl delete jobs busybox ``` ### Create the same job, but make it run 5 parallel times show ```bash vi job.yaml ``` Add job.spec.parallelism=5 ```YAML apiVersion: batch/v1 kind: Job metadata: creationTimestamp: null lab... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//c.pod_design.md | main | ckad-exercises | [
-0.022765347734093666,
0.008600263856351376,
-0.01895180344581604,
-0.010166425257921219,
-0.019462846219539642,
-0.04410543292760849,
-0.08474839478731155,
-0.07735586166381836,
0.06415203958749771,
0.027441831305623055,
0.01751987263560295,
-0.06625648587942123,
-0.06233847886323929,
-0.... | 0.075896 |
Kubernetes cluster image: busybox name: time-limited-job resources: {} restartPolicy: Never schedule: '\* \* \* \* \*' status: {} ``` ### Create a cron job with image busybox that runs every minute and writes 'date; echo Hello from the Kubernetes cluster' to standard output. The cron job should be terminated if it succ... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//c.pod_design.md | main | ckad-exercises | [
0.055504921823740005,
0.0411076657474041,
0.004404256585985422,
-0.004031650722026825,
0.016973024234175682,
0.004989690613001585,
-0.05027543008327484,
-0.004617620259523392,
0.056044962257146835,
0.04797440394759178,
-0.038568299263715744,
-0.06502639502286911,
-0.04081462323665619,
0.00... | 0.080297 |
 # Services and Networking (13%) ### Create a pod with image nginx called nginx and expose its port 80 show ```bash kubectl run nginx --image=nginx --restart=Never --port=80 --expose # observe that a pod as well as a service are created ``` ###... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//f.services.md | main | ckad-exercises | [
-0.005582126788794994,
-0.0128592848777771,
-0.04212493821978569,
0.020518749952316284,
-0.020800143480300903,
-0.03580799698829651,
-0.004636344965547323,
-0.09941046684980392,
0.07398176193237305,
0.07822683453559875,
0.0037132096476852894,
-0.053311098366975784,
-0.01945945993065834,
-0... | 0.1191 |
--port=6262 --target-port=8080 kubectl get service foo # you will see ClusterIP as well as port 6262 kubectl get endpoints foo # you will see the IPs of the three replica pods, listening on port 8080 ``` ### Create a temp busybox pod and connect via wget to foo service. Verify that each time there's a different hostnam... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//f.services.md | main | ckad-exercises | [
-0.0028672891203314066,
-0.0527852326631546,
-0.011271192692220211,
-0.02002634108066559,
-0.02741115726530552,
-0.06468033790588379,
-0.06945788860321045,
-0.1030997633934021,
0.09165060520172119,
0.034354619681835175,
-0.01937149278819561,
-0.04747395217418671,
-0.045370232313871384,
-0.... | 0.127223 |
# Define, build and modify container images - Note: The topic is part of the new CKAD syllabus. Here are a few examples of using \*\*podman\*\* to manage the life cycle of container images. The use of \*\*docker\*\* had been the industry standard for many years, but now large companies like [Red Hat](https://www.redhat... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//j.podman.md | main | ckad-exercises | [
-0.051447466015815735,
0.03799561411142349,
0.059736523777246475,
-0.04636351391673088,
-0.006536094471812248,
-0.019997671246528625,
0.010843035764992237,
-0.010563447140157223,
0.03611500561237335,
0.0621616393327713,
0.0017865021945908666,
-0.03975566104054451,
0.009249315597116947,
-0.... | 0.18995 |
skipped: already exists Copying blob 8e47efbf2b7e skipped: already exists Copying blob 42e0f5a91e40 skipped: already exists Copying config ef4b14a72d done Writing manifest to image destination Storing signatures ef4b14a72d02ae0577eb0632d084c057777725c279e12ccf5b0c6e4ff5fd598b ``` ### Create a container without running/... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//j.podman.md | main | ckad-exercises | [
0.05324007570743561,
-0.0038975237403064966,
0.06038430333137512,
-0.05311981961131096,
0.10692444443702698,
-0.06430863589048386,
0.01687020994722843,
-0.014002122916281223,
0.033355969935655594,
0.017356447875499725,
0.023595580831170082,
-0.09853110462427139,
-0.019491072744131088,
-0.0... | 0.018481 |
 # Configuration (18%) [ConfigMaps](#configmaps) [SecurityContext](#securitycontext) [Resource Requests and Limits](#resource-requests-and-limits) [Limit Ranges](#limit-ranges) [Resource Quotas](#resource-quotas) [Secrets](#secrets) [Servi... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//d.configuration.md | main | ckad-exercises | [
-0.020712601020932198,
0.022850558161735535,
-0.05587806552648544,
0.036950044333934784,
-0.02024272456765175,
-0.012471089139580727,
0.04436682164669037,
-0.04825790226459503,
0.03374375030398369,
0.09627322852611542,
0.002310783602297306,
-0.09753306210041046,
0.06344665586948395,
-0.027... | 0.095906 |
- name: myvolume # the name that you specified in pod.spec.volumes.name mountPath: /etc/lala # the path inside your container dnsPolicy: ClusterFirst restartPolicy: Never status: {} ``` ```bash kubectl create -f pod.yaml kubectl exec -it nginx -- /bin/sh cd /etc/lala ls # will show var8 var9 cat var8 # will show val8 `... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//d.configuration.md | main | ckad-exercises | [
0.0256145391613245,
-0.0386284738779068,
-0.01148432120680809,
-0.037648383527994156,
-0.045382656157016754,
0.00626859487965703,
-0.01649465225636959,
0.027992263436317444,
0.03918259218335152,
0.01631215214729309,
-0.03713955357670784,
-0.06090417876839638,
0.01826118864119053,
0.0172245... | 0.13023 |
2Gi ``` ```bash kubectl apply -f rq-one.yaml ``` or ```bash kubectl create quota my-rq --namespace=one --hard=requests.cpu=1,requests.memory=1Gi,limits.cpu=2,limits.memory=2Gi ``` ### Attempt to create a pod with resource requests `cpu=2`, `memory=3Gi` and limits `cpu=3`, `memory=4Gi` in namespace `one` show ```bash vi... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//d.configuration.md | main | ckad-exercises | [
0.04130001738667488,
-0.0014437698991969228,
-0.01585792936384678,
-0.004007688723504543,
-0.04399885609745979,
-0.054698627442121506,
-0.007869605906307697,
-0.01462493184953928,
0.12819114327430725,
0.05675170570611954,
-0.054800521582365036,
-0.07698965817689896,
-0.014743758365511894,
... | 0.09715 |
pod in env variable called 'USERNAME' show ```bash kubectl delete po nginx kubectl run nginx --image=nginx --restart=Never -o yaml --dry-run=client > pod.yaml vi pod.yaml ``` ```YAML apiVersion: v1 kind: Pod metadata: creationTimestamp: null labels: run: nginx name: nginx spec: containers: - image: nginx imagePullPolic... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//d.configuration.md | main | ckad-exercises | [
0.01707454025745392,
0.035782720893621445,
0.00880847405642271,
-0.013023185543715954,
-0.010948480106890202,
-0.039808180183172226,
0.03835636377334595,
0.001219556201249361,
0.1101950854063034,
0.014590686187148094,
-0.015048437751829624,
-0.06456302851438522,
-0.02425326593220234,
-0.01... | 0.100956 |
Create an nginx pod that uses 'myuser' as a service account show ```bash kubectl run nginx --image=nginx --restart=Never -o yaml --dry-run=client > pod.yaml vi pod.yaml ``` ```YAML apiVersion: v1 kind: Pod metadata: creationTimestamp: null labels: run: nginx name: nginx spec: serviceAccountName: myuser # we use pod.spe... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//d.configuration.md | main | ckad-exercises | [
0.013807447627186775,
-0.0032613908406347036,
0.016731737181544304,
-0.04169506952166557,
-0.06470629572868347,
-0.04944738373160362,
0.025871803984045982,
-0.0014837534399703145,
0.06729209423065186,
0.026946967467665672,
-0.05273584648966789,
-0.06738051027059555,
-0.03702884167432785,
0... | 0.098026 |
 # Observability (18%) ## Liveness, readiness and startup probes kubernetes.io > Documentation > Tasks > Configure Pods and Containers > [Configure Liveness, Readiness and Startup Probes](https://kubernetes.io/docs/tasks/configure-pod-cont... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//e.observability.md | main | ckad-exercises | [
0.0020813876762986183,
-0.0010188795858994126,
0.005300083663314581,
0.019263727590441704,
0.035644013434648514,
-0.03334309160709381,
-0.04504907503724098,
-0.08179877698421478,
0.024375461041927338,
0.08845220506191254,
-0.025037404149770737,
-0.043512482196092606,
0.023784680292010307,
... | 0.061296 |
### Create a busybox pod that runs 'ls /notexist'. Determine if there's an error (of course there is), see it. In the end, delete the pod show ```bash kubectl run busybox --restart=Never --image=busybox -- /bin/sh -c 'ls /notexist' # show that there's an error kubectl logs busybox kubectl describe po busybox kubectl de... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//e.observability.md | main | ckad-exercises | [
0.06551553308963776,
0.01614266447722912,
0.05337759852409363,
-0.020466485992074013,
0.043906934559345245,
-0.04826240986585617,
-0.012985399924218655,
-0.023550570011138916,
0.11221205443143845,
0.025383317843079567,
0.027884237468242645,
-0.08327338099479675,
-0.01882859319448471,
-0.03... | 0.127505 |
[](LICENSE) [](http://makeapullrequest.com) [ # Core Concepts (13%) kubernetes.io > Documentation > Reference > kubectl CLI > [kubectl Cheat Sheet](https://kubernetes.io/docs/reference/kubectl/cheatsheet/) kubernetes.io > Documentation > Tasks > Monitoring, Logging, and Debugging > ... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//a.core_concepts.md | main | ckad-exercises | [
0.04394781216979027,
0.00910128653049469,
-0.031944166868925095,
-0.01802685670554638,
0.005371870007365942,
0.00609119376167655,
-0.0043129753321409225,
-0.03911598026752472,
0.02593010663986206,
0.0927530974149704,
-0.026798686012625694,
-0.08989737182855606,
0.026424484327435493,
-0.043... | 0.159394 |
recreated' kubectl get po nginx -w # watch it ``` \*Note\*: some time after changing the image, you should see that the value in the `RESTARTS` column has been increased by 1, because the container has been restarted, as stated in the events shown at the bottom of the `kubectl describe pod` command: ``` Events: Type Re... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//a.core_concepts.md | main | ckad-exercises | [
0.017736732959747314,
0.023005815222859383,
0.05119086056947708,
0.0001796538708731532,
0.022893792018294334,
-0.06920915842056274,
-0.0012817762326449156,
-0.024128993973135948,
0.09495782852172852,
0.032437585294246674,
-0.0024957219138741493,
-0.024935929104685783,
-0.04439181834459305,
... | 0.120855 |
# Extend the Kubernetes API with CRD (CustomResourceDefinition) - Note: CRD is part of the new CKAD syllabus. Here are a few examples of installing custom resource into the Kubernetes API by creating a CRD. ## CRD in K8s ### Create a CustomResourceDefinition manifest file for an Operator with the following specificatio... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//i.crd.md | main | ckad-exercises | [
-0.02821207605302334,
0.002792003331705928,
0.06310001015663147,
-0.05049898102879524,
-0.08503986150026321,
0.06281030178070068,
-0.022261004894971848,
-0.0007085314719006419,
0.06563284248113632,
0.044065315276384354,
-0.044417448341846466,
-0.09519512951374054,
-0.008328622207045555,
0.... | 0.116762 |
 # Multi-container Pods (10%) ### Create a Pod with two containers, both with image busybox and command "echo hello; sleep 3600". Connect to the second container and run 'ls' show The easiest way to do it is create a pod with a single c... | https://github.com/dgkanatsios/CKAD-exercises/blob/main//b.multi_container_pods.md | main | ckad-exercises | [
0.05632511526346207,
0.019231753423810005,
0.00606205128133297,
0.032272953540086746,
-0.0020432230085134506,
-0.017689667642116547,
0.004826492164283991,
-0.034477002918720245,
0.039364539086818695,
0.06996282190084457,
0.012326724827289581,
-0.09860748052597046,
0.053749796003103256,
-0.... | 0.044937 |
//!!NODE\_ROOT [."topic"] [[contribute,contribute.title]] = Contribute to this guide :info\_doctype: chapter :info\_titleabbrev: Contribute Anyone can contribute to the best practices guide. The EKS Best Practices Guide is written in the AsciiDoc format on GitHub. == Summary for existing contributors \* Open the https:... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/contribute.adoc | mainline | aws-eks-best-practices | [
-0.07625415176153183,
0.06607616692781448,
-0.08143480867147446,
0.07083369046449661,
0.024589432403445244,
0.017030835151672363,
-0.045431360602378845,
0.01230045035481453,
0.09582872688770294,
0.01949349232017994,
0.030723394826054573,
-0.08247910439968109,
0.017064249143004417,
-0.04735... | 0.186694 |
Edit a single page You can rapidly update individual pages by using GitHub. Each page contains an "📝 Edit this page on GitHub" link at the bottom. . Navigate to the page in this guide you want to edit . Click the "Edit this page on GitHub" link at the bottom . Click the edit pencil icon on the top right of the GitHub ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/contribute.adoc | mainline | aws-eks-best-practices | [
-0.09238580614328384,
-0.015457198023796082,
-0.019474603235721588,
0.04470103979110718,
0.03648360073566437,
-0.016775602474808693,
-0.1288885623216629,
-0.002953367307782173,
0.018054576590657234,
0.07556174695491791,
-0.040954869240522385,
0.11021110415458679,
0.045358967036008835,
-0.0... | 0.059028 |
"diagram of VPC with three availability zones" is appropriate alt-text. . Update the following example with the alt-text and image filename. Insert at the desired location. + ==== +image::[]+ ==== + For example, + ==== +image::eks-data-plane-connectivity.jpeg[Network diagram]+ ==== == Check style with Vale . https://va... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/contribute.adoc | mainline | aws-eks-best-practices | [
-0.009671875275671482,
0.010201476514339447,
-0.040534909814596176,
0.07508911937475204,
0.029943225905299187,
0.0025997308548539877,
-0.06956851482391357,
0.009266058914363384,
0.05595758557319641,
-0.05996834114193916,
0.055132731795310974,
-0.05869089066982269,
0.010385979898273945,
-0.... | 0.131351 |
//!!NODE\_ROOT [[top]] = Amazon EKS :doctype: book :toc: left :icons: font :experimental: :idprefix: :idseparator: - :info\_doctype: book :info\_title: Amazon EKS :info\_subtitle: Best Practices Guide :info\_abstract: Learn best practices for operating EKS clusters. :info\_corpauthor: AWS :info\_publisher: AWS :info\_c... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/book.adoc | mainline | aws-eks-best-practices | [
-0.04886502027511597,
0.03165654093027115,
0.006021933164447546,
-0.02815173752605915,
0.06203147768974304,
-0.0034641255624592304,
0.042477816343307495,
-0.05074586719274521,
0.06061211973428726,
0.01600143313407898,
0.04179910942912102,
-0.014979937113821507,
0.0791485533118248,
-0.07582... | 0.173043 |
//!!NODE\_ROOT [."topic"] [[introduction,introduction.title]] = Amazon EKS Best Practices Guide :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Amazon EKS Best Practices Guide :info\_titleabbrev: Introduction :info\_abstract... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/index.adoc | mainline | aws-eks-best-practices | [
-0.060038972645998,
0.06549834460020065,
0.013675806112587452,
0.06805810332298279,
0.00000857623035699362,
-0.0347098633646965,
-0.027629954740405083,
-0.03534239903092384,
0.021022170782089233,
0.05873233079910278,
0.0025457129813730717,
-0.00019696488743647933,
0.03329697623848915,
-0.0... | 0.199377 |
//!!NODE\_ROOT [."topic"] [[aiml-networking,aiml-networking.title]] = AI/ML on EKS - Networking :info\_doctype: section :imagesdir: images/ :info\_title: Networking :info\_abstract: Networking :info\_titleabbrev: Networking :authors: ["Leah Tucker"] :date: 2025-05-30 TIP: https://aws-experience.com/emea/smb/events/seri... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_networking.adoc | mainline | aws-eks-best-practices | [
-0.016448302194476128,
0.02931137941777706,
0.013834334909915924,
0.049234796315431595,
0.048823125660419464,
-0.021815551444888115,
0.012421662919223309,
-0.01742715947329998,
0.037544406950473785,
0.06437727063894272,
-0.04802779480814934,
-0.02017565444111824,
0.007917382754385471,
-0.0... | 0.169862 |
//!!NODE\_ROOT [."topic"] [[aiml-performance,aiml-performance.title]] = AI/ML on EKS - Performance :info\_doctype: section :imagesdir: images/ :info\_title: Application Scaling and Performance :info\_abstract: Application Scaling and Performance :info\_titleabbrev: Performance :authors: ["Leah Tucker"] :date: 2025-05-3... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_performance.adoc | mainline | aws-eks-best-practices | [
-0.026709022000432014,
0.03363823518157005,
0.018495680764317513,
0.06383182853460312,
0.1028369590640068,
-0.038381293416023254,
-0.02891630306839943,
-0.0031115980818867683,
0.036858830600976944,
0.045109204947948456,
-0.03644587844610214,
-0.018116693943738937,
0.030381781980395317,
-0.... | 0.185508 |
extra infrastructure, compatible with all HuggingFace models, simple Kubernetes deployment. \* \*\*Cons\*\*: Restricts to single request/simple batching, slow token generation (no optimized kernels), memory inefficient, lacks scaling/monitoring, and involves long startup times. \* \*\*Recommendation\*\*: Use for initia... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_performance.adoc | mainline | aws-eks-best-practices | [
-0.04895615950226784,
-0.07629621773958206,
0.0240112766623497,
-0.025955157354474068,
0.011752546764910221,
-0.02572295069694519,
-0.08832940459251404,
0.03290313109755516,
0.009307590313255787,
0.01545813586562872,
-0.05963246151804924,
-0.01915844902396202,
-0.03151079639792442,
-0.0005... | 0.291747 |
to the node\*:: For layer fetch optimization, SOCI creates multiple concurrent HTTP connections per layer, multiplying download throughput beyond the single-connection limitation. It splits large layers into chunks and downloads them simultaneously across multiple connections. This approach helps saturate your availabl... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_performance.adoc | mainline | aws-eks-best-practices | [
-0.07476798444986343,
0.0704396441578865,
-0.028387118130922318,
0.03115096315741539,
0.030962860211730003,
-0.06584220379590988,
0.011793320067226887,
-0.0071646361611783504,
0.02383340708911419,
0.03374643251299858,
-0.04542645812034607,
0.037850312888622284,
-0.013213408179581165,
-0.06... | 0.22264 |
nodes scale in/out, new nodes added by tools like Cluster Autoscaler may schedule workload pods before the pre-pull DaemonSet completes image pulling. This can cause the initial pod on the new node to trigger the pull anyway, potentially delaying startup and impacting low-latency requirements. Additionally, kubelet ima... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_performance.adoc | mainline | aws-eks-best-practices | [
0.00738013070076704,
0.08894561231136322,
0.0694555789232254,
0.0602872408926487,
0.02616402879357338,
-0.03293916955590248,
-0.01740996167063713,
0.0064124432392418385,
0.061069075018167496,
0.04669288918375969,
0.028694195672869682,
0.026011040434241295,
-0.012057764455676079,
-0.0422925... | 0.145206 |
//!!NODE\_ROOT [."topic"] [[aiml-security,aiml-security.title]] = AI/ML on EKS - Security :info\_doctype: section :imagesdir: images/ :info\_title: Security :info\_abstract: Security :info\_titleabbrev: Security :authors: ["Leah Tucker"] :date: 2025-07-01 TIP: https://aws-experience.com/emea/smb/events/series/get-hands... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_security.adoc | mainline | aws-eks-best-practices | [
-0.025987207889556885,
0.020227743312716484,
-0.04606961831450462,
0.02238008938729763,
0.07442480325698853,
-0.0031106884125620127,
0.003380321431905031,
-0.037463679909706116,
0.12214971333742142,
0.050815556198358536,
-0.028906896710395813,
-0.024174313992261887,
0.06232975423336029,
-0... | 0.068401 |
//!!NODE\_ROOT [."topic"] [[aiml-storage,aiml-storage.title]] = AI/ML on EKS - Storage :info\_doctype: section :imagesdir: images/ :info\_title: Storage :info\_abstract: Storage :info\_titleabbrev: Storage :authors: ["Leah Tucker"] :date: 2025-05-30 TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-wi... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.016459118574857712,
0.04556005820631981,
0.04553493112325668,
0.07179993391036987,
0.06266163289546967,
-0.05562533065676689,
-0.025073125958442688,
0.027043981477618217,
0.10622021555900574,
0.0624108612537384,
0.003599149640649557,
-0.025456687435507774,
0.0712021142244339,
0.00071882... | 0.168416 |
serving, and you require native Amazon S3 data repository integration, we recommend https://docs.aws.amazon.com/fsx/latest/LustreGuide/what-is.html[Amazon FSx for Lustre]. FSx for Lustre provides a fully managed high performance parallel filesystem that is designed for compute-intensive workloads like high-performance ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.06960394233465195,
-0.023971011862158775,
-0.06326458603143692,
-0.013559023849666119,
0.0209638811647892,
-0.04551157355308533,
-0.06546204537153244,
0.02893754281103611,
0.011530672200024128,
0.0535612516105175,
-0.0399739034473896,
0.024358177557587624,
0.028076281771063805,
-0.02837... | 0.104347 |
larger than the `ImportedFileChunkSize` will be stored on multiple OSTs with a stripe count based on the `ImportedFileChunkSize` defined value (default 1GiB). If you have large files, we recommend tuning this parameter to a higher value. \*\* \*\*Placement\*\*: Deploy an FSx for Lustre file system in the same Availabil... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.016298197209835052,
-0.007294349372386932,
-0.09370681643486023,
0.010255987755954266,
0.02101152576506138,
-0.04157394915819168,
-0.06496810913085938,
0.1241602748632431,
-0.04500658065080643,
0.003884561825543642,
-0.02307802252471447,
0.03681674227118492,
-0.010509178973734379,
-0.00... | 0.052946 |
\* \*\*API request charges\*\*: When performing a high number of file operations with the Mountpoint for S3, API request charges can become a portion of storage costs. To mitigate this, if strong consistency is not required, always enable metadata caching and set the `metadata-ttl` period to reduce the number of API op... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.03189610689878464,
0.005836373660713434,
-0.04271221160888672,
0.026907792314887047,
0.09363104403018951,
-0.06562331318855286,
-0.05083007737994194,
-0.021181700751185417,
0.13000500202178955,
0.055181268602609634,
-0.03806788846850395,
0.0162921454757452,
0.07390495389699936,
-0.01943... | 0.09544 |
\* \*\*Storage Class:\*\* FSx for OpenZFS supports both the https://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/performance-ssd.html[SSD storage] class as well as the https://docs.aws.amazon.com/fsx/latest/OpenZFSGuide/performance-intelligent-tiering.html[Intelligent-Tiering] storage class. For AI/ML workloads it is re... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.04403313994407654,
0.07665349543094635,
-0.0695028156042099,
0.0628710463643074,
0.09086526930332184,
-0.06656620651483536,
-0.026325881481170654,
-0.002674002666026354,
0.042929209768772125,
0.030976178124547005,
-0.07207254320383072,
0.1053861528635025,
0.04376830533146858,
-0.0501781... | 0.125125 |
Claim (PVC) that is backed by an EFS file system is created as an https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html[EFS Access-point to the EFS file system]. EFS allows multiple nodes and pods to access the same model files, eliminating the need to sync data to each node's filesystem. https://docs.aws.am... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.07381328195333481,
-0.0015961425378918648,
-0.00964057631790638,
0.05344197526574135,
0.10268815606832504,
-0.026562603190541267,
-0.03210986778140068,
0.01029288675636053,
0.05835435539484024,
0.10838735103607178,
-0.002299918094649911,
-0.016495617106556892,
0.04356100782752037,
-0.03... | 0.191566 |
using the Mountpoint S3 CSI Driver with S3 Express One Zone is caching. The first instance reads data from S3 Standard (general purpose), caching it in lower-latency Express One Zone. Subsequent reads by other clients access the cached data faster, which is ideal for multi-node scenarios where multiple EKS nodes read t... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_storage.adoc | mainline | aws-eks-best-practices | [
-0.030641594901680946,
-0.04769546166062355,
-0.015010167844593525,
0.01803913153707981,
0.08500207215547562,
-0.07129573076963425,
-0.07452556490898132,
-0.00124647025950253,
0.053069185465574265,
0.025829220190644264,
-0.07748878002166748,
0.031159106642007828,
0.03232543170452118,
-0.03... | 0.157797 |
//!!NODE\_ROOT [."topic"] [[aiml-compute,aiml-compute.title]] = AI/ML on EKS - Compute :info\_doctype: section :imagesdir: images/ :info\_title: Compute and Autoscaling :info\_abstract: Compute and Autoscaling :info\_titleabbrev: Compute :authors: ["Leah Tucker"] :date: 2025-05-30 TIP: https://aws-experience.com/emea/s... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.04391438141465187,
0.06651998311281204,
-0.013092088513076305,
0.06547624617815018,
-0.006562435533851385,
-0.06301243603229523,
0.0024258075281977654,
-0.020879125222563744,
0.04196871072053909,
0.027516063302755356,
-0.05667166784405708,
-0.08167637884616852,
0.016712093725800514,
-0.... | 0.148447 |
available. It’s important to understand the unique characteristics of your AI/ML workloads before diversifying arbitrarily. Review the available instance types using the https://aws.amazon.com/ec2/instance-explorer/[EC2 Instance Type Explorer] tool to generate a list of instance types that match your specific compute r... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.0108374347910285,
-0.06331220269203186,
-0.010851472616195679,
0.071441650390625,
0.014288785867393017,
0.0323171503841877,
-0.03767640143632889,
0.02111482433974743,
-0.016659216955304146,
0.01339591946452856,
-0.04853000491857529,
-0.05039971321821213,
0.02614598348736763,
-0.024884710... | 0.141955 |
from checkpoints if interrupted, making them ideal for Spot's variable availability. \* \*\*Fine-tuning models\*\*: Use Spot instances for fine-tuning with robust checkpointing mechanisms to resume from the last saved state, minimizing the impact of instance interruptions. \* \*\*Batch inference\*\*: Use Spot instances... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.07104681432247162,
-0.03549603000283241,
-0.002536772284656763,
0.05294084921479225,
0.031047817319631577,
0.02488800324499607,
0.004454741254448891,
-0.030736509710550308,
-0.016873832792043686,
-0.005514198448508978,
-0.012844652868807316,
0.04048467054963112,
-0.0004690363130066544,
... | 0.219324 |
unused EC2 instance capacity for a specific instance type in a specific Availability Zone (AZ). When Karpenter tries to provision a new node, it selects an instance type that matches the NodePool's requirements. If no compatible instance type has Spot capacity in any AZ, then provisioning fails. To avoid this issue, al... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.028173187747597694,
-0.01740295998752117,
0.014667787589132786,
0.03895273804664612,
0.004498135764151812,
-0.025122372433543205,
-0.026755597442388535,
-0.051635388284921646,
0.009327600710093975,
-0.0017384581733494997,
-0.08438345044851303,
-0.08543507009744644,
0.026247307658195496,
... | 0.079917 |
longer than two minutes, the old node will be interrupted prior to those pods being rescheduled, which could impact workload availability. Consider the two-minute Spot interruption notice when designing your applications, implement checkpointing in long-running applications (e.g., saving progress to persistent storage ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.027866924181580544,
0.0023774660658091307,
0.08345265686511993,
0.0493335947394371,
0.06137154623866081,
-0.053510233759880066,
-0.10885340720415115,
-0.013342413119971752,
0.026286326348781586,
0.046926792711019516,
-0.05609205365180969,
0.07145144045352936,
-0.048523955047130585,
-0.07... | 0.137005 |
work completed within a specific time frame to understand impact of diversification. \*\*Scenario: Diversification for real time inference workloads\*\* For a real-time online inference workload on Spot Instances, you can configure a Karpenter NodePool to diversify across compatible GPU instance families and generation... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.025980167090892792,
-0.031301915645599365,
0.027798043563961983,
0.05069180577993393,
0.05985533818602562,
-0.01482310052961111,
-0.038758784532547,
-0.028482265770435333,
0.014397528022527695,
-0.025222696363925934,
-0.08513841032981873,
-0.0017819606000557542,
-0.012398197315633297,
0... | 0.129512 |
overhead. \* \*\*For Spot instances or hardware failures\*\*: In environments prone to interruptions, such as EC2 Spot (2-minute notice) or hardware failures (e.g., GPU memory errors), checkpointing enables quick resumption, making Spot viable for cost savings in fault-tolerant workloads. \* \*\*Distributed training at... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.03176553174853325,
-0.012552311643958092,
-0.00425328966230154,
0.03244549781084061,
0.06121579557657242,
-0.04744858294725418,
-0.052491188049316406,
0.05914456397294998,
0.04250744357705116,
-0.02530939131975174,
-0.04599941894412041,
0.02844509482383728,
0.037758078426122665,
-0.0649... | 0.205905 |
and Trainium instances, ODCRs can be used for a wider range of instance types, including G instances, making them suitable for workloads that require different GPU capabilities, such as inference or graphics. When using Amazon EC2 Spot Instances, being able to diverse across different instance types, sizes, and availab... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.02818339504301548,
-0.041382886469364166,
-0.022894224151968956,
0.06887461245059967,
0.09146315604448318,
-0.04537959024310112,
-0.09411121904850006,
-0.010229313746094704,
0.07408081740140915,
-0.03681673854589462,
-0.05422337353229523,
0.013347542844712734,
0.0440179742872715,
-0.046... | 0.069717 |
`karpenter.k8s.aws/instance-gpu-name: "a100"`) \* \*\*Time-Slicing\*\*: Schedules workloads to share a GPU's compute resources over time, allowing concurrent execution without physical partitioning. This is ideal for workloads with variable compute demands, but may lack memory isolation. \* \*\*Multi-Instance GPU (MIG)... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.08623020350933075,
0.0078575499355793,
-0.02678791992366314,
0.025826117023825645,
0.004147353116422892,
-0.06665708124637604,
-0.01661957986652851,
-0.015126493759453297,
0.04212125763297081,
-0.02429061569273472,
-0.048661988228559494,
-0.004526343662291765,
-0.02011525072157383,
-0.0... | 0.260406 |
and Trainium-based instances. It is tailored for AI/ML workloads, using labels (e.g., node-health-status) to manage node health. When a node is deemed unhealthy, HyperPod triggers automatic replacement of the faulty hardware, such as GPUs. It detects networking-related failures for EFA through its basic health checks b... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.025985540822148323,
0.004342255182564259,
0.0440220907330513,
0.08968062698841095,
0.08975186198949814,
0.01698719896376133,
-0.00606980687007308,
-0.016392597928643227,
-0.05905158817768097,
0.0636163204908371,
-0.0008221754105761647,
-0.008092123083770275,
-0.008199249394237995,
-0.022... | 0.232491 |
memory. We recommend using Kubernetes `PriorityClass` to assign priorities and `PodDisruptionBudget` to control eviction behavior. [,yaml] ---- apiVersion: scheduling.k8s.io/v1 kind: PriorityClass metadata: name: low-priority value: 100 --- spec: priorityClassName: low-priority ---- See the https://kubernetes.io/docs/c... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.0018200742779299617,
0.054322101175785065,
0.03567223623394966,
0.04225659370422363,
-0.02605137974023819,
-0.024124015122652054,
-0.053237538784742355,
-0.01618691347539425,
0.06413346529006958,
0.08927058428525925,
-0.06248117610812187,
-0.01757715828716755,
-0.024533914402127266,
-0.... | 0.151195 |
DRA transforms this model by introducing structured, declarative allocation that provides the Kubernetes scheduler with complete visibility into hardware characteristics and workload requirements. This enables intelligent placement decisions and efficient resource sharing. === Advantages of using DRA instead of NVIDIA ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.037783361971378326,
-0.005513170268386602,
-0.0011289609828963876,
0.03367985785007477,
-0.024798937141895294,
-0.029430368915200233,
-0.09863460808992386,
-0.02092638984322548,
0.040403541177511215,
-0.02130918949842453,
-0.09214537590742111,
-0.03104565478861332,
-0.04699435457587242,
... | 0.180971 |
about Kubernetes DRA and NVIDIA DRA drivers, see the following resources on GitHub: \* Kubernetes https://github.com/kubernetes/dynamic-resource-allocation[dynamic-resource-allocation] \* https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3063-dynamic-resource-allocation[Kubernetes enhancement proposa... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.03461870923638344,
0.032863784581422806,
-0.0012166360393166542,
0.03664488345384598,
-0.07885466516017914,
-0.021033933386206627,
-0.02206742763519287,
0.043079908937215805,
0.01717028021812439,
-0.014704763889312744,
-0.08071359246969223,
-0.00846337154507637,
-0.060571178793907166,
-... | 0.116135 |
A10G GPU and creates two `resourceslices` on that node. \* The `gpu.nvidia.com` slice registers the physical A10G GPU device with its specifications (memory, compute capability, and more). \* Since A10G doesn't support MIG partitioning, the `compute-domain.nvidia.com` slice creates a single compute domain representing ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.08846883475780487,
0.028471894562244415,
0.025215936824679375,
0.032713230699300766,
-0.035475969314575195,
-0.07315154373645782,
-0.042898666113615036,
0.005023630801588297,
0.061398424208164215,
-0.04011703282594681,
-0.041283018887043,
-0.03693036735057831,
-0.0500526987016201,
-0.00... | 0.169885 |
usage. For an example, see <>. \* \*Multi-Process service (MPS)\* enables concurrent execution of multiple CUDA processes on a single GPU with better isolation than time-slicing. For an example, see <>. \* \*Multi-Instance GPU (MIG)\* provides hardware-level partitioning, creating isolated GPU instances with dedicated ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.07419892400503159,
-0.010375040583312511,
-0.040671207010746,
0.01991329900920391,
0.030755838379263878,
-0.08252304792404175,
-0.011227025650441647,
0.027850637212395668,
0.03432530164718628,
-0.025982040911912918,
-0.062050603330135345,
0.05375015363097191,
-0.016220439225435257,
0.00... | 0.282453 |
GPU and reserved it for this Pod \* \*Pod status\*: Starts running immediately Second Pod (`training-pod-2`) \* \*State\*: `pending` \* \*Meaning\*: Waiting for DRA to configure time-slicing on the same GPU \* \*Pod status\*: Waiting to be scheduled \* The state will go from `pending` to `allocated,reserved` to `runnin... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.05117523670196533,
0.005256379023194313,
-0.02754843421280384,
0.01247705239802599,
-0.005254643503576517,
-0.048333823680877686,
-0.017116138711571693,
-0.009076807647943497,
-0.001090031466446817,
0.016307180747389793,
-0.008563409559428692,
-0.047639328986406326,
-0.0682998076081276,
... | 0.093671 |
driver allocates one `ResourceClaim` to the Pod and automatically configures MPS to allow both the inference and training containers to execute concurrently. Each container gets its own isolated GPU memory space and compute resources, with the MPS daemon coordinating access to the underlying hardware. You can verify th... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.010900568217039108,
0.0055719357915222645,
-0.026396332308650017,
0.05070408433675766,
0.038487304002046585,
-0.06748484075069427,
-0.044711221009492874,
-0.052339810878038406,
0.001447138492949307,
-0.04540187865495682,
-0.07262545078992844,
-0.03136453405022621,
-0.01306493952870369,
... | 0.078114 |
pre-installed, we disabled the deployment of drivers by the GPU Operator to avoid conflicts and leverage the optimized drivers already present on the instances. The NVIDIA DRA Driver handles dynamic resource allocation for MIG instances, while the GPU Operator manages the entire GPU lifecycle. This includes MIG configu... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.044238969683647156,
0.0161015372723341,
-0.010910206474363804,
0.09067805111408234,
0.006427033804357052,
-0.06144005432724953,
-0.011794131249189377,
-0.03899196907877922,
-0.06313782930374146,
-0.06320737302303314,
-0.03164132311940193,
-0.020400775596499443,
-0.03258153423666954,
0.0... | 0.085634 |
node-type: "p4de" vpc.amazonaws.com/efa.present: "true" accelerator: "nvidia" # Node taints taints: - key: nvidia.com/gpu value: "true" effect: NoSchedule # EFA support efaEnabled: true # Placement group for high-performance networking placementGroup: groupName: p4de-placement-group strategy: cluster # Capacity Block R... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.0450129434466362,
0.036646805703639984,
-0.06453903764486313,
0.05701713263988495,
0.03786672651767731,
0.04397238790988922,
-0.0581844188272953,
-0.04353974759578705,
-0.06479091942310333,
-0.027407575398683548,
-0.013376912102103233,
-0.07017859071493149,
0.02594493329524994,
0.0137453... | 0.027913 |
3g.40gb) and exposes them as schedulable resources through the `mig.nvidia.com` device class. The DRA driver continuously monitors the MIG topology and maintains an inventory of available instances across all GPUs. When a Pod requests a specific MIG profile through a `ResourceClaimTemplate`, the DRA driver intelligentl... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.05523597076535225,
-0.008109609596431255,
0.010264737531542778,
0.07598070055246353,
0.006635334342718124,
-0.08956244587898254,
-0.03549179434776306,
0.018263420090079308,
0.018384598195552826,
-0.045324116945266724,
-0.06348448991775513,
-0.009756534360349178,
-0.02908727526664734,
-0... | 0.126174 |
in range(100): # Medium batch for 2g.20gb x = torch.randn(128, 1024).cuda() y = torch.randint(0, 10, (128,)).cuda() optimizer.zero\_grad() output = model(x) loss = criterion(output, y) loss.backward() optimizer.step() if epoch % 10 == 0: print(f"Medium Training - Epoch {epoch}, Loss: {loss.item():.4f}, GPU Memory: {tor... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.007738061714917421,
-0.044568855315446854,
-0.045727089047431946,
0.08936263620853424,
0.07299208641052246,
-0.030484618619084358,
-0.017721984535455704,
0.056310832500457764,
-0.04183709993958473,
-0.0654696598649025,
-0.005570892244577408,
-0.02533443458378315,
-0.08562111854553223,
-0... | 0.074936 |
NAME STATE AGE mig-large-training-pod-mig-large-claim-6dpn8 pending 0s mig-large-training-pod-mig-large-claim-6dpn8 pending 0s mig-large-training-pod-mig-large-claim-6dpn8 allocated,reserved 0s mig-medium-training-pod-mig-medium-claim-bk596 pending 0s mig-medium-training-pod-mig-medium-claim-bk596 pending 0s mig-medium... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.02406974509358406,
-0.008408136665821075,
-0.0372655875980854,
0.05306398868560791,
0.07136085629463196,
-0.0505734384059906,
0.0010571947786957026,
0.003201066982001066,
0.02253994718194008,
-0.0005681682378053665,
0.06281191855669022,
-0.03453409671783447,
-0.0317101776599884,
-0.0033... | 0.144264 |
| 71MiB / 19968MiB | 28 0 | 2 0 1 0 0 | | | 0MiB / 16383MiB | | | +------------------+----------------------------------+-----------+-----------------------+ | 1 13 0 2 | 161MiB / 9728MiB | 14 0 | 1 0 0 0 0 | | | 2MiB / 8191MiB | | | +------------------+----------------------------------+-----------+-------------------... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
-0.02175680547952652,
0.036623042076826096,
-0.12834949791431427,
0.004336299374699593,
-0.09564635902643204,
-0.04696858674287796,
-0.06538671255111694,
0.050162963569164276,
-0.06158487871289253,
-0.06705635786056519,
0.0029503507539629936,
-0.13024936616420746,
0.02649683505296707,
-0.0... | 0.069501 |
in imex\_vars: print(f' {var}={os.environ[var]}') print('IMEX channel verification completed') " # Keep container running for inspection sleep 3600 resources: claims: - name: imex-channel-0 - name: imex-channel-1 resourceClaims: - name: imex-channel-0 resourceClaimTemplateName: imex-channel-template - name: imex-channe... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_compute.adoc | mainline | aws-eks-best-practices | [
0.00911747757345438,
0.041527364403009415,
0.039319541305303574,
0.015022609382867813,
0.04842362925410271,
-0.05128750950098038,
0.07035347074270248,
0.005472966469824314,
0.06352655589580536,
0.015202627517282963,
0.018893133848905563,
-0.07383061945438385,
0.03419464826583862,
0.0500804... | 0.238244 |
//!!NODE\_ROOT [[aiml,aiml.title]] = AI/ML on EKS - Introduction :info\_doctype: chapter :info\_title: Best Practices for Running AI/ML Workloads :info\_abstract: Best Practices for running AI/ML workloads on EKS :info\_titleabbrev: AI/ML :imagesdir: images/ :authors: ["Leah Tucker"] :date: 2025-05-30 TIP: https://aws-... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_index.adoc | mainline | aws-eks-best-practices | [
-0.0636771097779274,
0.0295190941542387,
0.01563866250216961,
0.07191373407840729,
0.029004212468862534,
-0.05407525971531868,
-0.019878311082720757,
-0.013924778439104557,
0.032253462821245193,
0.06692726910114288,
-0.02699732594192028,
-0.0010917974868789315,
0.023464486002922058,
-0.054... | 0.236118 |
//!!NODE\_ROOT [."topic"] [[aiml-observability,aiml-observability.title]] = AI/ML on EKS - Observability :info\_doctype: section :imagesdir: images/ :info\_title: Observability :info\_abstract: Observability :info\_titleabbrev: Observability :authors: ["Leah Tucker", "Omri Shiv"] :date: 2025-11-19 TIP: https://aws-expe... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.011091131716966629,
0.02382383868098259,
-0.043305087834596634,
0.07433953881263733,
0.0622507706284523,
-0.06996047496795654,
-0.016396645456552505,
-0.03503766655921936,
0.03740520030260086,
0.011497837491333485,
-0.04801793396472931,
-0.02965371310710907,
0.038010839372873306,
-0.012... | 0.165082 |
infrastructure and observability stack. They collect, store, and visualize metrics. AI/ML engineers define model-specific metrics and monitor performance under varying load and data distribution. Application developers consume APIs, route requests, and track service-level metrics and user interactions. Without unified ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.00315488176420331,
-0.005398856010288,
-0.04885506629943848,
0.09112649410963058,
0.055673833936452866,
-0.07941491156816483,
-0.054161787033081055,
-0.013511892408132553,
0.005479858256876469,
0.014224736019968987,
-0.08073294162750244,
-0.05742042139172554,
0.016172461211681366,
-0.04... | 0.229628 |
and Grafana\*\* If your organization needs customized dashboards and advanced visualization capabilities, deploy Prometheus with the https://catalog.ngc.nvidia.com/orgs/nvidia/teams/k8s/containers/dcgm-exporter[NVIDIA DCGM-Exporter] and Grafana for Kubernetes-native monitoring. Prometheus scrapes and stores GPU metrics... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.041887424886226654,
-0.001028995611704886,
-0.05580651015043259,
0.026707885786890984,
0.061622172594070435,
-0.05922464281320572,
-0.050354160368442535,
-0.01985379494726658,
0.023351822048425674,
0.040270060300827026,
-0.09591591358184814,
-0.10175959765911102,
-0.012605015188455582,
... | 0.186603 |
model performs on validation data. Calculate the F1-score on a validation set after each training epoch to assess whether the model is improving and when it reaches acceptable performance levels. \* \*\*Business-Specific Metrics and KPIs\*\* — Define and track metrics that directly measure the business value of your AI... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
0.0002674581774044782,
-0.07817057520151138,
-0.07267764210700989,
0.027963031083345413,
0.042808640748262405,
0.04258247837424278,
-0.07467687129974365,
0.06610921770334244,
-0.037615224719047546,
-0.09029965847730637,
-0.05870575085282326,
-0.007967012003064156,
0.022579945623874664,
-0.... | 0.228222 |
loading consumes more than 20% of total training time, consider optimizing your data pipeline with caching, prefetching, or faster storage. \*\*Error Rates and Failures\*\* Monitor error rates and failures throughout your training pipeline to maintain reliability and prevent wasted compute resources. Undetected errors ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.030251724645495415,
-0.04177297651767731,
0.023271281272172928,
0.06656958907842636,
-0.027780765667557716,
-0.1083393394947052,
-0.07158578932285309,
0.0365971177816391,
-0.08942040801048279,
-0.06552697718143463,
-0.09316667169332504,
-0.02016424387693405,
-0.04070376604795456,
-0.058... | 0.071765 |
about errors, state changes, and system events that help you understand why training jobs fail or perform poorly. Correlating logs with metrics allows you to pinpoint root causes faster. \* \*\*Application Logs\*\* - Collect application logs from your training jobs, data pipelines, and ML frameworks to identify bottlen... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
0.05621665343642235,
-0.04121352359652519,
0.02614957094192505,
0.05771869421005249,
0.06876594573259354,
-0.060282476246356964,
-0.018359022215008736,
0.034591544419527054,
-0.019128818064928055,
-0.0052857669070363045,
-0.08343576639890671,
-0.037588827311992645,
-0.05461916700005531,
0.... | 0.168224 |
text. \* \*\*Error Rate \*\* — Tracks failed requests, which can indicate performance issues. For example, monitor failed requests for large documents or certain characters. \* \*\*Throughput\*\* — Measure the number of requests or operations the system can handle per unit of time. For example, track requests per secon... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.06332705169916153,
-0.034154124557971954,
-0.005922035314142704,
0.06089314445853233,
-0.019937237724661827,
-0.035783786326646805,
-0.006921316962689161,
0.017160318791866302,
0.07692350447177887,
-0.021879760548472404,
-0.06866973638534546,
-0.039571866393089294,
-0.022776594385504723,
... | 0.14205 |
memory usage gpu\_index, memory\_used = get\_gpu\_memory\_usage() ---- [#track-inference-request-duration-for-real-time-online-inference] === Track Inference Request Duration for Real-Time Online Inference As discussed in the <> topic, low latency is critical for providing timely responses to users or other dependent s... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
0.022471792995929718,
-0.007444389164447784,
-0.05845227837562561,
0.05690602585673332,
0.0443381629884243,
-0.01742737926542759,
0.010550450533628464,
-0.00018935956177301705,
0.02954864874482155,
0.014522614888846874,
-0.022403152659535408,
-0.07934993505477905,
-0.02312559448182583,
-0.... | 0.079185 |
tokens token\_duration.observe(time.time() - start\_time) ---- In Grafana, use the query `histogram\_quantile(0.95, sum(rate(token\_processing\_duration\_seconds\_bucket[5m])) by (le, pod))`` to visualize P95 processing time trends. To learn more, see https://github.com/prometheus/client\_python[Prometheus Histogram Do... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/aiml/aiml_observability.adoc | mainline | aws-eks-best-practices | [
-0.051469799131155014,
-0.0017693188274279237,
-0.020054513588547707,
0.004382262006402016,
-0.04159867763519287,
-0.12299943715333939,
-0.02070576325058937,
0.0064698196947574615,
-0.006992244627326727,
0.0014918383676558733,
-0.018750742077827454,
-0.06508169323205948,
0.003528870409354567... | 0.18031 |
//!!NODE\_ROOT [."topic"] [[identity-and-access-management,identity-and-access-management.title]] = Identity and Access Management :info\_doctype: section :info\_title: Identity and Access Management :info\_abstract: Identity and Access Management :info\_titleabbrev: Identity and Access Management :imagesdir: images/ i... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.061816588044166565,
0.10411572456359863,
-0.0416085384786129,
0.06550600379705429,
0.07169385999441147,
-0.0214709360152483,
0.11553937941789627,
-0.028560958802700043,
0.0804072842001915,
0.027158882468938828,
0.04743998125195503,
0.0006185232778079808,
0.12159277498722076,
-0.03907455... | 0.203203 |
=== CloudWatch query to help users identify clients sending requests to global STS endpoint Run CloudWatch query below to get sts endpoint. If stsendpoint equals to "sts.amazonaws.com", then it is a global STS endpoint. If stsendpoint equals like "sts..amazonaws.com", then it is a regional STS endpoint. ---- fields @ti... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
0.0014685577480122447,
0.005472538992762566,
-0.021914919838309288,
0.04796288162469864,
-0.010135217569768429,
-0.00923833902925253,
0.07516807317733765,
-0.09514778852462769,
0.07989075779914856,
0.037711650133132935,
-0.022037973627448082,
-0.051903001964092255,
0.028228675946593285,
0.... | 0.200629 |
|=== |EKS Access Policy |Kubernetes RBAC |AmazonEKSClusterAdminPolicy |cluster-admin |AmazonEKSAdminPolicy |admin |AmazonEKSEditPolicy |edit |AmazonEKSViewPolicy |view |=== [source,bash] ---- $ aws eks list-access-policies { "accessPolicies": [ { "name": "AmazonEKSAdminPolicy", "arn": "arn:aws:eks::aws:cluster-access-p... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
0.007843175902962685,
0.06537890434265137,
-0.06305967271327972,
0.017702532932162285,
0.00460333377122879,
0.006225919816643,
0.06474486738443375,
-0.07907426357269287,
0.05939756706357002,
0.058315496891736984,
-0.005818139296025038,
-0.05791883170604706,
0.02192023955285549,
-0.05395740... | 0.126855 |
way to manage permissions through AWS-native tooling. == Cluster Access Recommendations === Combine IAM Identity Center with CAM API \* \*Simplified management\*: By using the Cluster Access Management API in conjunction with IAM Identity Center, administrators can manage EKS cluster access alongside other AWS services... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
0.014744581654667854,
0.009956538677215576,
-0.022816127166152,
0.004418770782649517,
-0.03542877361178398,
0.020162567496299744,
0.0847785472869873,
-0.01459576841443777,
0.05017448216676712,
0.11795871704816818,
-0.023565217852592468,
-0.11917803436517715,
0.04762021824717522,
0.01252933... | 0.17935 |
the cluster creator principal By default Amazon EKS clusters are created with a permanent `cluster-admin` permission bound to the cluster creator principal. With the Cluster Access Manager API, it's possible to create clusters without this permission setting the `--access-config bootstrapClusterCreatorAdminPermissions`... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.02515031024813652,
0.06692052632570267,
-0.04102490469813347,
0.062434688210487366,
0.003569397609680891,
-0.02014636993408203,
0.017688404768705368,
-0.08120480179786682,
0.04920722544193268,
0.07398483157157898,
0.027288325130939484,
-0.036599546670913696,
0.08234432339668274,
-0.0567... | 0.084085 |
that creates the cluster, is automatically granted `system:masters` permissions in the cluster's RBAC configuration. Even being a best practice to remove this permission, as described xref:iam-cluster-creator[here] if using the `CONFIG\_MAP` authentication method, relying on `aws-auth` ConfigMap, this access cannot be ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
0.019350310787558556,
-0.02239886298775673,
-0.0894104391336441,
0.03224627673625946,
0.013228273019194603,
-0.010396325960755348,
0.035699512809515,
-0.030061565339565277,
-0.0020747941453009844,
0.06458494812250137,
0.0004951863083988428,
-0.07431060075759888,
0.07895040512084961,
-0.009... | 0.191182 |
project includes a CLI for updating the ConfigMap. https://github.com/kubernetes-sigs/aws-iam-authenticator/releases[Download a release] on GitHub. Add cluster permissions to an IAM Role: [source,bash] ---- $ ./aws-iam-authenticator add role --rolearn arn:aws:iam::185309785115:role/lil-dev-role-cluster --username lil-d... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.05491406470537186,
0.030030133202672005,
0.00032725027995184064,
0.03168768808245659,
0.006910417694598436,
-0.04031800106167793,
0.08243804425001144,
-0.031428687274456024,
0.05551565811038017,
0.05924251675605774,
0.020863190293312073,
-0.09218385815620422,
0.059172939509153366,
-0.03... | 0.164971 |
running within a Pod calls the Kubernetes APIs, the Pod needs to be assigned a service account that explicitly grants it permission to call those APIs. Similar to guidelines for user access, the Role or ClusterRole bound to a service account should be restricted to the API resources and methods that the application nee... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.030230343341827393,
-0.040631361305713654,
-0.009612971916794777,
0.006397110875695944,
-0.04857023432850838,
-0.0054964348673820496,
0.05254443362355232,
0.010830401442945004,
0.08906691521406174,
0.04651743546128273,
-0.03474948927760124,
-0.03511744737625122,
0.01886017620563507,
0.0... | 0.165171 |
AWS SDKs are responsible for reloading the token when it rotates. For further information about IRSA, see https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-technical-overview.html. === EKS Pod Identities https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html[EKS Pod Identitie... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.018800396472215652,
0.0034098904579877853,
-0.013073558919131756,
0.04132583737373352,
0.012239692732691765,
0.012616796419024467,
0.07381752133369446,
-0.012931017205119133,
0.1384328454732895,
0.03456881269812584,
0.005461257416754961,
0.011311609297990799,
0.02624545805156231,
-0.059... | 0.177826 |
Identities |eks-cluster-arn |The ARN of the EKS cluster, e.g. `arn:${Partition}:eks:${Region}:${Account}:cluster/${ClusterName}`. The cluster ARN is unique, but if a cluster is deleted and recreated in the same region with the same name, within the same AWS account, it will have the same ARN. |eks-cluster-name |The nam... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.04629627242684364,
0.02342279627919197,
-0.024201001971960068,
0.05154472589492798,
0.017100023105740547,
0.02779494598507881,
0.1302020251750946,
-0.12562449276447296,
0.1432199478149414,
0.017056887969374657,
0.0058438582345843315,
-0.0884341448545456,
0.04995249584317207,
-0.01780793... | 0.169191 |
pod \_can still inherit the rights of the instance profile assigned to the worker node\_. For pods that do not need these permissions, you can block access to the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html[instance metadata] to help ensure that your applications only ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
0.0033758338540792465,
0.0630498081445694,
0.021574977785348892,
0.0032092570327222347,
0.028183024376630783,
-0.0423545204102993,
0.013023264706134796,
0.0020895919296890497,
0.051253993064165115,
0.03720835968852043,
-0.03484676405787468,
-0.023187361657619476,
-0.004761008080095053,
-0.... | 0.113988 |
scale, as ABAC allows you to operate with fewer IAM roles. === When your application needs access to IMDS, use IMDSv2 and increase the hop limit on EC2 instances to 2 https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html[IMDSv2] requires you use a PUT request to get a session to... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.04336894303560257,
0.008663656190037727,
0.037953369319438934,
-0.006974353920668364,
-0.040770817548036575,
-0.03389720246195793,
-0.0016189574962481856,
0.050908543169498444,
0.0809619128704071,
0.06555503606796265,
-0.009678009897470474,
-0.046886805444955826,
0.04374973475933075,
-0... | 0.127717 |
account token without adding them to the Nobody group. === Grant least privileged access to applications https://github.com/princespaghetti/actionhero[Action Hero] is a utility that you can run alongside your application to identify the AWS API calls and corresponding IAM permissions your application needs to function ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.0001670697529334575,
0.030779851600527763,
-0.07471215724945068,
0.0004580776731017977,
0.00936504639685154,
-0.0016564978286623955,
0.040434688329696655,
-0.00923969317227602,
0.044298768043518066,
0.06780263781547546,
-0.013583309948444366,
-0.04599624127149582,
0.06706477701663971,
-... | 0.06285 |
shown below: [source,yaml] ---- # Please edit the object below. Lines beginning with a '#' will be ignored, # and an empty file will abort the edit. If an error occurs while saving this file will be # reopened with the relevant failures. # apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: anno... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.03368471935391426,
-0.005905505269765854,
-0.016618533059954643,
0.07159136980772018,
0.033248577266931534,
0.03628335893154144,
-0.015069378539919853,
-0.04036845266819,
0.08075197041034698,
0.11432124674320221,
-0.005364499986171722,
-0.03307785093784332,
0.011465797200798988,
-0.0353... | 0.178911 |
\* https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/patterns/sso-iam-identity-center[Terraform EKS Blueprints Pattern - IAM Identity Center Single Sign-On for Amazon EKS Cluster] \* https://github.com/aws-ia/terraform-aws-eks-blueprints/tree/main/patterns/sso-okta[Terraform EKS Blueprints Pattern - Okta... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/iam.adoc | mainline | aws-eks-best-practices | [
-0.10036399215459824,
-0.0028546226676553488,
-0.06143800914287567,
0.016922758892178535,
0.05174410715699196,
0.007337702438235283,
0.002653357107192278,
-0.05224819853901863,
-0.0036958614364266396,
0.07835932075977325,
0.04143010452389717,
-0.04498037323355675,
0.03979307785630226,
-0.0... | 0.277091 |
//!!NODE\_ROOT [."topic"] [[runtime-security,runtime-security.title]] = Runtime security :info\_doctype: section :info\_title: Runtime security :info\_abstract: Runtime security :info\_titleabbrev: Runtime security :imagesdir: images/ Runtime security provides active protection for your containers while they're running... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/runtime.adoc | mainline | aws-eks-best-practices | [
0.04949455335736275,
0.05743543803691864,
0.0322253480553627,
-0.03392792120575905,
0.1543276309967041,
-0.04995735362172127,
0.046897515654563904,
0.013597343116998672,
0.05450230464339256,
-0.01235694345086813,
-0.00297709577716887,
-0.023907281458377838,
0.036762550473213196,
-0.0011415... | 0.166309 |
Pods and containers. === AppArmor and SELinux AppArmor and SELinux are known as https://en.wikipedia.org/wiki/Mandatory\_access\_control[mandatory access control or MAC systems]. They are similar in concept to seccomp but with different APIs and abilities, allowing access control for e.g. specific filesystem paths or n... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/runtime.adoc | mainline | aws-eks-best-practices | [
0.026822993531823158,
0.014013231731951237,
0.004555239342153072,
-0.05644867569208145,
0.055711276829242706,
-0.030210912227630615,
0.0324278399348259,
0.09091150015592575,
0.01763056591153145,
-0.03220879286527634,
0.012886629439890385,
-0.02244173362851143,
0.0068085393868386745,
-0.026... | 0.216922 |
syscall, or deeper in the kernel in areas that might be reachable through multiple different syscalls (such as writing to a specific privileged file). Seccomp, on the other hand, is a syscall filter which is applied to all syscalls before they are run. A process can set up a filter which allows them to revoke their rig... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/runtime.adoc | mainline | aws-eks-best-practices | [
0.04405318945646286,
0.03504254296422005,
0.009445047937333584,
-0.018074670806527138,
0.02455328218638897,
-0.03847484663128853,
0.0562925711274147,
0.024755630642175674,
0.05693783983588219,
0.05202361196279526,
0.006056457292288542,
-0.03391597792506218,
-0.015781624242663383,
-0.016334... | 0.194591 |
//!!NODE\_ROOT [."topic"] [[autosecure,autosecure.title]] = EKS Auto Mode - Security :info\_doctype: section :info\_title: EKS Auto Mode - Security :info\_abstract: EKS Auto Mode - Security :info\_titleabbrev: EKS Auto Mode - Security :imagesdir: images/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/automode.adoc | mainline | aws-eks-best-practices | [
-0.03994802385568619,
0.09094516932964325,
-0.012977397069334984,
0.01444431021809578,
0.07204674929380417,
0.01917210780084133,
0.056745294481515884,
0.022691240534186363,
0.040591370314359665,
0.08177997916936874,
0.048767272382974625,
-0.04799534007906914,
0.07730964571237564,
-0.012732... | 0.232705 |
compared to IRSA \* Enhanced security through session tagging and ABAC support [source,bash] ---- aws eks create-pod-identity-association \ --cluster-name ${EKS\_CLUSTER\_NAME} \ --role-arn arn:aws:iam::${AWS\_ACCOUNT\_ID}:role/${IAM\_ROLE\_NAME} \ --namespace ${NAMESPACE} \ --service-account ${SERVICE\_ACCOUNT\_NAME} ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/automode.adoc | mainline | aws-eks-best-practices | [
-0.04324007406830788,
0.07129990309476852,
-0.054994285106658936,
0.03237074241042137,
0.026660583913326263,
0.006548939738422632,
0.10750368982553482,
-0.0034305036533623934,
0.04596259072422981,
0.09290628880262375,
0.0007129196310415864,
-0.07007855921983719,
0.03654581308364868,
0.0125... | 0.211375 |
and decryption handled seamlessly by the service ==== EBS Volumes \* Root and data EBS volumes are always encrypted \* Volumes are configured to be deleted upon termination of the instance \* There is an option to specify custom KMS keys for encryption ==== EFS Integration \* Support for encryption in transit with EFS ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/automode.adoc | mainline | aws-eks-best-practices | [
0.0011834247270599008,
0.04012071341276169,
0.01587892323732376,
0.03943350166082382,
0.050667621195316315,
-0.03858475014567375,
0.06930045783519745,
-0.046899329870939255,
0.09121393412351608,
0.09271447360515594,
-0.005018732510507107,
-0.04252537339925766,
0.034559376537799835,
-0.0103... | 0.139775 |
supported in EKS Auto Mode clusters, providing enhanced security visibility without additional configuration at the node level. ==== ===== GuardDuty Findings Integration GuardDuty findings can be integrated with other AWS services for automated response: \* \*EventBridge Rules\*: [source,json] ---- { "source": ["aws.gu... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/automode.adoc | mainline | aws-eks-best-practices | [
-0.017040446400642395,
0.08621767163276672,
-0.005413530860096216,
0.04213254526257515,
0.07419261336326599,
-0.007981762290000916,
0.04499799758195877,
-0.06063677370548248,
0.025508234277367592,
0.0674283429980278,
-0.01712678000330925,
-0.11288706958293915,
0.07271811366081238,
0.023176... | 0.139084 |
through `NodePools` and `NodeClasses` resources. [NOTE] ==== While EKS Auto Mode may require adjustments to your security tooling deployment strategy, these changes often result in more maintainable and secure configurations aligned with cloud-native best practices. EKS Auto Mode expects to completely take over most of... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/automode.adoc | mainline | aws-eks-best-practices | [
-0.04319441691040993,
0.060559261590242386,
0.04462753236293793,
0.0486084446310997,
0.020360976457595825,
0.011875788681209087,
-0.0012626373209059238,
-0.00416326429694891,
0.026782387867569923,
0.08031657338142395,
0.02612590603530407,
-0.02475617825984955,
0.050757065415382385,
-0.0213... | 0.113426 |
//!!NODE\_ROOT [."topic"] [[cluster-access-management,cluster-access-management.title]] = Cluster access management :info\_doctype: section :info\_title: Cluster access management :info\_abstract: Cluster access management :info\_titleabbrev: Cluster access management :imagesdir: images/ Effective access management is ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/cam.adoc | mainline | aws-eks-best-practices | [
-0.009912095032632351,
0.04345289245247841,
-0.06667707115411758,
0.055370256304740906,
0.06191813945770264,
-0.008826936595141888,
0.04778045415878296,
-0.00006452063098549843,
0.0598495677113533,
0.10825080424547195,
-0.0028812859673053026,
-0.030601972714066505,
0.09680945426225662,
-0.... | 0.241141 |
level. Additional configuration is required for custom Kubernetes RBAC roles. Along with Kubernetes-native RBAC, consider using Kyverno for advanced permissions management in EKS clusters. == Option 2: AWS IAM Users/Roles mapped to Kubernetes groups === Pros: . Fine-grained control over IAM permissions. . Predictable a... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/cam.adoc | mainline | aws-eks-best-practices | [
-0.0066886176355183125,
-0.0032900082878768444,
-0.004878005478531122,
0.03568928688764572,
-0.04934508353471756,
0.0218333899974823,
0.0684085488319397,
-0.012488999404013157,
0.04863845929503441,
0.04534059390425682,
-0.016010936349630356,
-0.05278920754790306,
0.052033912390470505,
0.00... | 0.184209 |
//!!NODE\_ROOT [."topic"] [[pod-security,pod-security.title]] = Pod Security :info\_doctype: section :info\_title: Pod Security :info\_abstract: Pod Security :info\_titleabbrev: Pod Security :imagesdir: images/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.02775392308831215,
0.03421974182128906,
0.01699921116232872,
-0.022742578759789467,
0.06842020153999329,
-0.05490447208285332,
0.029478400945663452,
0.03767212852835655,
0.058365486562252045,
0.04580152779817581,
-0.02092721499502659,
0.009598813951015472,
0.036184538155794144,
-0.036141... | 0.194069 |
Kubernetes https://kubernetes.io/docs/concepts/security/pod-security-standards/[Pod Security Standards (PSS)] Both the PAC and PSS solutions can coexist with PSP; they can be used in clusters before PSP is removed. This eases adoption when migrating from PSP. Please see this https://kubernetes.io/docs/tasks/configure-p... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.0114362807944417,
0.00022187986178323627,
0.018954535946249962,
-0.019823167473077774,
0.08202069997787476,
0.06566507369279861,
-0.007805580273270607,
0.010491604916751385,
0.007287702057510614,
0.0840832069516182,
-0.0008579628192819655,
0.024917734786868095,
0.0021963000763207674,
-0.... | 0.139956 |
rejected. \* \*audit:\* Policy violations will trigger the addition of an audit annotation to the event recorded in the audit log, but are otherwise allowed. \* \*warn:\* Policy violations will trigger a user-facing warning, but are otherwise allowed. These modes and the profile (restriction) levels are configured at t... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.012889759615063667,
0.0675983875989914,
0.06144028529524803,
0.00980639923363924,
0.08484666049480438,
0.006766475737094879,
0.09272797405719757,
-0.059900831431150436,
0.058864887803792953,
0.062014032155275345,
0.04213316738605499,
-0.0832335501909256,
0.05428602173924446,
-0.000145565... | 0.165727 |
profiles. ==== Existing Pods If a namespace with existing pods is modified to use a more restrictive PSS profile, the \_audit\_ and \_warn\_ modes will produce appropriate messages; however, \_enforce\_ mode will not delete the pods. The warning messages are seen below. [source,bash] ---- Warning: existing pods in name... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.013373345136642456,
0.016204673796892166,
0.015788609161973,
0.057759493589401245,
0.08799747377634048,
-0.029693713411688805,
0.09300519526004791,
-0.02741890214383602,
-0.00660727359354496,
0.02796785905957222,
0.047998808324337006,
-0.07072336971759796,
0.04819054901599884,
0.01272866... | 0.144358 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.