Is there any example that runs on Api Gateway + Ko...

# kotless

[LeoColman]

Is there any example that runs on Api Gateway + Kotless (ktor)?

[TanVD]

Yep, here is few applications: https://github.com/JetBrains/kotless/tree/master/examples/ktor

[TanVD]

Both of them runs: <http://ktor.site.kotless.io|ktor.site.kotless.io> and <http://ktor.short.kotless.io|ktor.short.kotless.io>

[LeoColman]

None of them explictly use api gateway tho, right?

[TanVD]

Kotless would not use API Gateway explicitly, it will generate it from code

[TanVD]

You can use generate task and see APIGateway resources in generated Terraform code 🙂

[TanVD]

So, Kotless always use APIGateway (in case of AWS), but it is not stated explicitly

[LeoColman]

The APIs work if I'm using that randomized string for the api, but not for a custom domain

[LeoColman]

I guess this is api gateway's fault, but idk how to solve this with kotless

[TanVD]

Hm, where do you use randomized string? You mean as name of Rest API?

[TanVD]

BTW, note that to use custom domain you need certificate in Virgina

[LeoColman]

For the path /hello/world
Api gateway creates
API endpoint: https://XXXXXXXYYYYYY.execute-api.us-east-1.amazonaws.com/1/hello/world

[LeoColman]

Calling that directly works, but when adding it to a custom api gateway endpoiint doesn't

[LeoColman]

https://my.customdomain/hello/world -> 404

[LeoColman]

When adding the custom domain to API gateway itself

[TanVD]

Hm, do you use Kotless custom domain?

[TanVD]

it has built-in support of DNS records bounded to API Gateway

[LeoColman]

It's bounded to Route53. I'm currently experimenting on AWS free tier, and route53 isn't part of it

[TanVD]

Oh, hm

[LeoColman]

I don't think this is an issue with Kotless. It's probably a problem with AWS itself

[LeoColman]

It adds extra path to the URL, and then Kotless + Ktor can't find it. And it seems there isn't a way to wildcard that extra path

[TanVD]

Well, yeah, probably. Kotless works with DNS-aliased applications in a pretty same fashion it does with anonymous applications. So it should not give 404

[TanVD]

Do you have any errors in cloudwatch log of application?

[LeoColman]

No

[TanVD]

It may be, that custom domain attached that way generates incorrect (from Kotless POV) routes to application

[LeoColman]

Butt it gets called

[TanVD]

Well, you can try to enable info level of logging to see the whole trace of execution

[TanVD]

In that case we would know at least what is going on and what route Kotless see in request

[TanVD]

Oh, hm

[LeoColman]

I did. Api Gateway maps a different endpoint, and I can't get Kotless + Ktor to identify it.
For example https://my.customdomain/1/basepath/hello/world

[LeoColman]

And I can't get that to be wildcarded

[LeoColman]

I can't add it as part of the path either, or else kotless will generate an api with that path as part of it. And this won't be supported again by API Gateway

[TanVD]

Hm, you mean APIGateway adds basepath to application with Custom Domain?

[LeoColman]

yes

[TanVD]

And it does so only for custom domain?

[LeoColman]

Yes

[LeoColman]

https://forums.aws.amazon.com/thread.jspa?threadID=269585

[TanVD]

Have you tried to set empty path during configuration of API?)

[LeoColman]

I think this guy explains it better

[TanVD]

Yep, one moment

[TanVD]

I'll take a look)

[LeoColman]

Have you tried to set empty path during configuration of API?)

I can't, as I'm using Kotless to define multiple APIs

[LeoColman]

And to define multiple apis we need to define the path

[TanVD]

You mean you have Kotless application, that has few parts -- each is a separate API? And you need to map those paths to according DNS records?

[TanVD]

Could you give an example of what you are trying to do?) It may help a bit 🙂

[LeoColman]

Sure! Thank you for your patience!

Let's say I have 2 teams. Team 1 works on HelloWorld project and Team 2 works on HiWorld project.

Both the teams define their APIs:
• /helloworld
• /hiworld
And now I want to deploy both to an API gateway, as we're serving these apis do an external client. I want both to be indexed under api.hi , so
• https://api.hi/helloworld
• https://api.hi/hiworld
Each API is defined in its own Kotless application, as both teams are doing entire different applications.

[LeoColman]

Today I can do that via serverless

[LeoColman]

It seems that with Kotless I can do it with a single project, but that seems a little bit counter intuitive, as I would have to put all functions under the same application

[LeoColman]

It's probably way out of scope for what Kotless is usually used for, but I'm trying to replicate this usecase to test Kotless' as an alternative for our typescript stuff

[LeoColman]

I can open an issue if you think it's more appropriate

[TanVD]

Yeah, it would be very nice of you. As for use-case. In general it means that you have two different applications that should end up being one APIGateway under different base paths. This use-case is not supported right now, unfortunately.
As an alternative, you can use different third level names, like hi.api.hi and hello.api.hi

[TanVD]

I would say, that for a big projects that approach is also preferrable -- it makes links shorter and looks cleaner in address panel of browser.

[TanVD]

Still, I would consider implementation of your use-case as well, if you would create an issue 🙂