🚷
561
Unauthorized
Example HTTP Response
HTTP Response
HTTP/1.1 561 Unauthorized
Content-Type: application/json
Connection: close
{"message": "Unauthorized"}Common Causes
- Lambda authorizer function returned deny decision
- Invalid or expired authentication token
- Missing required authentication headers
- Lambda authorizer validation logic rejected request
- JWT token validation failed in authorizer
- API key validation failed
- Custom authentication logic in Lambda denied access
- Lambda authorizer timeout or error
Technical Details
What does this mean?
The bouncer said no! Your request made it to AWS's VIP entrance, but the Lambda security guard checked your credentials and decided you're not on the list. Access denied at the door!
Technical Definition
The Lambda authorizer configured for the Application Load Balancer returned an unauthorized response.
Code Snippets
Ready-to-use code for returning this HTTP status in your application:
Node.js
// Express.js
app.get('/example', (req, res) => {
res.status(561).json({
error: 'Unauthorized',
message: 'Your error message here'
});
});
// Native HTTP
const http = require('http');
http.createServer((req, res) => {
res.writeHead(561, { 'Content-Type': 'application/json' });
res.end(JSON.stringify({
error: 'Unauthorized',
message: 'Your error message here'
}));
}).listen(3000);Related Status Codes