content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
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 |
(solution dependent) \* Supports mutating API server requests before validation (solution dependent) \* Can generate complementary policies and Kubernetes resources (solution dependent - From pod policies, Kyverno can https://kyverno.io/docs/writing-policies/autogen/[auto-gen] policies for higher-level controllers, suc... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
-0.10397898405790329,
-0.002092310693114996,
0.033262621611356735,
-0.08180782943964005,
0.007680199109017849,
-0.01998487487435341,
0.014781891368329525,
0.02046160399913788,
0.04744230955839157,
0.06364637613296509,
0.02400454692542553,
-0.05315366014838219,
0.015930956229567528,
-0.0055... | 0.287473 |
containers of a pod are run on infrastructure that AWS manages. With Fargate, you cannot run a privileged container or configure your pod to use hostNetwork or hostPort. ==== === Do not run processes in containers as root All containers run as root by default. This could be problematic if an attacker is able to exploit... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.0725148543715477,
0.04776764661073685,
-0.006352570373564959,
-0.018363112583756447,
0.01871715858578682,
-0.03272019326686859,
-0.021119719371199608,
0.046084653586149216,
0.04440165311098099,
0.05187162011861801,
-0.07770612835884094,
-0.019257578998804092,
0.014559680595993996,
-0.038... | 0.056249 |
requests and limits will help minimize resource contention and mitigate the risk from poorly written applications that consume an excessive amount of resources. The `podSpec` allows you to specify requests and limits for CPU and memory. CPU is considered a compressible resource because it can be oversubscribed. Memory ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
-0.0036071324720978737,
0.05029667168855667,
0.025488508865237236,
0.04054388776421547,
-0.02040169946849346,
-0.003959029447287321,
0.03694731742143631,
0.0052718897350132465,
0.07546025514602661,
0.034335777163505554,
-0.06969980150461197,
0.02838553488254547,
-0.017255432903766632,
-0.0... | 0.199351 |
it forces you to specify requests and limits for all containers deployed into that namespace. By contrast, limit ranges give you more granular control of the allocation of resources. With limit ranges you can min/max for CPU and memory resources per pod or per container within a namespace. You can also use them to set ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
-0.040903788059949875,
0.05017228052020073,
-0.0291284266859293,
-0.03153170272707939,
0.003506226697936654,
-0.05370519310235977,
-0.0027039917185902596,
0.03738199919462204,
0.04621104151010513,
0.00471104821190238,
-0.036377787590026855,
0.020752111449837685,
0.04654959589242935,
-0.017... | 0.203129 |
the file system, consider writing to a temporary directory or attach and mount a volume. You can enforce this by setting the pod's SecurityContext as follows: [source,yaml] ---- ... securityContext: readOnlyRootFilesystem: true ... ---- Policy-as-code and Pod Security Standards can be used to enforce this behavior. [IN... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/pods.adoc | mainline | aws-eks-best-practices | [
0.04079253971576691,
0.04111955314874649,
-0.013956092298030853,
0.039802223443984985,
0.01334486622363329,
-0.02023203670978546,
0.0051924074068665504,
0.03223535418510437,
0.11111342906951904,
0.09254400432109833,
-0.003747217822819948,
-0.02477863058447838,
-0.011004259809851646,
0.0040... | 0.107871 |
//!!NODE\_ROOT [."topic"] [[incident-response-and-forensics,incident-response-and-forensics.title]] = Incident response and forensics :info\_doctype: section :info\_title: Incident response and forensics :info\_abstract: Incident response and forensics :info\_titleabbrev: Incident response and forensics :imagesdir: ima... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/incidents.adoc | mainline | aws-eks-best-practices | [
0.0018929133657366037,
0.0799734890460968,
0.06509990990161896,
0.016500167548656464,
0.19712015986442566,
-0.0728546604514122,
0.01695866696536541,
0.05831301212310791,
0.024781981483101845,
0.05743449181318283,
0.029038703069090843,
-0.022462913766503334,
0.035209715366363525,
0.02342674... | 0.193188 |
[source,yaml] ---- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny spec: podSelector: matchLabels: app: web policyTypes: - Ingress - Egress ---- [IMPORTANT] ==== A Network Policy may prove ineffective if an attacker has gained access to underlying host. If you suspect that has happened... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/incidents.adoc | mainline | aws-eks-best-practices | [
-0.013255119323730469,
0.09239917993545532,
0.012758037075400352,
0.04028831422328949,
0.11074699461460114,
-0.003753428580239415,
0.02678738348186016,
-0.08264646679162979,
0.04485625773668289,
0.08929134160280228,
-0.014862802810966969,
-0.043870531022548676,
0.038702625781297684,
-0.027... | 0.104079 |
compromised pod or workload resource. First roll out the fix for the vulnerability that was compromised and start new replacement pods. Then delete the vulnerable pods. If the vulnerable pods are managed by a higher-level Kubernetes workload resource (for example, a Deployment or DaemonSet), deleting them will schedule... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/incidents.adoc | mainline | aws-eks-best-practices | [
0.02648107148706913,
0.043852876871824265,
0.06881933659315109,
0.025391383096575737,
0.05436524376273155,
0.0035422646906226873,
-0.009806113317608833,
-0.034881070256233215,
0.09294312447309494,
0.04580621048808098,
-0.018047962337732315,
-0.005867208819836378,
0.041297413408756256,
0.00... | 0.111529 |
//!!NODE\_ROOT [."topic"] [[auditing-and-logging,auditing-and-logging.title]] = Auditing and logging :info\_doctype: section :info\_title: Auditing and logging :info\_abstract: Auditing and logging :info\_titleabbrev: Detective Controls :imagesdir: images/ TIP: https://aws-experience.com/emea/smb/events/series/get-hand... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/detective.adoc | mainline | aws-eks-best-practices | [
-0.02833748608827591,
0.06933245062828064,
0.0252909567207098,
0.02518356591463089,
0.10859532654285431,
-0.043323930352926254,
0.06070426478981972,
-0.06715548783540726,
0.10645387321710587,
0.09529339522123337,
0.010465338826179504,
-0.03075064718723297,
0.046354442834854126,
-0.00342750... | 0.136666 |
- group: "authentication.k8s.io" - group: "authorization.k8s.io" - group: "autoscaling" - group: "batch" - group: "certificates.k8s.io" - group: "extensions" - group: "metrics.k8s.io" - group: "networking.k8s.io" - group: "policy" - group: "rbac.authorization.k8s.io" - group: "scheduling.k8s.io" - group: "settings.k8s.... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/detective.adoc | mainline | aws-eks-best-practices | [
-0.06626009196043015,
0.028583582490682602,
-0.055186957120895386,
0.04825674369931221,
0.0036763225216418505,
-0.039611268788576126,
0.05863269791007042,
-0.035760484635829926,
-0.003169215749949217,
0.06661071628332138,
-0.030309153720736504,
-0.08614275604486465,
0.019573494791984558,
0... | 0.141854 |
"delete"] ---- Lists create, update, delete operations to ClusterRoles: [source,bash] ---- fields @timestamp, @message | sort @timestamp desc | limit 100 | filter objectRef.resource="clusterroles" and verb in ["create", "update", "patch", "delete"] ---- Lists create, update, delete operations to ClusterRoleBindings: [s... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/detective.adoc | mainline | aws-eks-best-practices | [
-0.014226174913346767,
0.005945309996604919,
-0.0939304530620575,
0.03344472125172615,
0.011217886582016945,
-0.053149282932281494,
0.1067163273692131,
-0.02937442809343338,
-0.017709478735923767,
0.08767803013324738,
0.03816234692931175,
-0.04645166173577309,
0.10675083845853806,
-0.03707... | 0.156641 |
//!!NODE\_ROOT [."topic"] [[data-encryption-and-secrets-management,data-encryption-and-secrets-management.title]] = Data encryption and secrets management :info\_doctype: section :info\_title: Data encryption and secrets management :info\_abstract: Data encryption and secrets management :info\_titleabbrev: Data encrypt... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/data.adoc | mainline | aws-eks-best-practices | [
-0.030160799622535706,
0.010429405607283115,
-0.007589333225041628,
0.021213138476014137,
0.0187915600836277,
0.039025384932756424,
0.009735215455293655,
0.024775417521595955,
0.07751519978046417,
0.05557223781943321,
-0.03362372890114784,
-0.024100663140416145,
0.04740755632519722,
-0.041... | 0.051614 |
keys. They are persisted in etcd as base64 encoded strings. On EKS, the EBS volumes for etcd nodes are encrypted with https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html[EBS encryption]. A pod can retrieve a Kubernetes secrets objects by referencing the secret in the `podSpec`. These secrets can eith... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/data.adoc | mainline | aws-eks-best-practices | [
-0.03039783239364624,
0.05190030112862587,
0.04897864907979965,
0.000669619592372328,
-0.010325356386601925,
0.03054848499596119,
-0.003872085828334093,
-0.02628461644053459,
0.13640937209129333,
0.04085022211074829,
-0.023537293076515198,
-0.034848589450120926,
0.03166019544005394,
-0.116... | 0.114183 |
the use of external secrets stores has grown, so has need for integrating them with Kubernetes. The https://github.com/kubernetes-sigs/secrets-store-csi-driver[Secret Store CSI Driver] is a community project that uses the CSI driver model to fetch secrets from external secret stores. Currently, the Driver has support f... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/data.adoc | mainline | aws-eks-best-practices | [
-0.06748885661363602,
-0.0033880427945405245,
-0.026461167261004448,
0.017740286886692047,
-0.03160092607140541,
0.02180243283510208,
0.017048770561814308,
-0.00889523047953844,
0.11092106252908707,
0.039001598954200745,
0.011155214160680771,
0.0032880178187042475,
0.05320053920149803,
-0.... | 0.091524 |
//!!NODE\_ROOT [."topic"] [[network-security,network-security.title]] = Network security :info\_doctype: section :info\_title: Network security :info\_abstract: Network security :info\_titleabbrev: Network security :imagesdir: images/security/ include::../attributes.txt[] TIP: https://aws-experience.com/emea/smb/events... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.03430745005607605,
0.08877579122781754,
-0.022925114259123802,
0.0015938816359266639,
0.05125006288290024,
-0.0031007647048681974,
0.06907810270786285,
-0.025616060942411423,
0.07815150171518326,
0.05857447162270546,
-0.020386433228850365,
-0.023731108754873276,
0.07827601581811905,
-0.... | 0.186885 |
egress: - to: - namespaceSelector: matchLabels: kubernetes.io/metadata.name: kube-system podSelector: matchLabels: k8s-app: kube-dns ports: - protocol: UDP port: 53 ---- .allow-dns-access image::allow-dns-access.jpg[allow-dns-access] ==== Incrementally add rules to selectively allow the flow of traffic between namespac... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.05043502524495125,
0.08515071868896484,
0.06324750185012817,
-0.03248657286167145,
-0.03827667236328125,
-0.01742432825267315,
0.048584263771772385,
-0.015885185450315475,
0.051725223660469055,
0.06433495134115219,
-0.036108195781707764,
-0.07320857793092728,
0.006118142511695623,
-0.05... | 0.208281 |
find the SDK binary installed under `/opt/cni/bin` directory on the node. At launch, the SDK provides support for fundamental functionalities such as inspecting eBPF programs and maps. [source,shell] ---- sudo /opt/cni/bin/aws-eks-na-cli ebpf progs ---- ==== Log network traffic metadata https://docs.aws.amazon.com/vpc/... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
0.007496114354580641,
0.022379416972398758,
-0.03137587010860443,
-0.0025057466700673103,
0.1404097080230713,
-0.008236503228545189,
0.04377913475036621,
-0.05462129786610603,
0.12188274413347244,
0.08097046613693237,
-0.026369141414761543,
-0.11416393518447876,
-0.04768097773194313,
-0.03... | 0.182345 |
still apply when using security groups for pods so use them judiciously. ==== [IMPORTANT] ==== You \*must\* create rules for inbound traffic from the cluster security group (kubelet) for all of the probes configured for pod. ==== [IMPORTANT] ==== Security groups for pods relies on a feature known as https://docs.aws.am... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
0.03841676935553551,
-0.015476486645638943,
0.000981649267487228,
0.06250915676355362,
0.07763087004423141,
-0.021450761705636978,
0.019822031259536743,
-0.03401502966880798,
0.05238673835992813,
0.05377758666872978,
0.010299637913703918,
-0.036533601582050323,
0.038504961878061295,
-0.058... | 0.136114 |
Minimize the attack surface by limiting the exposure of your applications [IMPORTANT] ==== Security Groups for pods provides two enforcing modes: `strict` and `standard`. You must use `standard` mode when using both Network Policy and Security Groups for pods features in an EKS cluster. ==== When it comes to network se... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.0006673386669717729,
0.09210359305143356,
0.06582294404506683,
-0.008893770165741444,
0.01167641207575798,
0.02409125678241253,
0.044725481420755386,
-0.001045561395585537,
0.06373562663793564,
0.09716270864009857,
-0.03156060352921486,
-0.07307228446006775,
0.058748770505189896,
-0.038... | 0.266867 |
can find a list of common Kubernetes network policies at https://github.com/ahmetb/kubernetes-network-policy-recipes. A similar set of rules for Calico are available at https://docs.projectcalico.org/security/calico-network-policy. === Migration to Amazon VPC CNI Network Policy Engine To maintain consistency and avoid ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.0008009523153305054,
-0.08188507705926895,
0.031064366921782494,
-0.05202557519078255,
0.029808543622493744,
0.033429600298404694,
-0.0406782366335392,
-0.07211380451917648,
0.01371061336249113,
0.049942053854465485,
-0.018185222521424294,
-0.09505067020654678,
0.002981176134198904,
-0.... | 0.071874 |
Mesh, Linkerd v2, and Istio. AppMesh supports https://docs.aws.amazon.com/app-mesh/latest/userguide/mutual-tls.html[mTLS] with X.509 certificates or Envoy's Secret Discovery Service(SDS). Linkerd and Istio both have support for mTLS. The https://github.com/aws/aws-app-mesh-examples[aws-app-mesh-examples] GitHub reposit... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.08688764274120331,
0.04818098247051239,
0.039138827472925186,
0.017666567116975784,
0.008452140726149082,
-0.047208674252033234,
-0.050047896802425385,
0.012719925493001938,
0.06997641921043396,
0.05846507474780083,
-0.06189705431461334,
-0.08636847883462906,
0.0813402459025383,
0.06906... | 0.152066 |
Kubernetes add-on to distribute, renew, and revoke certificates. ACM Private CA is a highly-available, secure, managed CA without the upfront and maintenance costs of managing your own CA. If you are using the default Kubernetes certificate authority, there is an opportunity to improve your security and meet compliance... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.023689378052949905,
0.06656864285469055,
0.0880315899848938,
0.0793641209602356,
-0.024802230298519135,
0.005656122695654631,
-0.009411385282874107,
0.01483312901109457,
0.13850675523281097,
0.027216704562306404,
0.022079816088080406,
-0.05200545862317085,
0.060862552374601364,
0.018794... | 0.08512 |
specify a service account, Kubernetes will automatically assign one to your workload. Also, service accounts automatically mount an associated token. This token is used by the service account for workloads to authenticate against the Kubernetes API. The service account may be sufficient as an identity for Kubernetes bu... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.07020553201436996,
0.0006458457792177796,
0.014190834946930408,
0.010783457197248936,
-0.05390423536300659,
-0.0010482737561687827,
0.11479048430919647,
0.016326934099197388,
0.12373032420873642,
0.00314082158729434,
-0.05267465487122536,
-0.12294729053974152,
0.0024551793467253447,
0.0... | 0.485487 |
signing requests for workloads to verify that they get approved and signed (`preserveCertificateRequests=true`). + [source,bash] ---- helm install -n cert-manager cert-manager-istio-csr jetstack/cert-manager-istio-csr \ --set "app.certmanager.issuer.group=awspca.cert-manager.io" \ --set "app.certmanager.issuer.kind=AWS... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/network.adoc | mainline | aws-eks-best-practices | [
-0.019534235820174217,
0.04497113078832626,
-0.0504094734787941,
0.007048445288091898,
0.007044720463454723,
-0.08387095481157303,
0.04668942466378212,
0.005894846748560667,
0.057183608412742615,
-0.01614227332174778,
-0.01759946160018444,
-0.15136250853538513,
0.046874161809682846,
0.0660... | 0.121628 |
//!!NODE\_ROOT [."topic"] [[tenant-isolation,tenant-isolation.title]] = Tenant Isolation :info\_doctype: section :info\_title: Tenant Isolation :info\_abstract: Tenant Isolation :info\_titleabbrev: Multi-tenancy :imagesdir: images/ When we think of multi-tenancy, we often want to isolate a user or application from othe... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.042198460549116135,
-0.0026906286366283894,
0.011490839533507824,
0.0015822270652279258,
0.00352347525767982,
-0.0030601348262280226,
0.01297763828188181,
-0.02383452281355858,
0.11291323602199554,
0.008880112320184708,
0.014632759615778923,
-0.05064351111650467,
0.06848306953907013,
-0.... | 0.178044 |
spaces in different clusters \* \*Sleep mode\* scales down deployments in a space during periods of inactivity \* \*Single sign-on\* with OIDC authentication providers like GitHub There are three primary use cases that can be addressed by soft multi-tenancy. === Enterprise Setting The first is in an Enterprise setting ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.011039958335459232,
-0.07716725766658783,
0.002481430070474744,
0.012508304789662361,
-0.011522050015628338,
-0.03209569305181503,
0.04562130570411682,
-0.06289801746606827,
0.08765614032745361,
-0.0018500842852517962,
0.029820065945386887,
-0.02537316456437111,
0.04200134426355362,
-0.0... | 0.177335 |
to query the DNS server for name resolution. With that in place, you can begin adding more permissive rules that allow for communication within a namespace. This can be further refined as required. [NOTE] ==== Amazon https://aws.amazon.com/blogs/containers/amazon-vpc-cni-now-supports-kubernetes-network-policies/[VPC CN... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
-0.024014467373490334,
0.02541344054043293,
-0.0008055259240791202,
-0.023754186928272247,
-0.05832488462328911,
0.029425790533423424,
0.009684971533715725,
-0.0466584786772728,
0.10050327330827713,
0.04557093232870102,
-0.07380358129739761,
-0.0777856633067131,
0.05339941754937172,
-0.038... | 0.144226 |
Pods, see https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#limitations-of-preemption[Limitations of preemption]. ==== == Mitigating controls Your chief concern as an administrator of a multi-tenant environment is preventing an attacker from gaining access to the underlying host. The foll... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.08009768277406693,
0.0819956362247467,
0.017013881355524063,
0.012041176669299603,
-0.0008601693552918732,
-0.01978195831179619,
-0.02927304059267044,
-0.0436619408428669,
0.03477818891406059,
0.0679430142045021,
-0.004171357955783606,
-0.00571517925709486,
0.022933047264814377,
-0.01807... | 0.118661 |
by modifying the node labels. ==== [INFO] ==== Instead of node affinity, we could have used the https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector[node selector]. However, node affinity is more expressive and allows for more conditions to be considered during pod scheduling. For addit... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.017639774829149246,
0.06123851612210274,
0.05923319607973099,
0.05714087188243866,
0.039328355342149734,
0.004574993159621954,
0.09806127846240997,
-0.09388729929924011,
0.018404223024845123,
0.041637130081653595,
-0.01825597696006298,
-0.04985533654689789,
0.0269797220826149,
0.02393465... | 0.137629 |
to a Kubernetes API server request, to apply a pod to the \_tenants-x\_ namespace. The policy adds the `requiredDuringSchedulingIgnoredDuringExecution` node affinity rule, so that pods are attracted to nodes with the `tenant: tenants-x` label. A second policy, seen below, adds the toleration to the same pod specificati... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.042932409793138504,
0.01148576196283102,
0.05799608305096626,
0.030658261850476265,
0.049015093594789505,
-0.0062574059702456,
0.019979044795036316,
-0.0672721192240715,
0.06697935611009598,
0.04925110936164856,
0.006050559692084789,
-0.06729582697153091,
0.023158106952905655,
-0.0192682... | 0.15118 |
to include \_Audit\_ policies to routinely check your cluster for unwanted configurations. ==== === References \* https://github.com/cruise-automation/k-rail[k-rail] Designed to help you secure a multi-tenant environment through the enforcement of certain policies. \* https://d1.awsstatic.com/whitepapers/security-pract... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multitenancy.adoc | mainline | aws-eks-best-practices | [
0.0650131106376648,
-0.020645469427108765,
-0.05442586913704872,
0.02369825914502144,
0.036395784467458725,
0.01907280460000038,
-0.0019670540932565928,
-0.07232492417097092,
-0.004002500791102648,
0.05872923880815506,
0.021579526364803314,
-0.07919524610042572,
0.09635865688323975,
0.0077... | 0.043547 |
//!!NODE\_ROOT [."topic"] [[compliance,compliance.title]] = Compliance :info\_doctype: section :info\_title: Compliance :info\_abstract: Compliance :info\_titleabbrev: Regulatory Compliance :imagesdir: images/ Compliance is a shared responsibility between AWS and the consumers of its services. Generally speaking, AWS i... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/compliance.adoc | mainline | aws-eks-best-practices | [
0.012235263362526894,
0.03799283131957054,
-0.01452145166695118,
-0.062337007373571396,
0.11460677534341812,
-0.046050507575273514,
0.012850477360188961,
-0.021901508793234825,
0.06280517578125,
0.00727056572213769,
0.004949118942022324,
0.008427025750279427,
0.0546526201069355,
-0.0178190... | 0.120522 |
source policy engine that's part of the CNCF. It's used for making policy decisions and can be run a variety of different ways, e.g. as a language library or a service. OPA policies are written in a Domain Specific Language (DSL) called Rego. While it is often run as part of a Kubernetes Dynamic Admission Controller as... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/compliance.adoc | mainline | aws-eks-best-practices | [
-0.053613755851984024,
0.020568402484059334,
-0.00821631494909525,
-0.027399122714996338,
-0.012313448823988438,
-0.06164487451314926,
-0.00677562365308404,
0.017613576725125313,
0.07621630281209946,
0.051533326506614685,
-0.01233209203928709,
-0.016439132392406464,
-0.005619271192699671,
... | 0.195178 |
//!!NODE\_ROOT [[security,security.title]] = Amazon EKS Best Practices Guide for Security :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Security :info\_abstract: Best Practices for Security :info\_titlea... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/index.adoc | mainline | aws-eks-best-practices | [
-0.05980949103832245,
0.12441261112689972,
-0.015313508920371532,
0.014817511662840843,
0.044424742460250854,
0.027996741235256195,
0.04533772170543671,
-0.027535615488886833,
0.030342567712068558,
0.05961966514587402,
0.022077888250350952,
0.020383939146995544,
0.08112876117229462,
-0.054... | 0.181046 |
your security posture. For example, you need to control who can perform actions against a set of resources. You also need the ability to quickly identify security incidents, protect your systems and services from unauthorized access, and maintain the confidentiality and integrity of data through data protection. Having... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/index.adoc | mainline | aws-eks-best-practices | [
-0.028769712895154953,
0.05779034644365311,
0.025934262201189995,
0.014086631126701832,
0.06287957727909088,
0.0007192761404439807,
0.005367862991988659,
0.005904220510274172,
0.07694820314645767,
0.07138650864362717,
-0.014240543358027935,
-0.0022285236045718193,
0.053843770176172256,
-0.... | 0.150411 |
//!!NODE\_ROOT [."topic"] [[protecting-the-infrastructure,protecting-the-infrastructure.title]] = Protecting the infrastructure (hosts) :info\_doctype: section :info\_title: Protecting the infrastructure (hosts) :info\_abstract: Protecting the infrastructure (hosts) :info\_titleabbrev: Infrastructure Security :imagesdi... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/hosts.adoc | mainline | aws-eks-best-practices | [
0.025589091703295708,
0.0892546996474266,
-0.0038581264670938253,
-0.04766981676220894,
0.1701129674911499,
-0.08120915293693542,
0.02376589924097061,
0.0764833390712738,
-0.03980740159749985,
-0.006719883531332016,
0.038682084530591965,
0.02079113945364952,
0.05905642732977867,
-0.0190542... | 0.082573 |
kube-bench is an open source project from Aqua that evaluates your cluster against the CIS benchmarks for Kubernetes. The benchmark describes the best practices for securing unmanaged Kubernetes clusters. The CIS Kubernetes Benchmark encompasses the control plane and the data plane. Since Amazon EKS provides a fully ma... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/hosts.adoc | mainline | aws-eks-best-practices | [
-0.025907404720783234,
0.02429956942796707,
-0.013026826083660126,
0.04797732084989548,
-0.010966598987579346,
0.0007689340854994953,
-0.035482633858919144,
-0.036465924233198166,
0.08024293929338455,
0.07140877097845078,
-0.044488325715065,
-0.05708557739853859,
0.06348633766174316,
-0.11... | 0.159336 |
Regardless of SSM agent status, all of your Amazon EC2 instances are scanned for network reachability issues. For more information about configuring scans for Amazon EC2, see https://docs.aws.amazon.com/inspector/latest/user/enable-disable-scanning-ec2.html[Scanning Amazon EC2 instances]. [IMPORTANT] ==== Inspector can... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/hosts.adoc | mainline | aws-eks-best-practices | [
0.10244951397180557,
0.0031607074197381735,
-0.07165686786174774,
0.00293806754052639,
0.1015552207827568,
-0.021959753707051277,
-0.030376430600881577,
-0.009251694194972515,
0.03396666422486305,
-0.05236378312110901,
-0.006780912168323994,
0.02703343890607357,
0.04420553892850876,
-0.071... | 0.19252 |
---- docker container run -it \ -v /var/log:/host/var/log:Z \ fluentbit:latest ---- In Kubernetes, relabeling is slightly different. Rather than having Docker automatically relabel the files, you can specify a custom MCS label to run the pod. Volumes that support relabeling will automatically be relabeled so that they ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/hosts.adoc | mainline | aws-eks-best-practices | [
0.03354710713028908,
0.03502872586250305,
0.004409519024193287,
-0.022677332162857056,
0.019060537219047546,
-0.0019060727208852768,
0.05182510241866112,
0.024523185566067696,
0.058216772973537445,
-0.007081056945025921,
-0.03000008314847946,
-0.04742754250764847,
0.03265223279595375,
0.00... | 0.126633 |
//!!NODE\_ROOT [."topic"] [[image-security,image-security.title]] = Image security :info\_doctype: section :info\_title: Image security :info\_abstract: Image security :info\_titleabbrev: Image security :imagesdir: images/ include::../attributes.txt[] You should consider the container image as your first line of defens... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
0.05785397067666054,
0.1370759755373001,
0.022225957363843918,
0.023097140714526176,
0.14561879634857178,
-0.06764312088489532,
0.031738217920064926,
0.01587587594985962,
0.03387004882097244,
0.02772505022585392,
0.024058012291789055,
-0.034393612295389175,
0.14475472271442413,
0.008105719... | 0.014977 |
by creating an attested pipeline execution report along with attested SBOM and attested CVE scan report to assure the consumers of the image that this image is in-fact created through secure means (pipeline) with secure components. \* \*Dependency Trust Verification\*: recursive checking of an artifact's dependency tre... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
-0.020831843838095665,
-0.015755347907543182,
-0.05335589870810509,
-0.019500279799103737,
0.1291922628879547,
-0.02724115177989006,
-0.0159946046769619,
-0.0026766443625092506,
-0.0016348946373909712,
0.025227908045053482,
0.015647701919078827,
-0.03465326502919197,
0.05492411181330681,
-... | 0.124912 |
without knowing all the software components or dependencies that are included in that image. However, if we trust whatever the producer of the container image says about what software is present, we can use the producer's attestation to rely on that artifact. This means that we can proceed to use the artifact safely in... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
-0.04361742362380028,
0.12312475591897964,
0.005559172946959734,
-0.05448588356375694,
0.056903909891843796,
-0.11548316478729248,
-0.005442936904728413,
-0.02219647355377674,
0.0388370007276535,
0.008355708792805672,
0.04288220405578613,
-0.04113728925585747,
0.043263569474220276,
-0.0359... | 0.161379 |
vended from and cluster region. [cols=",",options="header",] |=== |Account Number |Region |602401143452 |All commercial regions except for those listed below |— |— |800184023465 |ap-east-1 - Asia Pacific (Hong Kong) |558608220178 |me-south-1 - Middle East (Bahrain) |918309763551 |cn-north-1 - China (Beijing) |961992271... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
0.035738423466682434,
0.05540599301457405,
-0.00874853041023016,
-0.06072499603033066,
0.07713152468204498,
0.02683711238205433,
-0.036750517785549164,
-0.07329734414815903,
-0.021093351766467094,
-0.011078950949013233,
0.014488676562905312,
-0.0895569920539856,
0.008381347171962261,
-0.02... | 0.058144 |
Dockerfiles that violate a rule will automatically fail. === Build images from Scratch Reducing the attack surface of your container images should be primary aim when building images. The ideal way to do this is by creating minimal images that are devoid of binaries that can be used to exploit vulnerabilities. Fortunat... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
-0.0037359001580625772,
0.10245846956968307,
0.025525737553834915,
-0.027022290974855423,
0.0366397462785244,
-0.05035989731550217,
-0.0053077335469424725,
0.0382368266582489,
-0.04862862825393677,
0.028059858828783035,
-0.016773948445916176,
-0.08836166560649872,
0.08417938649654388,
0.05... | -0.017057 |
the report, e.g. a CVE scan should not have any critical CVEs. Deployment is allowed only for images that satisfy these conditions and all other deployments will be rejected by the admissions controller. Examples of admission controller include: \* https://kyverno.io/[Kyverno] \* https://github.com/open-policy-agent/ga... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/image.adoc | mainline | aws-eks-best-practices | [
-0.0771520733833313,
-0.000030275950848590583,
-0.02385895699262619,
-0.08348307013511658,
0.03524010255932808,
-0.022492721676826477,
-0.011752868071198463,
0.04824835807085037,
-0.12574636936187744,
0.02082778885960579,
0.052870962768793106,
-0.0028518789913505316,
0.04133955016732216,
0... | 0.11192 |
//!!NODE\_ROOT [."topic"] [[multi-account-strategy,multi-account-strategy.title]] = Multi Account Strategy :info\_doctype: section :info\_title: Multi Account Strategy :info\_abstract: Multi Account Strategy :info\_titleabbrev: Multi Account Strategy :imagesdir: images/security/ include::../attributes.txt[] AWS recomme... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.015092593617737293,
0.007643426302820444,
-0.03899642452597618,
-0.020684946328401566,
0.06727366149425507,
-0.029225558042526245,
-0.0020736916922032833,
0.02535492740571499,
0.1032865047454834,
0.03641039505600929,
-0.026181180030107498,
-0.009772821329534054,
0.1025204062461853,
-0.0... | 0.121779 |
very large scale, you may require multiple `Cluster Accounts` to ensure that there are enough kubernetes and AWS service quotas available to all your workloads. //GDC: check image path image:multi-account-eks.jpg[multi-account-eks] |In the above diagram, AWS RAM is used to share subnets from a cluster account into a wo... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
0.04012259468436241,
-0.01582152023911476,
-0.03254006803035736,
0.01853722147643566,
-0.0038009427953511477,
0.03522002696990967,
-0.003063905518501997,
-0.03728413209319115,
0.08155053108930588,
0.052249785512685776,
-0.04052715376019478,
-0.03774533048272133,
0.03918607532978058,
-0.015... | 0.104209 |
the same procedure for setting up https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html[IRSA], except the Identity Provider will be created in the workload account. Then when configuring IRSA for your workloads on EKS, you can https://docs.aws.amazon.com/eks/latest/userguide/associ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.08630075305700302,
0.02071038819849491,
-0.0553111806511879,
0.02533775195479393,
-0.00709346542134881,
0.00960591435432434,
0.09541783481836319,
-0.01029399037361145,
0.07029634714126587,
0.039235275238752365,
-0.030398719012737274,
-0.06643141806125641,
0.06249716132879257,
0.01412886... | 0.129198 |
creating additional IAM roles. Session policies are applied when EKS Pod Identity assumes the role and the resulting permissions are the intersection of the role policy and the session policy; for considerations and detailed steps, refer to the AWS Containers blog https://aws.amazon.com/blogs/containers/session-policie... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.007487806491553783,
0.04953581094741821,
-0.01802819035947323,
-0.01006810087710619,
-0.015632953494787216,
-0.003259902121499181,
0.13529425859451294,
-0.027271879836916924,
0.046670131385326385,
0.06838679313659668,
0.020773254334926605,
-0.09585636109113693,
0.05437213554978371,
0.01... | 0.159353 |
deployed to respective workload accounts. Then workloads running in EKS pods use IRSA or EKS Pod Identities to access their AWS resources. GitOps is a way of managing application and infrastructure deployment so that the whole system is described declaratively in a Git repository. It's an operational model that offers ... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.006631531752645969,
-0.0200812891125679,
0.011657868511974812,
0.021895455196499825,
-0.019854068756103516,
-0.007426667958498001,
0.05035973712801933,
-0.012510648928582668,
0.12000760436058044,
0.08362671732902527,
-0.037700552493333817,
-0.045306578278541565,
0.05143756791949272,
-0.... | 0.230603 |
clusters and VPCs are present, each workload has more available k8s and AWS service quota |Networking: |Single VPC is used per cluster, allowing for simpler connectivity for applications on that cluster |Routing must be established between the de-centralized EKS cluster VPCs |Kubernetes Access Management: |Need to main... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.017401661723852158,
0.005644167773425579,
-0.02507423236966133,
0.04077655449509621,
0.018080471083521843,
0.04987232759594917,
0.05366034060716629,
-0.03265633061528206,
0.1084134429693222,
0.06272038072347641,
-0.030363962054252625,
-0.058175958693027496,
0.05113605037331581,
-0.01903... | 0.209915 |
//!!NODE\_ROOT [."topic"] [[vpc-cni,vpc-cni.title]] = Amazon VPC CNI :info\_doctype: section :info\_title: Amazon VPC CNI :info\_abstract: Amazon VPC CNI :info\_titleabbrev: Amazon VPC CNI :imagesdir: images/networking/ [abstract] -- Amazon VPC CNI -- TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.06157679855823517,
-0.022654319182038307,
-0.09407134354114532,
-0.00346924876794219,
0.08643106371164322,
0.03444809094071388,
-0.02080896496772766,
-0.06219625100493431,
0.038788143545389175,
0.006638532038778067,
-0.006274444051086903,
-0.05120375379920006,
0.03611740469932556,
-0.04... | 0.159745 |
a generic overview of VPC CNI behavior when Secondary IP mode is enabled. The functionality of ipamd (allocation of IP addresses) may vary depending on the configuration settings for VPC CNI, such as <>, <>, and <>. The Amazon VPC CNI is deployed as a Kubernetes Daemonset named aws-node on worker nodes. When a worker n... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.055259160697460175,
-0.01740128919482231,
0.010359769687056541,
-0.011397242546081543,
0.04087201505899429,
-0.009268036112189293,
0.01483466662466526,
-0.08874888718128204,
0.08084610104560852,
0.04685688018798828,
-0.0022943331860005856,
-0.024156779050827026,
0.0446932390332222,
-0.0... | 0.180032 |
second ENI, consuming 20 possible addresses from the subnet CIDR. \* `MINIMUM\_IP\_TARGET`, Integer, Values greater than 0 indicate requirement Enabled \*\* The minimum number of IP addresses to be allocated at any time. This is commonly used to front-load the assignment of multiple ENIs at instance launch. \*\* Exampl... | https://github.com/aws/aws-eks-best-practices/blob/mainline/latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.01163402572274208,
0.02502526342868805,
0.014344888739287853,
-0.002335938857868314,
0.03320445120334625,
-0.08376661688089371,
0.019543956965208054,
-0.07395406067371368,
0.06122530251741409,
0.0480048842728138,
-0.0279962457716465,
-0.052752211689949036,
0.09593687951564789,
-0.039110... | 0.130594 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.