3 ms·

Do you have any feedback that I can pass along to the team? Post it here or email it to me (email in profile).

• hobofan 10y ago
  I'm in the same boat. If I would have to name one thing, it's that the configuration of API Gateway via the UI is unbearable if you have a nontrivial amount of routes (> 3). I need to configure Authorization, Error code mappings etc. for every route, although they are exactly the same. If there would be per-gateway defaults I can set with per-route overrides, that would cut down the setup time by 95%, which is the main thing holding me back from using API Gateway for projects that would suit it. Right now the only option I seem to have is using a tool like Terraform to automate it, which is a pain to adopt if you already have a running API Gateway.
  • aaimnr 10y ago
    You could also write a quick script using their REST API, although that's a bit cumbersome (lot of IDs that need to be passed around after creation of each resource). Still better than manual clicking in my opinion. http://docs.aws.amazon.com/apigateway/api-reference/resource/ http://docs.aws.amazon.com/apigateway/api-reference/resource...
  • imglorp 10y ago
    You might want to play with https://github.com/awslabs/chalice https://github.com/awslabs/chalice It gets you to hello lambda (python) in one shot, from the cli. Anything written down in one repo is going to be far more undertstandable than piles of hidden behaviors and obscure error messages. I think there's a new one on their blog for node.