# Not able connect to elastic apm server from AWS lambda **URL:** \ **Category:** APM\ **Tags:** java, aws-lambda\ **Created:** [August 24, 2022, 1:07pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813 "2022-08-24T13:07:20Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [August 24, 2022, 1:07pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/1 "2022-08-24T13:07:20Z")
If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂 TIP 1: select at least one tag that further categorizes your topic. For example `server` for APM Server related questions, `java` for questions regarding the Elastic APM Java agent, or `ui` for questions about the APM App within Kibana. TIP 2: Check out the [troubleshooting guide](https://www.elastic.co/guide/en/apm/get-started/current/troubleshooting.html) first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you. **Kibana version** : **Elasticsearch version** : 7.15.0 **APM Server version** : 7.15.0 **APM Agent language and version** : java and elastic-apm-extension-ver-1-0-2-x86\_64 , elastic-apm-java-ver-1-33-0 **Browser version** : **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: **Fresh install or upgraded from other version?** **Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc. load balancer is there **Description of the problem including expected versus actual behaviour. Please include screenshots (if relevant)**: not getting hit to elastic apm from aws lambda , added environment variables as well |ELASTIC\_APM\_LAMBDA\_APM\_SERVER|http://14.142.143.138:8200| |ELASTIC\_APM\_LOG\_LEVEL|TRACE| |ELASTIC\_APM\_SERVICE\_NAME|service\_name| **Steps to reproduce** : 1. 2. 3. **Errors in browser console (if relevant)**: **Provide logs and/or server output (if relevant)**: ---
**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\ **Post date:** [August 24, 2022, 1:20pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/2 "2022-08-24T13:20:48Z")
Hi @Pratiksha_Nagoshe , welcome to the forum ! Could you elaborate a bit on the setup steps that you followed to add the agent layer and lambda extension that are both required on top of the environment variables ? Do you see anything in the lambda standard output when it executes ? If the agent is properly added then you should have a few lines created by the Java agent. ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [August 24, 2022, 5:03pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/3 "2022-08-24T17:03:13Z")
Hello @Sylvain_Juge Added one more env variable : ELASTIC\_APM\_LOG\_LEVEL TRACE I followed this page [Monitoring AWS Lambda Java Functions | APM Java Agent Reference [1.x] | Elastic](https://www.elastic.co/guide/en/apm/agent/java/current/aws-lambda.html) for setup Below are the logs 2022-08-24 16:55:54,749 [main] DEBUG co.elastic.apm.agent.impl.ElasticApmTracer - endTransaction := endTransaction is method to end transaction at co.elastic.apm.agent.impl.ElasticApmTracer.startRootTransaction(ElasticApmTracer.java:171) [elastic-apm-agent.jar:1.33.0] 2022-08-24 16:55:54,748 [main] TRACE co.elastic.apm.agent.impl.ElasticApmTracer - starting transaction at ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [August 25, 2022, 7:40am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/4 "2022-08-25T07:40:08Z")
Hi @Pratiksha_Nagoshe , could you please try with the newest release of the Elastic APM Lambda extension (v 1.1.0): [Release v1.1.0 · elastic/apm-aws-lambda · GitHub](https://github.com/elastic/apm-aws-lambda/releases/tag/v1.1.0) The new version of the extension has an improved logging in case of connection errors to the APM server. Can you also provide the extension logs (which are also logged into the same CloudWatch streams) in DEBUG mode (not only the APM agent logs) so we can see what happens there. Thanks ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [August 25, 2022, 8:21am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/5 "2022-08-25T08:21:41Z")
Hi @alexander.wert , Thanks for reply I updated version of elastic-apm-extension-ver-1-1-0-x86\_64 Please check below logs 2022-08-25 07:59:05,215 [elastic-apm-server-healthcheck] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Type match for instrumentation CreateSpanInstrumentation: (hasSuperType(erasure(is(class java.net.HttpURLConnection))) and not(name(equals(sun.net.www.protocol.https.HttpsURLConnectionImpl)))) matches class sun.net.www.protocol.http.HttpURLConnection 2022-08-25 07:59:05,215 [elastic-apm-server-healthcheck] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Type match for instrumentation CreateSpanInstrumentation: (hasSuperType(erasure(is(class java.net.HttpURLConnection))) and not(name(equals(sun.net.www.protocol.https.HttpsURLConnectionImpl)))) matches class sun.net.www.protocol.http.HttpURLConnection 2022-08-25 07:58:55,537 [main] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Type match for instrumentation ExecutorRunnableInstrumentation: (hasSuperType(erasure(name(equals(java.util.concurrent.Executor)))) and not(name(equals(org.apache.felix.resolver.ResolverImpl$DumbExecutor))) and not(name(contains(jetty))) and not(name(contains(tomcat))) and not(name(contains(jboss))) and not(name(contains(undertow))) and not(name(contains(netty))) and not(name(contains(vertx))) and not(name(startsWith(com.hazelcast))) and not((name(contains($Proxy)) or name(contains($$)) or name(contains($JaxbAccessor)) or name(contains(CGLIB)) or name(contains(EnhancerBy))))) matches class java.util.concurrent.AbstractExecutorService 2022-08-25 07:58:55,537 [main] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Type match for instrumentation ExecutorRunnableInstrumentation: (hasSuperType(erasure(name(equals(java.util.concurrent.Executor)))) and not(name(equals(org.apache.felix.resolver.ResolverImpl$DumbExecutor))) and not(name(contains(jetty))) and not(name(contains(tomcat))) and not(name(contains(jboss))) and not(name(contains(undertow))) and not(name(contains(netty))) and not(name(contains(vertx))) and not(name(startsWith(com.hazelcast))) and not((name(contains($Proxy)) or name(contains($$)) or name(contains($JaxbAccessor)) or name(contains(CGLIB)) or name(contains(EnhancerBy))))) matches class java.util.concurrent.AbstractExecutorService 2022-08-25 07:58:35,016 [main] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Not applying excluded instrumentation co.elastic.apm.agent.vertx.v4.web.WebInstrumentation$ContextImplTracerInstrumentation 2022-08-25 07:59:37,018 [main] DEBUG co.elastic.apm.agent.bci.ElasticApmAgent - Method match for instrumentation ExecutePreparedStatementInstrumentation: ((name(equals(execute)) or name(equals(executeQuery))) and hasParameter(ofSize(0)) and isPublic() and not(isAbstract())) matches public synchronized java.sql.ResultSet com.vertica.jdbc.common.SCallableStatement.executeQuery() throws java.sql.SQLException LOGS Name: apm-lambda-extension State: Subscribed Types: [platform] { "log.level": "warn", "@timestamp": "2022-08-25T07:58:27.639Z", "log.origin": { "file.name": "extension/process\_env.go", "file.line": 110 }, "message": "Could not read ELASTIC\_APM\_DATA\_RECEIVER\_TIMEOUT\_SECONDS, defaulting to 15: strconv.Atoi: parsing "": invalid syntax", "ecs.version": "1.6.0" } { "log.level": "warn", "@timestamp": "2022-08-25T07:58:27.656Z", "log.origin": { "file.name": "extension/process\_env.go", "file.line": 116 }, "message": "Could not read ELASTIC\_APM\_DATA\_FORWARDER\_TIMEOUT\_SECONDS, defaulting to 3: strconv.Atoi: parsing "": invalid syntax", "ecs.version": "1.6.0" } { "log.level": "debug", "@timestamp": "2022-08-25T07:59:23.576Z", "log.origin": { "file.name": "logsapi/event.go", "file.line": 78 }, "message": "Received log event platform.extension", "ecs.version": "1.6.0" } ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [August 25, 2022, 12:03pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/6 "2022-08-25T12:03:26Z")
Hi @Pratiksha_Nagoshe , is this the full logs? I would expect something like this to be logged by the extension: ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/f/af2ca1b75911267166cefcad95bf5269108df46f.png) Or some error log stating that connection to APM server was not successful. ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [August 25, 2022, 4:33pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/7 "2022-08-25T16:33:20Z")
Hey @alexander.wert No, I am not getting such logs ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 2, 2022, 3:11am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/8 "2022-09-02T03:11:30Z")
Hi @alexander.wert and @Sylvain_Juge , Is there any configuration missing ? please help with this is properties file & jar file is required in upload ? is code has to be compiled by specific java version ? Thanks ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [September 2, 2022, 2:15pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/9 "2022-09-02T14:15:31Z")
Hi @Pratiksha_Nagoshe, without more information about your setup it's hard to do further troubleshooting. Can you please confirm that you have done all of the following: 1. You added **BOTH** layers to your function ( **arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-extension-ver-1-1-0-x86\_64:1** AND **arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-java-ver-1-33-0:1** ) of course with the correct AWS region being replaced in the ARNs 2. You configured **ALL** of the following environment variables: - AWS\_LAMBDA\_EXEC\_WRAPPER = /opt/elastic-apm-handler - ELASTIC\_APM\_LAMBDA\_APM\_SERVER = - ELASTIC\_APM\_SECRET\_TOKEN = \ In your description above I see that the environment variable `AWS_LAMBDA_EXEC_WRAPPER` is missing. Is it actually missing or did you just forgot to mention it in the description above? Setting this variable is necessary for the agent to attach to the target application. Could you maybe provide a screenshot (with obfuscated values) of your environment variables configuration and your layer configurations from the AWS Lambda Web console? Thanks! ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 2, 2022, 2:40pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/10 "2022-09-02T14:40:15Z")
@alexander.wert Thanks for reply we added all configuration **arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-extension-ver-1-1-0-x86\_64:1** **arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-java-ver-1-33-0:1** Environment variables are |AWS\_LAMBDA\_EXEC\_WRAPPER|/opt/elastic-apm-handler| |ELASTIC\_APM\_LAMBDA\_APM\_SERVER| |ELASTIC\_APM\_SERVICE\_NAME| we not added token because we remove that from our server I hope this will helpful for you In jar file , we added elastic.properties file and jar as well , is this effecting ? is code has to be compiled by specific java version ? Java 8 on Amazon Linux 1 Waiting for your reply Thanks ---
**Author:** ![alexander.wert](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexander.wert/32/95085_2.png) [@alexander.wert](https://discuss.elastic.co/u/alexander.wert)\ **Post date:** [September 5, 2022, 6:17am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/11 "2022-09-05T06:17:17Z")
Hi @Pratiksha_Nagoshe, I now see what's the problem here: You are running on the _Java 8 Amazon Linux 1 Lambda_ runtime. As [documented here](https://www.elastic.co/guide/en/apm/agent/java/current/aws-lambda.html), this runtime is not supported. Can you try with _Java 8 on Amazon Linux 2_ OR _Java 11 on Amazon Linux 2_ and see if you still see this problem? > In jar file , we added elastic.properties file and jar as well , is this effecting ? > is code has to be compiled by specific java version ? There's no need to add anything to your target JAR, the agent layer will provide everything that is needed. Regarding the Java compile version, the only requirement is that it needs to be Java 8 or higher. ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 5, 2022, 7:58am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/12 "2022-09-05T07:58:52Z")
> [@Pratiksha\_Nagoshe](#): > > **arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-java-ver-1-33-0:1** Hi @alexander.wert , now complied with java 11 but still error { "log.level": "error", "@timestamp": "2022-09-05T07:54:04.083Z", "log.origin": { "file.name": "app/run.go", "file.line": 178 }, "message": "error sending to APM server, skipping: failed to post to APM server: Post "[http://host](http://host):port/intake/v2/events": context deadline exceeded (Client.Timeout exceeded while awaiting headers)", "ecs.version": "1.6.0", "log.origin.stack\_trace": "[github.com/elastic/apm-aws-lambda/app.(\*App).processEvent.func1](http://github.com/elastic/apm-aws-lambda/app.(*App).processEvent.func1)\n\t/var/lib/jenkins/workspace/ibrary\_apm-aws-lambda-mbp\_v1.1.0/src/github.com/elastic/apm-aws-lambda/app/run.go:178" } Waiting for your reply Thanks ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [September 5, 2022, 11:58am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/13 "2022-09-05T11:58:41Z")
Hi @Pratiksha_Nagoshe , the last message that you shared (`error sending to APM server, skipping: failed to post to APM server: Post "http://host:port/intake/v2/events": context deadline exceeded (Client.Timeout exceeded while awaiting headers)`) might also indicate an issue with your APM Server. Can you check the logs in the APM Server to see if it is running into any issues and/or giving us more information? ---
**Author:** ![axw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/axw/32/28197_2.png) [@axw](https://discuss.elastic.co/u/axw)\ **Post date:** [September 5, 2022, 12:21pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/14 "2022-09-05T12:21:53Z")
@Pratiksha_Nagoshe one other thing you can check: is your APM Server even accessible? Can you use `curl` to check that the server is responding? It may be your APM Server host is firewalled. In your initial post you wrote: > |ELASTIC\_APM\_LAMBDA\_APM\_SERVER|http://14.142.143.138:8200| I can ping that IP, but port 8200 is not open. ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 7, 2022, 7:45am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/15 "2022-09-07T07:45:58Z")
Hi @alexander.wert , @Sylvain_Juge , @simitt , @axw Thanks reply Its working with java 11 dummy aws lambda but with real application its showing following error logs - 2022-09-07T12:42:27.166+0530 ERROR [request] middleware/log\_middleware.go:74 data validation error {"request\_id": "4dde2c43-770f-4ae1-a1d7-646fbf6d7f93", "method": "POST", "URL": "/intake/v2/events", "content\_length": 405, -2022-09-07 07:12:26,876 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Failed to handle event of type TRANSACTION with this error: null "message": "APM server response body: {"accepted":0,"errors":[{"message":"did not recognize object type","document":"{\"metricset\":{\"samples\":{\"faas.coldstart\_duration\":{\"value\":455.7799987792969},\"faas.timeout\":{\"value\":195000},\"system.memory.total\":{\"value\":5.36870912e+08},\"system.memory.actual.free\":{\"value\":4.15236096e+08},\"faas.duration\":{\"value\":14438.7099609375},\"faas.billed\_duration\":{\"value\":14439}},\"timestamp\":1662545939270000,\"faas\":{\"coldstart\":true,\"execution\":\"11a9f891-19ed-4f26-90a9-74ed24b226ce\",\"id\":==========}}}} 2022-09-07T12:42:27.166+0530 ERROR [request] middleware/log\_middleware.go:74 data validation error {"request\_id": "4d-770f-4ae1-a1d7-646fbf6d7f93", "method": "POST", "URL": "/intake/v2/events", "content\_length": 405, "remote\_address": "\*\*\*\*\*", "user-agent": "Go-http-client/1.1", "response\_code": 400, "error": "did not recognize object type [{"metricset":{"samples":{"faas.duration":{"value":65826.90625},"faas.billed\_duration":{"value":65827},"faas.coldstart\_duration":{"value":0},"faas.timeout":{"value":267000},"system.memory.total":{"value":5.36870912e+08},"system.memory.actual.free":{"value":3.60710144e+08}},"timestamp":1662534583442000,"faas":{"coldstart":false,"execution":"5a0f5171-f854-4bbb-bc8b-fb0","id":""}}}]"} Thanks waiting for reply ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [September 7, 2022, 11:14am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/16 "2022-09-07T11:14:35Z")
When setting the log level in the `apm-server` to debug (`logging.level: "debug"`), the server should log the full event body. Please share these log details here (but remove any sensitive information beforehand). It should give us more insights into the data validation error. ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 7, 2022, 11:58am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/17 "2022-09-07T11:58:13Z")
Hi @simitt Thanks for reply please check the logs above I added full logs ---
**Author:** ![axw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/axw/32/28197_2.png) [@axw](https://discuss.elastic.co/u/axw)\ **Post date:** [September 8, 2022, 3:03am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/18 "2022-09-08T03:03:24Z")
@Pratiksha_Nagoshe the APM Server log message does not line up with v7.15.0. Just guessing, but maybe you're actually running v7.5.0? That version does not have support for metrics, and I think lines up with the log message you have supplied. Can you please check which version you're running, and provide the complete `apm-server.log`, with any sensitive data redacted? ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 9, 2022, 7:04am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/19 "2022-09-09T07:04:41Z")
Thanks all for such nice response We changed java version to 11 It worked ---
**Author:** ![Pratiksha\_Nagoshe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pratiksha_nagoshe/32/99920_2.png) [@Pratiksha\_Nagoshe](https://discuss.elastic.co/u/Pratiksha_Nagoshe)\ **Post date:** [September 12, 2022, 1:34pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/20 "2022-09-12T13:34:13Z")
Hi @alexander.wert , @axw , @Sylvain_Juge , @simitt for other lambda we got the error logs following WARN co.elastic.apm.agent.impl.transaction.AbstractSpan - End has already been 2022-09-12 12:52:59,335 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Failed to handle event of type TRANSACTION with this error: null 2022-09-12 12:42:19,172 [main] DEBUG co.elastic.apm.agent.bci.bytebuddy.CustomElementMatchers - Implementation version parsing error: ProtectionDomain (file:/var/task/ ) [Next page](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813.md?page=2)