2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
0
Related issue with the same problem: https://repost.aws/questions/QUxCioMpmpQICGq1H-kleEEw/make-api-gateway-resource-point-to-lambda-alias
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
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.