Skip to content

Commit f1490a2

Browse files
l0k0msl0k0ms
committed
update to be more consistent with AWS doc
1 parent 1760c7c commit f1490a2

File tree

1 file changed

+52
-36
lines changed

1 file changed

+52
-36
lines changed

‎content/en/integrations/amazon_eks_fargate.md

Lines changed: 52 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,16 @@ manifest_version: 1.0
1515
name: amazon_eks_fargate
1616
public_title: Datadog-Amazon EKS on AWS Fargate
1717
version: 1.0
18+
further_reading:
19+
- link: "https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html"
20+
tag: "AWS Documentation"
21+
text: "Getting Started with AWS Fargate on Amazon EKS"
22+
- link: "https://docs.aws.amazon.com/eks/latest/userguide/fargate.html"
23+
tag: "AWS Documentation"
24+
text: "AWS Fargate documentation"
25+
- link: "https://www.datadoghq.com/blog/eks-fargate-monitoring/"
26+
tag: "Blog"
27+
text: "Monitor Amazon EKS on AWS Fargate with Datadog"
1828
---
1929

2030
## Overview
@@ -23,37 +33,35 @@ Amazon EKS on AWS Fargate is a managed Kubernetes service that automates certain
2333

2434
## Setup
2535

26-
These steps cover the setup of the Datadog Agent in a container within Amazon EKS on AWS Fargate where you run the Agent as a sidecar of your application pod with custom RBAC.
36+
These steps cover the setup of the Datadog Agent in a container within Amazon EKS on AWS Fargate. Refer to the [Datadog-Amazon EKS integration documentation][1] if you are not using AWS Fargate.
2737

28-
AWS Fargate nodes are not physical nodes, which means they exclude [host-based system-checks][1], like CPU, memory, etc.
29-
30-
Running the Agent as a sidecar of your application pod with custom RBAC enables these features:
38+
AWS Fargate pods are not physical pod, which means they exclude [host-based system-checks][2], like CPU, memory, etc. In order to collect data from your AWS Fargate pods, you must run the Agent as a sidecar of your application pod with custom RBAC, which enables these features:
3139

3240
* Kubernetes metrics collection from the pod running your application containers and the Agent
33-
* [Autodiscovery][2]
41+
* [Autodiscovery][3]
3442
* Configuration of custom Agent Checks to target containers in the same pod
3543
* APM and DogStatsD for containers in the same pod
3644

37-
### EC2 Node
45+
### EC2 Node
3846

39-
EKS on Fargate allows users to create node groups that use classical EC2 machines, like for the standard EKS setup. This works by running the Agent as an EC2-type workload. The Agent setup is the same as that of the [Kuberenetes Agent setup][3], and all options are available. To deploy the Agent on EC2 nodes, use the [DaemonSet setup for the Datadog Agent][4].
47+
If you don't specify through [AWS Fargate Profile][4] that your pods should run on fargate, your pods can use classical EC2 machines. If it's the case refer to the [Datadog-Amazon EKS integration setup][5] in order to collect data from your them. This works by running the Agent as an EC2-type workload. The Agent setup is the same as that of the [Kuberenetes Agent setup][6], and all options are available. To deploy the Agent on EC2 nodes, use the [DaemonSet setup for the Datadog Agent][7].
4048

4149
### Installation
4250

43-
To get the best observability coverage monitoring workloads in AWS EKS Fargate, set up the Datadog integrations for:
44-
45-
* [Kubernetes][5]
46-
* [AWS][6]
47-
* [EC2][7] (if you are running an EC2 pod)
51+
To get the best observability coverage monitoring workloads in AWS EKS Fargate, install the Datadog integrations for:
4852

53+
* [Kubernetes][8]
54+
* [AWS][9]
55+
* [EKS][10]
56+
* [EC2][11] (if you are running an EC2-type node)
4957

50-
Also, set up integrations for any other AWS services you are running with EKS (for example, [ELB][5]).
58+
Also, set up integrations for any other AWS services you are running with EKS (for example, [ELB][12]).
5159

5260
#### Manual Installation
5361

5462
To install, download the custom Agent image: `datadog/agent:eks-fargate-beta`.
5563

56-
If the Agent is running as a sidecar, it can communicate only with containers on the same pod. Run an Agent for every pod you wish to monitor.
64+
If the Agent is running as a sidecar, it can communicate only with containers on the same pod. Run an Agent for every pod you wish to monitor.
5765

5866
### Configuration
5967

@@ -62,7 +70,7 @@ To collect data from your applications running in AWS EKS Fargate over a Fargate
6270
* [Set up AWS EKS Fargate RBAC rules](#aws-eks-fargate-rbac).
6371
* [Deploy the Agent as a sidecar](#running-the-agent-as-a-side-car).
6472
* Set up Datadog [metrics](#metrics-collection), [events](#events-collection), and [traces](#traces-collection) collection.
65-
73+
6674
#### AWS EKS Fargate RBAC
6775

6876
Use the following Agent RBAC when deploying the Agent as a sidecar in AWS EKS Fargate:
@@ -108,7 +116,7 @@ metadata:
108116
109117
#### Running the Agent as a sidecar
110118
111-
To start collecting data from your pod, deploy the Datadog Agent as a sidecar of your application. This is the minimum configuration required to collect metrics from your application running in the pod:
119+
To start collecting data from your Fargate type pod, deploy the Datadog Agent as a sidecar of your application. This is the minimum configuration required to collect metrics from your application running in the pod:
112120
113121
```yaml
114122
apiVersion: apps/v1
@@ -156,7 +164,7 @@ spec:
156164
cpu: "200m"
157165
```
158166
​
159-
**Note**: Don't forget to replace `<YOUR_DATADOG_API_KEY>` with the [Datadog API key from your organization][8].
167+
**Note**: Don't forget to replace `<YOUR_DATADOG_API_KEY>` with the [Datadog API key from your organization][13].
160168

161169
## Metrics Collection
162170

@@ -289,7 +297,7 @@ spec:
289297

290298
## Traces Collection
291299

292-
Set up the container port `8126` over your Agent container to collect traces from your application container. [Read more about how to set up tracing][9].
300+
Set up the container port `8126` over your Agent container to collect traces from your application container. [Read more about how to set up tracing][14].
293301

294302
​
295303
```yaml
@@ -345,33 +353,41 @@ spec:
345353
cpu: "200m"
346354
```
347355
​
348-
**Note**: Don't forget to replace `<YOUR_DATADOG_API_KEY>` with the [Datadog API key from your organization][8].
356+
**Note**: Don't forget to replace `<YOUR_DATADOG_API_KEY>` with the [Datadog API key from your organization][13].
349357

350358
## Events Collection
351359

352360
To collect events from your AWS EKS Fargate API server, run a Datadog Cluster Agent over an AWS EKS EC2 pod within your Kubernetes cluster:
353361

354-
1. [Setup the Datadog Cluster Agent][10].
355-
2. [Enable Event collection for your Cluster Agent][11].
362+
1. [Setup the Datadog Cluster Agent][15].
363+
2. [Enable Event collection for your Cluster Agent][16].
356364

357365
Optionally, deploy cluster check runners in addition to setting up the Datadog Cluster Agent to enable cluster checks.
358366

359367
**Note**: You can also collect events if you run the Datadog Cluster Agent in a pod in Fargate.
360368

361369
## Troubleshooting
362370

363-
Need help? Contact [Datadog support][12].
364-
365-
366-
[1]: /integrations/system
367-
[2]: /agent/autodiscovery
368-
[3]: /agent/kubernetes
369-
[4]: /agent/kubernetes/daemonset_setup
370-
[5]: /integrations/kubernetes
371-
[6]: /integrations/amazon_web_services
372-
[7]: /integrations/amazon_ec2
373-
[8]: https://app.datadoghq.com/account/settings#api
374-
[9]: /tracing/setup
375-
[10]: /agent/cluster_agent/setup
376-
[11]: /agent/cluster_agent/event_collection
377-
[12]: https://docs.datadoghq.com/help
371+
Need help? Contact [Datadog support][17].
372+
373+
## Further Reading
374+
375+
{{< partial name="whats-next/whats-next.html" >}}
376+
377+
[1]: /integrations/amazon_eks/
378+
[2]: /integrations/system
379+
[3]: /agent/autodiscovery
380+
[4]: https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html
381+
[5]: /integrations/amazon_eks/#setup
382+
[6]: /agent/kubernetes
383+
[7]: /agent/kubernetes/daemonset_setup
384+
[8]: https://app.datadoghq.com/account/settings#integrations/kubernetes
385+
[9]: https://app.datadoghq.com/account/settings#integrations/amazon-web-services
386+
[10]: https://app.datadoghq.com/account/settings#integrations/amazon-eks
387+
[11]: https://app.datadoghq.com/account/settings#integrations/amazon-ec2
388+
[12]: /integrations/kubernetes
389+
[13]: https://app.datadoghq.com/account/settings#api
390+
[14]: /tracing/setup
391+
[15]: /agent/cluster_agent/setup
392+
[16]: /agent/cluster_agent/event_collection
393+
[17]: https://docs.datadoghq.com/help

0 commit comments

Comments
 (0)