megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.

Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

Why am I getting INVALID_LOGIN_ATTEMPT when using aws lambda to call my restlet

edited Feb 25, 2022 1:17AM in Ask A Guru 5 comments

I am trying to diagnose an issue with connecting to a RESTlet from AWS lambda. I think I have the user and token role setup correctly as when I reach out with Postman I get the response I expect. On the other hand, when I try to connect from the lambda function I have created in AWS I get an INVALID_LOGIN_ATTEMPT. I see nothing in my 'login audit trail' to help point me in the direction of what is going wrong.

Attached

is the code I have for creating the OAuth header I use in token based authentication. If anyone can help me figure out what the issue is or how to track down the error I would be eternally grateful.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders