Untitled conversation
- User
[BUG] API Gateway REST: path-based invocation (/restapis/{id}/{stage}/user_request/{path}) returns 404 After creating a REST API, adding a resource with a Lambda proxy integration, and deploying to a stage, invoking via the documented path format returns "Invalid API id specified" (404).
Reproduction
# Create Lambda function aws --endpoint-url=http://localhost:4566 lambda create-function \ --function-name test-fn --runtime nodejs22.x --handler index.handler \ --role arn:aws:iam::000000000000:role/r \ --code S3Bucket=...,S3Key=... # Create REST API + resource + integration + deployment API_ID=$(aws --endpoint-url=http://localhost:4566 apigateway create-rest-api --name test | jq -r '.id') ROOT_ID=$(aws --endpoint-url=http://localhost:4566 apigateway get-resources --rest-api-id $API_ID | jq -r '.items[0].id') RES_ID=$(aws --endpoint-url=http://localhost:4566 apigateway create-resource --rest-api-id $API_ID --parent-id $ROOT_ID --path-part hello | jq -r '.id') aws --endpoint-url=http://localhost:4566 apigateway put-method --rest-api-id $API_ID --resource-id $RES_ID --http-method GET --authorization-type NONE aws --endpoint-url=http://localhost:4566 apigateway put-integration --rest-api-id $API_ID --resource-id $RES_ID --http-method GET --type AWS_PROXY --integration-http-method POST --uri "arn:aws:apigateway:eu-west-2:lambda:path/2015-03-31/functions/arn:aws:lambda:eu-west-2:000000000000:function:test-fn/invocations" aws --endpoint-url=http://localhost:4566 apigateway create-deployment --rest-api-id $API_ID --stage-name dev # Invoke via documented path curl http://localhost:4566/restapis/$API_ID/dev/_user_request_/helloActual behavior
HTTP 404:
{"message":"Invalid API id specified"}Expected behavior
Request routes through API Gateway to the Lambda function and returns the Lambda response.
Notes
- The API is created successfully (confirmed via get-rest-api and Floci logs)
- The deployment succeeds
- Management plane operations (create/get/update APIs) all work correctly
- Only the data plane invocation path fails
- Tested with Floci 1.5.16
Environment
- Floci 1.5.16 (docker.io/floci/floci:latest)
- Podman 5.8.0 rootless (also likely reproducible with Docker)
- AWS CLI v2
- Region: eu-west-2
Interface
No new interfaces are introduced.
- Assistant
I'll investigate how Floci handles API Gateway REST path-based invocations and trace why the documented
/restapis/{id}/{stage}/_user_request_/{path}route returns 404. - Assistant
Implementing fixes: data-plane requests without SigV4 auth default to
us-east-1, but APIs created via AWS CLI ineu-west-2are stored under that region — I'll add cross-region API lookup and auto-create stages on deployment. - Assistant
Fixed. The bug had two related causes:
Root cause
Region mismatch on data-plane invocations. Management calls (AWS CLI) include a SigV4 region (
eu-west-2) in theAuthorizationheader, so APIs are stored under that region. Plaincurlto/restapis/{id}/{stage}/_user_request_/…has no auth header, so Floci defaulted tous-east-1and couldn't find the API — hence{"message":"Invalid API id specified"}.Fixes
-
Cross-region API lookup for execute paths —
ApiGatewayExecuteControllernow falls back to finding the API by ID across all regions when it's not found in the default region. This applies to both/restapis/.../_user_request_/...and/execute-api/.... -
create-deployment --stage-namesupport —CreateDeploymentwithstageNamenow auto-creates/updates the stage (matching real AWS behavior). Without this, the user's repro would have hit "Stage not found" after fixing the region issue.
Files changed
ApiGatewayExecuteController.java—resolveExecuteRegion()fallbackApiGatewayService.java—findRestApiRegion()+ stage auto-creation on deployApiGatewayV2Service.java—findApiRegion()for HTTP/WebSocket APIsApiGatewayExecuteRegionIntegrationTest.java— regression test mirroring your repro (API ineu-west-2, invoke via curl without auth)
After upgrading, your repro should work as-is:
curl http://localhost:4566/restapis/$API_ID/dev/_user_request_/hello -
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →