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.

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

[Documentation] Add reference to ESF terraform #730

Merged
merged 3 commits into from
Jul 2, 2024

Conversation

constanca-m
Copy link
Contributor

@constanca-m constanca-m commented Jun 13, 2024

WARNING: Do not merge before ESF terraform is public.

What does this PR do?

We need to add a reference to ESF terraform repository for it to go public.

How to test this PR locally

To see the documents, run the command from elastic docs for a local repo:

<local-path-to-elastic-docs-repo>/docs/build_docs --doc <local-path-to-elastic-serverless-forwarder-repo>/docs/en/index.asciidoc --open

Related issues

Relates to elastic/terraform-elastic-esf#8.

Signed-off-by: constanca <[email protected]>
Signed-off-by: constanca <[email protected]>
@constanca-m constanca-m self-assigned this Jun 13, 2024
@@ -19,8 +19,7 @@ To deploy Elastic Serverless Forwarder, you have to:
[discrete]
[[aws-serverless-forwarder-deploy-prereq]]
== Prerequisites
This documentation assumes you have some familiarity with {aws} services and you have correctly created and configured the necessary {aws} objects. For example, if you want to use an Amazon S3 (via SQS event notifications) input then you must ensure that you have enabled AWS VPC flow logs to be sent to that bucket, and created an SQS queue to receive those logs. For more information, refer to the relevant https://docs.aws.amazon.com/[{aws} docs].
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am removing this because it does not read right. There are other forms to get logs in S3.

@@ -180,6 +179,8 @@ inputs:
ssl_assert_fingerprint: "22:F7:FB:84:1D:43:3E:E7:BB:F9:72:F3:D8:97:AD:7C:86:E3:08:42" #optional
----

WARNING: All versions up to 1.14.0 (included) only allow one output per type. So if the `output.type` chosen by a user is `elasticsearch`, then the user can only configure one output for it.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Adding this warning. See related issue: #721.

[[aws-serverless-forwarder-deploy-terraform]]
== Deploy Elastic Serverless Forwarder from Terraform

The terraform files to deploy ESF can be found in https://github.com/elastic/terraform-elastic-esf[`esf-terraform` repository]. There are two requirements to deploy these files: https://curl.se/download.html[curl] and https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli[terraform]. Refer to the https://github.com/elastic/terraform-elastic-esf/blob/main/README.md[README file] to learn how to use it.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am leaving this section purposely short. There is documentation in the README file and I want to avoid having to maintain two different documents for the same thing.

In the future, I would suggest creating a tutorial documentation on how to get logs similarly to ESF tutorial.

@@ -303,7 +311,7 @@ There are several deployment methods available via the {aws} Serverless Applicat

* <<aws-serverless-forwarder-deploy-console>>
* <<aws-serverless-forwarder-deploy-cloudformation>>
* <<aws-serverless-forwarder-deploy-terraform>>
* <<aws-serverless-forwarder-deploy-sar-terraform>>

Choose a reason for hiding this comment

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

@constanca-m Double checking that this renaming has been done to avoid confusion with the "real" Terraform option we are adding ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, but mainly because build_docs fails with two IDs that are the same:

INFO:build_docs:
INFO:build_docs:asciidoctor: WARNING: aws-deploy-elastic-serverless-forwarder.asciidoc: line 401: id assigned to block already in use: aws-serverless-forwarder-deploy-terraform

axw
axw previously approved these changes Jun 13, 2024
Copy link
Member

@axw axw left a comment

Choose a reason for hiding this comment

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

LGTM, just one minor suggestion

docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc Outdated Show resolved Hide resolved
@constanca-m constanca-m merged commit 7025566 into elastic:main Jul 2, 2024
4 checks passed
@constanca-m constanca-m deleted the add-tf-docs branch July 2, 2024 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants