Kojira is a stand-alone daemon which can run anywhere where koji-utils rpm is installed. There is no API for that, everything is handled by that daemon - see https://docs.pagure.org/koji/utils/#kojira for details.

Kojira is a stand-alone daemon which can run anywhere where koji-utils rpm is installed. There is no API for that, everything is handled by that daemon - see https://docs.pagure.org/koji/utils/#kojira for details.

Thanks @tkopecek. By this you mean, kojira is not connected to koji-hub, kojid(builder)? So If I want to run the entire kojira on AWS Lambda, I would just require the koji-utils rpm and nothing else? What are your thoughts on it?

You need:
a) configured hub url in /etc/kojira/kojira.conf (for hub connection)
b) rw access to /mnt/koji (for kojira to be able to delete old repos)

So, if you're able to provide these you're ok to go. It depends on your whole koji infra, especially on storage management if you're able to provide that RW access.

Thank you @tkopecek appreciate it. I have a doubt here by /etc/kojira/kojira.conf you mean https://pagure.io/koji/blob/master/f/util/kojira.conf ? I need some more insight if you could tell me where exactly in the kojira code is it making connection with the hub? I understand that it's a stand-alone daemon, but there must be some entry-point, some function calling that is taking place. That info would be helpful.

From this place on: https://pagure.io/koji/blob/master/f/util/kojira#_1333 In next lines it will do the first call depending on authentication type.