1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Please check if any of the limitations mentioned in this document https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-known-issues.html under the section "API Gateway supports most of the OpenAPI 2.0 specification and the OpenAPI 3.0 specification, with the following exceptions:" apply to you.
Is your imported API working correctly when using REST API as opposed to HTTP API. In that case, using REST API is probably a better option for you. You can use this document https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-vs-rest.html to see the differences between the two and make an informed decision.
Contenuto pertinente
- AWS UFFICIALEAggiornata 5 mesi fa
- AWS UFFICIALEAggiornata 8 mesi fa
Those limitations don't seem to apply. Also that document only talks about REST and WebSocket APIs, and REST works fine so I'll probably use that for now. But the HTTP API seems to be more fit for my application.
Yes if REST is working for you, please go ahead with REST. Functionally there is very little that can be done with HTTP that cannot be done with REST. But interested to know why you think HTTP API is a better fit for your application.