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 |
|---|---|---|---|---|---|
(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 |
account, or use a common IAM role across multiple service accounts and use ABAC to control what accounts it can access. To use ABAC to control what service accounts can assume a role into another account with role chaining, you create a role trust policy statement that only allows a role to be assumed by a role session... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
-0.04961549490690231,
0.030821576714515686,
-0.026140447705984116,
0.017735755071043968,
-0.019177712500095367,
0.0057550533674657345,
0.11319583654403687,
-0.06815630942583084,
0.062015071511268616,
0.03210028260946274,
0.035924751311540604,
-0.13336054980754852,
0.06329996138811111,
0.01... | 0.122797 |
clusters and other AWS resources in them. This enables centralized network managment/administration, simplified network connectivity, and de-centralized EKS clusters. Refer this https://aws.amazon.com/blogs/containers/use-shared-vpcs-in-amazon-eks/[AWS blog] for a detailed walkthrough and considerations of this approac... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/security/multiaccount.adoc | mainline | aws-eks-best-practices | [
0.006021470297127962,
0.014490769244730473,
-0.04830794408917427,
0.03635355830192566,
0.056879233568906784,
0.025925610214471817,
-0.0070353783667087555,
0.017666591331362724,
0.10478010773658752,
0.05149085819721222,
-0.05030498653650284,
-0.00006736177601851523,
0.04702160507440567,
-0.... | 0.212404 |
//!!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 |
VPC CNI. This guide provides 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 ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.06105511263012886,
-0.024858005344867706,
0.0043343836441636086,
-0.007225270848721266,
0.04833386838436127,
-0.004530715756118298,
0.010968692600727081,
-0.08917773514986038,
0.08383678644895554,
0.043851934373378754,
-0.010352660901844501,
-0.026438487693667412,
0.04015199840068817,
-... | 0.174256 |
the CNI will attach a 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 instan... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.01756896637380123,
0.007854236289858818,
0.003665802301838994,
-0.011380697600543499,
0.03058612532913685,
-0.0777009129524231,
0.012254195287823677,
-0.07438603788614273,
0.05938965827226639,
0.05321180075407028,
-0.016587894409894943,
-0.064844511449337,
0.09568990767002106,
-0.039650... | 0.127869 |
launch template. As an example, on a cluster with 3 c5.large nodes (3 ENIs and max 10 IPs per ENI), when the cluster starts up and has 2 CoreDNS pods, the CNI will consume 50 IP addresses and keep 43 IPs in warm pool. The warm pool enables faster Pod launches when the application is deployed. Node 1 (with CoreDNS pod):... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.012150218710303307,
-0.019506370648741722,
0.015314965508878231,
-0.00435125594958663,
0.021330639719963074,
-0.022522874176502228,
-0.028404174372553825,
-0.04522089287638664,
0.0023192784283310175,
0.04100620746612549,
-0.02413337305188179,
-0.06279516220092773,
0.03663194924592972,
-... | 0.181371 |
volume mounts. NOTE: The most frequently used fields such as WARM\_ENI\_TARGET, WARM\_IP\_TARGET, and MINIMUM\_IP\_TARGET are not managed and will not be reconciled. The changes to these fields will be preserved upon updating of the add-on. We suggest testing the add-on behavior in your non-production clusters for a sp... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
0.004415812436491251,
-0.04933600127696991,
0.037355177104473114,
0.021442798897624016,
0.07247759401798248,
-0.0016006267396733165,
-0.05012967064976692,
-0.061351384967565536,
0.060621824115514755,
0.045738525688648224,
0.03770861402153969,
-0.07284475862979889,
0.0700758770108223,
-0.02... | 0.090932 |
or removed. The aws-node Daemonset is a long-running process responsible for IP address management at the node level. The aws-node runs in `hostNetwork` mode and allows access to the loopback device, and network activity of other pods on the same node. The aws-node init-container runs in privileged mode and mounts the ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.033034548163414,
0.07433149218559265,
-0.026304829865694046,
0.0028023922350257635,
0.09160169959068298,
0.03140058368444443,
0.007787064183503389,
-0.041714560240507126,
0.02079792693257332,
0.11086315661668777,
-0.02957388013601303,
-0.04729778319597244,
0.040320269763469696,
-0.03974... | 0.080975 |
AMI, make sure to set iptables forward policy to ACCEPT under https://github.com/awslabs/amazon-eks-ami/blob/master/files/kubelet.service#L8[kubelet.service]. Many systems set the iptables forward policy to DROP. You can build custom AMI using https://packer.io/intro/why.html[HashiCorp Packer] and a build specification... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/vpc-cni.adoc | mainline | aws-eks-best-practices | [
-0.009424162097275257,
0.03380824625492096,
-0.01862655207514763,
-0.0780123919248581,
0.003817994613200426,
-0.01296872179955244,
-0.07253211736679077,
0.008184166625142097,
0.0657341256737709,
0.0315183624625206,
0.05128601938486099,
-0.0834396481513977,
0.041129712015390396,
-0.04940370... | 0.077402 |
//!!NODE\_ROOT [."topic"] [[sgpp,sgpp.title]] = Security Groups Per Pod :info\_doctype: section :info\_title: Security Groups Per Pod :info\_abstract: Security Groups Per Pod :info\_titleabbrev: Security Groups Per Pod :imagesdir: images/networking/ [abstract] -- Security Groups Per Pod -- TIP: https://aws-experience.c... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.007252009119838476,
0.031934745609760284,
-0.032486021518707275,
0.021411193534731865,
0.11570609360933304,
-0.010002953000366688,
0.035965729504823685,
-0.04839736223220825,
0.0995883196592331,
-0.012921660207211971,
0.05382048338651657,
-0.04542747139930725,
0.06123163178563118,
-0.05... | 0.198432 |
max-pods for nodes. When security groups for Pods are used in combination with https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html[custom networking], the security group defined in security groups for Pods is used rather than the security group specified in the ENIConfig. As a result, when custom n... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
0.06529010832309723,
0.048916008323431015,
0.0511687733232975,
0.006640751380473375,
-0.052215609699487686,
-0.015309732407331467,
-0.03430142626166344,
-0.027914488688111305,
0.07920898497104645,
0.0681787058711052,
-0.04874323680996895,
-0.067233607172966,
0.028895152732729912,
-0.072744... | 0.118334 |
can now run Kubernetes services of type NodePort and LoadBalancer using instance targets with an externalTrafficPolicy set to Local in the standard mode. `Local` preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type Services. \*Deploying NodeLocal DNSCache\* When using security group... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.0010462065692991018,
0.008159947581589222,
0.07918756455183029,
0.012575686909258366,
-0.04973762482404709,
0.0048486716113984585,
-0.03168322890996933,
-0.029738515615463257,
0.057491008192300797,
0.058039430528879166,
-0.07255413383245468,
-0.03286370262503624,
-0.025749847292900085,
... | 0.152974 |
AWS Loadbalancer Controller to update the rules of security groups to route traffic to the Pods. If just one security group is given to a Pod, the assignment of a tag is optional. Permissions set in a security group are additive, therefore tagging a single security group is sufficient for the loadbalancer controller to... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/sgpp.adoc | mainline | aws-eks-best-practices | [
-0.029353970661759377,
0.011602304875850677,
-0.03356817737221718,
0.0013537536142393947,
0.04955344647169113,
0.00539804482832551,
-0.0046862224116921425,
-0.018931467086076736,
0.054783422499895096,
0.04475914314389229,
-0.040372561663389206,
-0.05772765725851059,
0.014353200793266296,
-... | 0.103782 |
//!!NODE\_ROOT [."topic"] [[prefix-mode-linux,prefix-mode-linux.title]] = Prefix Mode for Linux :info\_doctype: section :info\_title: Prefix Mode for Linux :info\_abstract: Prefix Mode for Linux :info\_titleabbrev: Prefix Mode for Linux :imagesdir: images/networking/ [abstract] -- Prefix Mode for Linux -- TIP: https://... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
0.015577152371406555,
-0.025589851662516594,
-0.013591470196843147,
-0.01630735769867897,
0.06866034865379333,
-0.019735820591449738,
-0.04425947740674019,
0.01722380332648754,
0.0545329786837101,
0.017804153263568878,
0.03432619571685791,
0.004782371688634157,
0.038659512996673584,
-0.044... | 0.124555 |
Recommendations === Use Prefix Mode when Use prefix mode if you are experiencing Pod density issue on the worker nodes. To avoid VPC CNI errors, we recommend examining the subnets for contiguous block of addresses for /28 prefix before migrate to prefix mode. Please refer "`https://docs.aws.amazon.com/vpc/latest/usergu... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
-0.006050619296729565,
-0.007301156409084797,
0.030117511749267578,
0.021228069439530373,
0.03633810207247734,
-0.015028031542897224,
-0.03740914165973663,
-0.026471227407455444,
0.02140250988304615,
0.06012057140469551,
0.0032862541265785694,
-0.09150981158018112,
0.03146704286336899,
-0.... | 0.049587 |
node when running in prefix mode. If you can afford (in the worst case) up to 15 unused IPs per node, we strongly recommend using the newer prefix assignment networking mode, and realizing the performance and efficiency gains that come with it. === Use Subnet Reservations to Avoid Subnet Fragmentation (IPv4) When EC2 a... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_linux.adoc | mainline | aws-eks-best-practices | [
0.00218008179217577,
-0.014528179541230202,
0.018381493166089058,
-0.006582038942724466,
0.06168690323829651,
-0.017745740711688995,
-0.08537404239177704,
-0.019312093034386635,
0.045206595212221146,
0.03953244909644127,
0.03496586158871651,
-0.06434376537799835,
0.02006910741329193,
-0.02... | -0.010801 |
//!!NODE\_ROOT [."topic"] [[load-balancing,load-balancing.title]] = Load Balancing :info\_titleabbrev: Load Balancing :info\_doctype: section :imagesdir: images/networking/ TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Explore] ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
-0.058944541960954666,
0.03294752165675163,
0.004231492523103952,
0.006066157948225737,
-0.03165058419108391,
0.003158970968797803,
0.025162961333990097,
-0.02782365120947361,
0.13677315413951874,
0.05210153013467789,
-0.09676623344421387,
-0.049315132200717926,
0.03950227424502373,
-0.061... | 0.156892 |
\* Leveraging the AWS Load Balancer Controller (recommended) By default, the Kubernetes Service Controller, also known as the in-tree controller, reconciles the Kubernetes Service resource of type LoadBalancer. This controller is built into the link:https://github.com/kubernetes/cloud-provider-aws[AWS Cloud Provider] c... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
-0.03427764028310776,
0.01056115236133337,
0.02709798328578472,
-0.029368221759796143,
-0.0006665270193479955,
0.036362580955028534,
0.03313412144780159,
-0.025406615808606148,
0.14053967595100403,
0.08353327959775925,
-0.054145701229572296,
-0.02813234180212021,
0.016697414219379425,
-0.0... | 0.118943 |
pod, this simplifies the network path as it bypasses the previous extra hops of Worker Nodes and Service Cluster IP, it reduces latency that would otherwise have been incurred if the Service forwarded traffic to a pod in another AZ and lastly it removes the iptables rules overhead processing on the Worker Nodes. \* The... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.03472960740327835,
0.06235814839601517,
0.01953529380261898,
0.024735836312174797,
0.07114363461732864,
-0.031995296478271484,
0.04486667364835739,
-0.031105078756809235,
0.07871422916650772,
0.08726580440998077,
-0.05505122244358063,
0.03235836327075958,
0.017191922292113304,
-0.0861060... | 0.288206 |
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-readiness-status[all the containers within a Pod are running] the https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions[Pod condition] is considered to be "`Ready`". However the application may still not be able to process ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.033080291002988815,
0.016149992123246193,
0.0219364482909441,
-0.020656157284975052,
0.001897183246910572,
-0.03731293976306915,
-0.029693108052015305,
-0.03699906915426254,
0.0660301148891449,
0.11055804044008255,
-0.018848901614546776,
0.027534468099474907,
-0.017583632841706276,
-0.01... | 0.168049 |
prevent the rolling update of a deployment from terminating old pods until the newly created Pods target status turn "`Healthy`" on the AWS ELB. === Gracefully shutdown applications Your application should respond to a SIGTERM signal by starting its graceful shutdown so that clients do not experience any downtime. What... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.0549640879034996,
0.026301855221390724,
0.08133180439472198,
-0.0035530172754079103,
-0.01881934329867363,
-0.05718475952744484,
-0.032772794365882874,
0.005079421680420637,
0.04422098398208618,
0.06038600206375122,
-0.024070877581834793,
0.0038634908851236105,
-0.04946275055408478,
-0.1... | 0.14422 |
takes for the application to close out the connections gracefully. Hence the not so perfect but most feasible approach here is to use a PreStop hook to delay the SIGTERM signal until the iptables rules are updated to make sure that no new client requests are sent to the application rather, only existing connections car... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.008927551098167896,
0.0549449659883976,
0.01618966832756996,
-0.016954775899648666,
0.008998709730803967,
-0.014906050637364388,
0.032421696931123734,
-0.012442103587090969,
0.10596819967031479,
0.06986337900161743,
-0.06017501652240753,
-0.015352921560406685,
0.019948020577430725,
-0.11... | 0.087682 |
container runtime to start the containers defined in the Pod spec. . When the containers starts running, the kubelet updates the https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions[Pod condition] as `Ready` in the Pod object in the Kubernetes API. . The https://kubernetes.io/docs/concepts/o... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/loadbalancing.adoc | mainline | aws-eks-best-practices | [
0.023481642827391624,
0.008150296285748482,
0.008913019672036171,
0.0003507430083118379,
-0.022408582270145416,
0.016558948904275894,
-0.01820331998169422,
-0.040331896394491196,
0.09520522505044937,
0.07653463631868362,
-0.005994731560349464,
0.02899508737027645,
-0.03634851053357124,
-0.... | 0.156818 |
//!!NODE\_ROOT [."topic"] [[custom-networking,custom-networking.title]] = Custom Networking :info\_doctype: section :imagesdir: images/networking/ :info\_title: Custom Networking :info\_abstract: Custom Networking :info\_titleabbrev: Custom Networking [abstract] -- Custom Networking -- TIP: https://aws-experience.com/... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
-0.009417776949703693,
0.010673176497220993,
0.0067833405919373035,
-0.0005910249892622232,
0.03139400854706764,
0.03401416540145874,
-0.013564251363277435,
-0.02513514645397663,
0.05634104460477829,
0.07524830847978592,
-0.01230337843298912,
-0.040328845381736755,
0.03750953823328018,
-0.... | 0.113779 |
challenges. Please consider using prefix delegation with custom networking to increase the Pods density on a node. You might consider custom networking if you have a security requirement to run Pods on a different network with different security group requirements. When custom networking enabled, the pods use different... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.008364556357264519,
0.0036785872653126717,
0.01772245205938816,
0.036131974309682846,
-0.014916393905878067,
0.025683477520942688,
-0.03055666573345661,
0.009275581687688828,
0.0368032231926918,
0.09049516916275024,
-0.08602694422006607,
-0.07092075049877167,
0.042992766946554184,
-0.046... | 0.155043 |
address ranges, customers have the option of using VPC Peering to interconnect such VPCs. This method could provide potential cost savings as all data transit within an Availability Zone via a VPC peering connection is now free. image::cn-image-3.png[illustration of network traffic using private NAT gateway] ==== Uniqu... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.00909245666116476,
-0.009804265573620796,
-0.0023446260020136833,
0.05969822779297829,
0.014767852611839771,
0.056594137102365494,
0.0026018228381872177,
-0.042844004929065704,
0.03605448082089424,
0.04628355801105499,
-0.02715454436838627,
-0.02868863008916378,
0.04755891114473343,
-0.0... | 0.088081 |
primary ENI is no longer used to assign Pod IP addresses, there is a decrease in the number of Pods you can run on a given EC2 instance type. To work around this limitation you can use prefix assignment with custom networking. With prefix assignment, each secondary IP is replaced with a /28 prefix on secondary ENIs. Co... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/custom-networking.adoc | mainline | aws-eks-best-practices | [
0.0411822535097599,
-0.012476414442062378,
0.06792476773262024,
-0.04487057030200958,
-0.03352782502770424,
-0.0463559664785862,
-0.06296414136886597,
0.006569091696292162,
0.014841618947684765,
0.04436229541897774,
-0.007685184478759766,
-0.06757906079292297,
0.03816100209951401,
-0.05109... | 0.169252 |
//!!NODE\_ROOT [."topic"] [[ip-opt,ip-opt.title]] = Optimizing IP Address Utilization :imagesdir: images/networking/ :info\_doctype: section TIP: https://aws-experience.com/emea/smb/events/series/get-hands-on-with-amazon-eks?trk=4a9b4147-2490-4c63-bc9f-f8a84b122c8c≻\_channel=el[Explore] best practices through Amazon EK... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.025898389518260956,
0.026470663025975227,
0.0336274616420269,
0.018433917313814163,
0.08375034481287003,
-0.0014747369568794966,
0.005456765182316303,
-0.03956461325287819,
0.0710752084851265,
0.06768331676721573,
-0.02094556763768196,
0.0017278242157772183,
0.030175210908055305,
-0.0630... | 0.138388 |
deployments on EKS. For detailed information please see the xref:ipv6[Running IPv6 EKS Clusters] section and for hands-on experience please see the https://catalog.workshops.aws/ipv6-on-aws/en-US/lab-6[Understanding IPv6 on Amazon EKS] section of the https://catalog.workshops.aws/ipv6-on-aws/en-US[Get hands-on with IPv... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.02730454131960869,
0.07019861787557602,
0.010691407136619091,
0.013256397098302841,
0.013598307967185974,
0.009756564162671566,
-0.07055915147066116,
-0.06476791203022003,
0.022203460335731506,
0.0551014170050621,
-0.046665649861097336,
-0.012929899618029594,
-0.05012587457895279,
-0.070... | 0.137943 |
the current workloads can keep running on the same subnets and Amazon Elastic Kubernetes Service (Amazon EKS) can now schedule additional pods on the new "usable subnet(s)". If your cluster's current subnets are running out of IP addresses, you can simply add additional subnets to your Amazon EKS cluster as follows: . ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
-0.006925197318196297,
-0.04014681652188301,
0.01592252030968666,
0.04899168759584427,
0.04670698940753937,
0.04470781981945038,
-0.03979410231113434,
-0.09805642068386078,
0.07886526733636856,
0.05760842561721802,
-0.08343447744846344,
-0.014528890140354633,
0.011469502933323383,
-0.03608... | 0.123338 |
maximum number of ENIs the cluster can support \* number of ENIs already allocated \* number of IP addresses currently assigned to Pods \* total and maximum number of IP address available You can also set https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html[CloudWatch alarms] to get n... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ip-optimization-strategies.adoc | mainline | aws-eks-best-practices | [
0.018635878339409828,
-0.04145076870918274,
0.026262829080224037,
0.013035590760409832,
0.07541164755821228,
-0.0013476156163960695,
0.007128990720957518,
-0.07527054846286774,
0.06778718531131744,
0.058827903121709824,
-0.09169072657823563,
-0.03971070796251297,
0.04270944744348526,
-0.07... | 0.118284 |
//!!NODE\_ROOT [."topic"] [[prefix-mode-win,prefix-mode-win.title]] = Prefix Mode for Windows :info\_doctype: section :imagesdir: images/networking/ In Amazon EKS, each Pod that runs on a Windows host is assigned a secondary IP address by the https://github.com/aws/amazon-vpc-resource-controller-k8s[VPC resource contro... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.03653370216488838,
0.0006271180463954806,
-0.03258715942502022,
0.02091149054467678,
0.04311380535364151,
0.009587284177541733,
-0.008869444951415062,
-0.028978930786252022,
0.06898995488882065,
0.06121009588241577,
-0.010736322030425072,
-0.02874772809445858,
0.046918999403715134,
-0.01... | 0.136829 |
== Recommendations === Use Prefix Delegation when Use prefix delegation if you are experiencing Pod density issues on the worker nodes. To avoid errors, we recommend examining the subnets for contiguous block of addresses for /28 prefix before migrating to prefix mode. Please refer "`https://docs.aws.amazon.com/vpc/lat... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.030525339767336845,
-0.005040237680077553,
0.028070470318198204,
0.04417473450303078,
0.011837865225970745,
-0.008842515759170055,
-0.02865077741444111,
-0.010754435323178768,
-0.040934208780527115,
0.05091472342610359,
-0.046115703880786896,
-0.0340021550655365,
0.027466420084238052,
0.... | 0.007091 |
drain all the existing nodes to safely evict all of your existing Pods. To prevent service disruptions, we suggest implementing https://kubernetes.io/docs/tasks/run-application/configure-pdb[Pod Disruption Budgets] on your production clusters for critical workloads. \* After you confirm the Pods are running, you can de... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/prefix-mode_windows.adoc | mainline | aws-eks-best-practices | [
0.04049430415034294,
0.02045491151511669,
0.0955609381198883,
0.01145510096102953,
0.032825544476509094,
0.006985807791352272,
-0.06150679662823677,
-0.09664760529994965,
0.051620304584503174,
0.10108117759227753,
-0.011159111745655537,
-0.05478375032544136,
0.009683936834335327,
-0.074641... | 0.106955 |
//!!NODE\_ROOT [."topic"] [[subnets,subnets.title]] = VPC and Subnet Considerations :info\_doctype: section :info\_title: VPC and Subnet Considerations :info\_abstract: VPC and Subnet Considerations :info\_titleabbrev: VPC and Subnets Considerations :imagesdir: images/networking/ [abstract] -- VPC and Subnet Considera... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
-0.04774010181427002,
-0.0025118226185441017,
-0.020364219322800636,
0.04204126074910164,
0.03796975314617157,
0.03948367387056351,
-0.016030671074986458,
-0.016939466819167137,
0.05478115752339363,
0.028033876791596413,
-0.04663975536823273,
-0.03429434448480606,
0.023911552503705025,
-0.... | 0.10191 |
public IP address and a route to an internet gateway or a route to a NAT gateway where they can use the public IP address of the NAT gateway. ==== Public and Private Endpoint When both the public and private endpoints are enabled, Kubernetes API requests from within the VPC communicate to the control plane via the X-EN... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.024837078526616096,
0.013430011458694935,
-0.04511985927820206,
0.03067079745233059,
0.0027118392754346132,
0.06942207366228104,
-0.0071302754804492,
-0.03739548847079277,
0.09100644290447235,
0.07246092706918716,
-0.025884006172418594,
-0.07010819017887115,
0.010778280906379223,
-0.0752... | 0.138352 |
public or a private subnet. Whether a subnet is public or private refers to whether traffic within the subnet is routed through an https://docs.aws.amazon.com/vpc/latest/userguide/VPC\_Internet\_Gateway.html[internet gateway]. Public subnets have a route table entry to the internet through the internet gateway, but pri... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.021371349692344666,
-0.039476606994867325,
-0.06167566776275635,
0.031794846057891846,
0.09045218676328659,
0.010170705616474152,
0.03562884405255318,
-0.047260817140340805,
0.07431921362876892,
0.0636480301618576,
-0.02181580848991871,
0.01638220064342022,
0.0036918881814926863,
-0.0992... | 0.077014 |
are the service provider and would want to share your Kubernetes service and ingress (either ALB or NLB) with your customer VPC in separate accounts. [[subnets-multiple-accounts, subnets-multiple-accounts.title]] === Sharing VPC across multiple accounts Many enterprises adopted shared Amazon VPCs as a means to streamli... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
-0.007116883993148804,
-0.024787133559584618,
-0.021970776841044426,
-0.009913560003042221,
0.007142726331949234,
0.06818916648626328,
0.029877033084630966,
-0.022731756791472435,
0.13210801780223846,
0.018454790115356445,
-0.064167320728302,
-0.03462032601237297,
0.07159995287656784,
-0.0... | 0.15833 |
or NLB) to route traffic to k8s pods either in application or central networking accounts. Refer to https://aws.amazon.com/blogs/containers/expose-amazon-eks-pods-through-cross-account-load-balancer/[Expose Amazon EKS Pods Through Cross-Account Load Balancer] walkthrough for detailed instructions on deploying the ELB r... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.0025934658478945494,
-0.01732971891760826,
-0.026483697816729546,
0.0031645535491406918,
-0.0071267480961978436,
0.03734355419874191,
0.01924147829413414,
-0.0029582043644040823,
0.056193672120571136,
0.07094135880470276,
-0.06208061799407005,
-0.10095888376235962,
0.05560166761279106,
-... | 0.150782 |
route table of a public subnet contains a route to an internet gateway . Pods are able to interact with the Internet via a NAT gateway. Private subnets are supported by https://docs.aws.amazon.com/vpc/latest/userguide/egress-only-internet-gateway.html[egress-only internet gateways] in the IPv6 environment (EIGW). Insta... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/subnets.adoc | mainline | aws-eks-best-practices | [
0.029239481315016747,
-0.005375977139919996,
0.00941329076886177,
0.009776851162314415,
-0.010530803352594376,
0.04790545627474785,
0.03589532524347305,
-0.013025723397731781,
0.05797277018427849,
0.05603374168276787,
-0.06363934278488159,
-0.018795764073729515,
-0.030576689168810844,
-0.0... | 0.144891 |
//!!NODE\_ROOT [."topic"] [[ipv6,ipv6.title]] = IPv6 :info\_doctype: section :info\_title: Running IPv6 EKS Clusters :info\_abstract: Running IPv6 EKS Clusters :info\_titleabbrev: Running IPv6 Clusters :imagesdir: images/networking/ [abstract] -- Running IPv6 EKS Clusters -- EKS in IPv6 mode solves the IPv4 exhaustion ... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.009854000993072987,
0.03191103786230087,
0.04566793143749237,
0.002851727418601513,
0.0297816451638937,
0.03846510499715805,
-0.10465656965970993,
-0.046816736459732056,
0.047180432826280594,
0.018743377178907394,
-0.01632351242005825,
0.016811642795801163,
-0.044867247343063354,
-0.051... | 0.136122 |
but Pod density (Resources wise). IPv6 prefix assignment only occurs at the EKS worker-node bootstrap time. This behaviour is known to mitigate scenarios where high Pod churn EKS/IPv4 clusters are often delayed in Pod scheduling due to throttled API calls generated by the VPC CNI plug-in (ipamd) aimed to allocate Priva... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.04288453236222267,
0.03129911422729492,
0.04769333824515343,
0.03910861536860466,
0.050298936665058136,
0.013702794909477234,
-0.06022351607680321,
-0.13481485843658447,
0.06794228404760361,
0.06378525495529175,
-0.019804099574685097,
-0.004482698626816273,
-0.026568017899990082,
-0.060... | 0.100333 |
assigned during EKS cluster creation stage and cannot be modified. The following diagram depict the Pod to Kubernetes Service flow: image::ipv6\_Pod-to-service-ipv6.png[EKS/IPv6, IPv6 Pod to IPv6 k8s service (ClusterIP ULA) flow] Services are exposed to the internet using an AWS load balancer. The load balancer receive... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.013114800676703453,
0.037538908421993256,
0.008284462615847588,
0.003931770101189613,
-0.03899434208869934,
0.03527144342660904,
-0.03094640001654625,
-0.06993918120861053,
0.08845215290784836,
0.05730760097503662,
-0.04802129045128822,
-0.039928365498781204,
-0.03518875315785408,
-0.07... | 0.198982 |
available IPv4 and IPv6 addresses. It is recommended to size your dual-stack subnets/VPC CIDRs for future growth. You will not be able to schedule new Fargate Pods if the underlying subnet does not contain an available IPv4 address, irrespective of IPv6 available addresses. === Deploy the AWS Load Balancer Controller (... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipv6.adoc | mainline | aws-eks-best-practices | [
-0.01701653189957142,
-0.04766250401735306,
0.013832276687026024,
-0.008930615149438381,
-0.009544450789690018,
0.039105337113142014,
-0.1119854599237442,
-0.05345189943909645,
0.0761583000421524,
0.020367147400975227,
-0.057536374777555466,
-0.05438687652349472,
-0.08039822429418564,
-0.1... | 0.013041 |
//!!NODE\_ROOT [[networking,networking.title]] = Amazon EKS Best Practices Guide for Networking :doctype: book :sectnums: :toc: left :icons: font :experimental: :idprefix: :idseparator: - :sourcedir: . :info\_doctype: chapter :info\_title: Best Practices for Networking :info\_abstract: Best Practices for Networking :in... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.011001684702932835,
-0.0033959627617150545,
0.02214837074279785,
0.02461279183626175,
0.023900093510746956,
0.06318174302577972,
-0.013158459216356277,
-0.03304392471909523,
0.03689371794462204,
0.06671321392059326,
-0.023013034835457802,
0.034718483686447144,
0.007244536653161049,
-0.0... | 0.22456 |
EKS clusters. VPC CNI add-on is installed by default when you provision EKS clusters. VPC CNI runs on Kubernetes worker nodes. The VPC CNI add-on consists of the CNI binary and the IP Address Management (ipamd) plugin. The CNI assigns an IP address from the VPC network to a Pod. The ipamd manages AWS Elastic Networking... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.05338781327009201,
-0.05292189121246338,
-0.02943030558526516,
0.00029378646286204457,
0.036172691732645035,
0.045068610459566116,
-0.025150399655103683,
-0.07507116347551346,
0.06801372021436691,
0.0728420540690422,
-0.011060182005167007,
-0.05256092548370361,
0.01760784164071083,
-0.0... | 0.167326 |
EKS has prioritized IPv6-only Pods over dual-stack Pods. That is, Pods may be able to access IPv4 resources, but they are not assigned an IPv4 address from VPC CIDR range. The VPC CNI assigns IPv6 addresses to Pods from the AWS managed VPC IPv6 CIDR block. == Subnet Calculator This project includes a https://github.com... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/index.adoc | mainline | aws-eks-best-practices | [
-0.019309328868985176,
0.016219738870859146,
0.030842216685414314,
0.022932222113013268,
0.008841325528919697,
0.01934957131743431,
-0.07308357208967209,
-0.0754711702466011,
0.06393459439277649,
0.03033248335123062,
-0.03211866319179535,
-0.06461141258478165,
0.004680887795984745,
-0.0483... | 0.093597 |
[."topic"] [#ipvs] = Running kube-proxy in IPVS Mode :info\_doctype: section EKS in IP Virtual Server (IPVS) mode solves the https://docs.aws.amazon.com/eks/latest/best-practices/control-plane.html#reliability\_cprunning\_large\_clusters[network latency issue] often seen when running large clusters with over 1,000 serv... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipvs.adoc | mainline | aws-eks-best-practices | [
0.04976475611329079,
0.017557429149746895,
0.018702859058976173,
0.030742421746253967,
0.0011166490148752928,
-0.0354592464864254,
-0.014685073867440224,
-0.0639452338218689,
0.04868713393807411,
0.04911211133003235,
-0.06648172438144684,
-0.006718411576002836,
-0.007858110591769218,
-0.08... | 0.071781 |
making these changes during initial EKS cluster creation to minimize impacts. ==== You can issue an AWS CLI command to enable IPVS by updating the `kube-proxy` EKS Add-on. [,bash] ---- aws eks update-addon --cluster-name $CLUSTER\_NAME --addon-name kube-proxy \ --configuration-values '{"ipvs": {"scheduler": "rr"}, "mod... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/ipvs.adoc | mainline | aws-eks-best-practices | [
-0.0244174562394619,
0.03872913867235184,
0.04251165688037872,
0.03165319561958313,
-0.05903692543506622,
0.017865166068077087,
-0.04310326650738716,
-0.05079841986298561,
0.07531317323446274,
0.07802587747573853,
-0.07490437477827072,
-0.06075286865234375,
0.020629392936825752,
-0.0538470... | 0.059741 |
//!!NODE\_ROOT [."topic"] = Monitoring EKS workloads for Network performance issues :info\_doctype: section :imagesdir: images/networking/ :info\_titleabbrev: Monitoring for Network performance issues == Monitoring CoreDNS traffic for DNS throttling issues Running DNS intensive workloads can sometimes experience interm... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.012134058400988579,
0.012074415571987629,
0.07204220443964005,
-0.007514874916523695,
-0.0506143793463707,
-0.037121713161468506,
-0.03651566430926323,
-0.03325258195400238,
0.07188165932893753,
0.05994865670800209,
-0.05260549858212471,
-0.039160002022981644,
0.016977347433567047,
-0.0... | 0.165382 |
new connections could not be established. == Other important Network performance metrics Other important network performance metrics include: `bw\_in\_allowance\_exceeded` (ideal value of the metric should be zero) is the number of packets queued and/or dropped because the inbound aggregate bandwidth exceeded the maxim... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.02350492589175701,
-0.03878980129957199,
-0.004291980527341366,
0.03860778734087944,
0.003257608041167259,
-0.025116397067904472,
0.027232833206653595,
-0.03432096913456917,
0.07995714992284775,
0.08718075603246689,
-0.04252013564109802,
-0.04230263829231262,
0.032912228256464005,
-0.00... | 0.026339 |
the metrics discussed so far. We will use the https://github.com/aws-controllers-k8s/prometheusservice-controller[ACK Controller for Amazon Managed Service for Prometheus] to provision the alerting and recording rules. Let's deploy the ACL controller for the Amazon Managed Service for Prometheus service: ---- export SE... | https://github.com/aws/aws-eks-best-practices/blob/mainline//latest/bpg/networking/monitoring.adoc | mainline | aws-eks-best-practices | [
-0.1004151850938797,
0.041338350623846054,
-0.07876280695199966,
0.0077569084241986275,
0.04050397872924805,
-0.085171639919281,
0.006234972737729549,
-0.012927748262882233,
0.06918957084417343,
0.04618752375245094,
0.015372399240732193,
-0.06618372350931168,
0.03831776976585388,
-0.021625... | 0.112842 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.