2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
I figured it out. From the "Resources" page of your ApiGateway, you need to click "Actions" -> "Deploy API" for any api changes that you make, even if they appear to persist in the UI. The issue was that my api changes were undeployed, and there is no visual indication that I have pending undeployed changes. Deploying the api resolves the issue.
beantwortet vor 2 Jahren
0
Related issue with the same problem: https://repost.aws/questions/QUxCioMpmpQICGq1H-kleEEw/make-api-gateway-resource-point-to-lambda-alias
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
It would be helpful to see the actual
uri
that is returned for the integration, using get-integration@Farski
And here's a CloudWatch entry for the ApiGateway api:
You can see that the alias is not included in the request.