---
title: "Comment by deepak bajaj on \"SMS OTP Authentication Using AWS Backend\" | Hashnode"
description: "This is not working, My lambda always give the below response { &quot;statusCode&quot;: 200, &quot;body&quot;: &quot;{\\&quot;response\\&quot;: \\&quot;NO\\&quot;}&"
url: "https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7/comment/607aaa85c99e200d08f7aa46"
---

[Discussion](https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7)

Comment [SMS OTP Authentication Using AWS Backend](https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7)

[deepak bajaj](https://hashnode.com/@alwindeep)

[Apr 17, 2021](https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7/comment/607aaa85c99e200d08f7aa46)

This is not working, My lambda always give the below response

{ "statusCode": 200, "body": "{\\"response\\": \\"NO\\"}" }

Kindly help.

Not working with UI as well

[Vikas Solegaonkar](https://hashnode.com/@solegaonkar)

[Apr 19, 2021](https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7/comment/607aaa85c99e200d08f7aa46#reply-607ce248eb2bd30d2d2282f3)

You can check your IAM role - if it has the required permissions. If it is good, you can try to remove the exception suppression in the lambda code. That will show you exact line where the error occurs - so that you can fix it.

[Yajat Gupta](https://hashnode.com/@yajat)

[Jun 17, 2021](https://hashnode.com/posts/sms-otp-authentication-using-aws-backend/5fbde4fbdaba2d288c551dc7/comment/607aaa85c99e200d08f7aa46#reply-60cb781f2f8ab52fde40ba47)

same issue with me. Were you able to fix it?
