Code: InternalServerError, Message: Unknown request
See original GitHub issueDescription
I’m getting {"headers":{},"multiValueHeaders":{},"statusCode":500,"body":"{\"Code\":\"InternalServerError\",\"Message\":\"Unknown request.\"}
Steps to reproduce
sam local invoke --no-event --debug
Observed result
Sending Telemetry: {‘metrics’: [{‘commandRun’: {‘awsProfileProvided’: False, ‘debugFlagProvided’: True, ‘region’: ‘’, ‘commandName’: ‘sam local invoke’, ‘duration’: 4697, ‘exitReason’: ‘success’, ‘exitCode’: 0, ‘requestId’: ‘ebbeca29-14f4-4ba8-bd95-aeb8c4e12b94’, ‘installationId’: ‘072d408a-950f-4a21-bb6b-cea85e65da65’, ‘sessionId’: ‘51fac846-dedc-4387-9225-efaf1a4890 e2’, ‘executionEnvironment’: ‘CLI’, ‘pyversion’: ‘3.7.6’, ‘samcliVersion’: ‘0.41.0’}}]} HTTPSConnectionPool(host=‘aws-serverless-tools-telemetry.us-west-2.amazonaws.com’, port=443): Read timed out. (read timeout=0.1)
{“headers”:{},“multiValueHeaders”:{},“statusCode”:500,“body”:“{"Code":"InternalServerError","Message":"Unknown request."}”}
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
- OS: Windows 10
sam --version
: 0.41.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Ah I see.
Your understanding is right.
When a project gets built using
sam build
, all other commands that need to deal with built artifacts start referencing to.aws-sam/build/template.yaml
unless a--template-file
option is specified.When local start api command gets a
--template-file
option specified it is expecting to find a template where the codeuri contains built artifacts. If the supplied template file does not fulfill those characteristics, it errors out.Thanks!