# Not able connect to elastic apm server from AWS lambda

**URL:** <https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813>\
**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:** 5\
**Page:** 2

<div class="post-metadata">

**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 12, 2022, 2:28pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/21 "2022-09-12T14:28:41Z")

</div>

@Pratiksha_Nagoshe which version of the APM Server are you running? If you are still on `7.x`, could you upgrade APM Server to the latest `7.17` version?

---

<div class="post-metadata">

**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, 2:31pm UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/22 "2022-09-12T14:31:23Z")

</div>

@simitt , no I could not upgrade the server , current is 7.15  
Thanks

---

<div class="post-metadata">

**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 13, 2022, 7:58am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/23 "2022-09-13T07:58:08Z")

</div>

As pointed out by my colleague in a former [comment](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/18), the shared APM Server log messages do not line up with how an APM Server of version `7.15` would issue log messages. The logs and the error suggest to be collected from an older version of APM Server. This would also explain why you are seeing this specific error, as older APM Servers are not supporting metrics.  
Please double check your server version and the configuration in your lambda app to which APM Server it is trying to connect.

---

<div class="post-metadata">

**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 14, 2022, 5:09am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/24 "2022-09-14T05:09:43Z")

</div>

@simitt Thank you for reply  
we got solution , its serialisation issue  
its sorted

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 5, 2022, 1:10am UTC](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813/25 "2022-10-05T01:10:40Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.

[Previous page](https://discuss.elastic.co/t/not-able-connect-to-elastic-apm-server-from-aws-lambda/312813.md?page=1)