Closed tetianakravchenko closed 1 month ago
I have tried to deploy it. I updated the needed variables:
The cloudwatch logs group here:
In my case, the value is arn:aws:logs:eu-north-1:627286350134:log-group:constanca-test-esf:*
And the S3 bucket to the config file:
In my case, it would be: s3://constanca-test-esf/config.yaml
, and this bucket looks like this:
The config.yaml
looks like this:
"inputs":
- "id": "arn:aws:logs:eu-north-1:627286350134:log-group:constanca-test-esf:*"
"outputs":
- "args":
"api_key": "..."
"elasticsearch_url": "https://terraform-8b3bac.es.eu-central-1.aws.cloud.es.io"
"es_datastream_name": "logs-esf.cloudwatch-default"
"type": "elasticsearch"
"type": "cloudwatch-logs"
Then I sent an event in my cloudwatch logs group:
And if I look in Discover I can see it there:
So the issue is related to fact that I was trying to deploy lambda application in the region where it was already deployed.
To sum up - we need to update documentation with the information:
Also to check: Is it possible to install multiple installations per region? maybe it is possible to fix somehow?
Also to check: Is it possible to install multiple installations per region? maybe it is possible to fix somehow?
It's never been possible (with SAR) due to limitations on the AWS side (full context from Andrea: https://github.com/elastic/elastic-serverless-forwarder/issues/150#issuecomment-1206405134 ). Things might have changed since the last time either myself or Andrea looked at this, so it's worth having a look.
I followed documentation - https://www.elastic.co/guide/en/esf/current/aws-deploy-elastic-serverless-forwarder.html#aws-serverless-forwarder-deploy-console
during installation - I've set only
ElasticServerlessForwarderS3ConfigFile
in formats3://<config-bucket-name>/config.yaml
and installation is failing:
View stack event:
cc @constanca-m