Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add docs section for ECS EC2 monitoring #22784

Merged
merged 6 commits into from
Dec 1, 2020
Merged

Add docs section for ECS EC2 monitoring #22784

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
8fd6bff
Add ECS EC2 documentation
ChrsMark Nov 30, 2020
26884b2
fix docs
ChrsMark Nov 30, 2020
c0ed864
review fix
ChrsMark Nov 30, 2020
848426c
fix list
ChrsMark Dec 1, 2020
2108b29
update
ChrsMark Dec 1, 2020
7ed2b38
split lists
ChrsMark Dec 1, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions metricbeat/docs/modules/awsfargate.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,17 @@ be managed: ECS EC2 and ECS Fargate.
ECS EC2 launches containers that run on EC2 instances. Users have to manage EC2
instances. Pricing depends on the number of EC2 instances running.

One can monitor these containers by deploying Metricbeat on the corresponding EC2 instances with the
Metricbeat Docker module enabled.

In order to achieve this one will need:
--
. to ensure access to these EC2 instances using ssh keys
coupled with EC2 instances (attach ssh keys on cluster creation using `Key pair` option)
. to enable shh access for the instances with the
proper https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html[inbound rules].
--

* *ECS Fargate*

ECS Fargate removes the responsibility of provisioning, configuring, and
Expand Down
11 changes: 11 additions & 0 deletions x-pack/metricbeat/module/awsfargate/_meta/docs.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,17 @@ be managed: ECS EC2 and ECS Fargate.
ECS EC2 launches containers that run on EC2 instances. Users have to manage EC2
instances. Pricing depends on the number of EC2 instances running.

One can monitor these containers by deploying Metricbeat on the corresponding EC2 instances with the
Metricbeat Docker module enabled.

In order to achieve this one will need:
--
. to ensure access to these EC2 instances using ssh keys
coupled with EC2 instances (attach ssh keys on cluster creation using `Key pair` option)
. to enable shh access for the instances with the
proper https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html[inbound rules].
--

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm I think the . messed up some formatting for * *ECS Fargate* section. Please see https://github.com/elastic/beats/blob/c0ed864b9797ed61a04192d34c2c813c56a0ff61/x-pack/metricbeat/module/awsfargate/_meta/docs.asciidoc

* *ECS Fargate*

ECS Fargate removes the responsibility of provisioning, configuring, and
Expand Down