<p><strong>Question:</strong></p>

<p>Does Knative expose low-level network components that allow me to configure the stack in such a way, that each instance has a <strong>unique IP address available for outbound networking</strong>?</p>

<p><strong>Info</strong></p>

<p>I have a workload that has to happen on queue event. The incoming event will start the fetching on an API. Due to rate limiting and amount of request (around 100), the process is long-running and with <code>wait / request / wait / request / wait / ..</code> . What the code (JS) basically does is, hitting an API endpoint with parameters from the queues message and sending the result of the 100 API requests back with another queue.  </p>

<p>Serverless on Lamdba is therefore expensive, also on AWS multiple instances are likely to be spawned on the same VM (tested), resulting in the same IP for outbound traffic. Therefore Lambda is not an option for me. </p>

<p>I read a lot about Knative lately and I imagine that the Kubernetes stack offers better configurability. I need to have concurrent instances of my service, but I need to have a unique outbound IP per instance.</p>

<p>Currently, the solution is deployed on AWS Beanstalk where I scale them out based on queue-length. Therefore 1 - 10 instances exist at the same time and perform the API requests. I use micro instances since CPU/../.. load is really low. There have been multiple issues with Beanstalk, that's why we'd like to move.</p>

<p>I do not expect a monthly cost advantage (IPs are expensive, that's ok), I am just unhappy with the deployment on Beanstalk.</p>

CaKa
<p>IMHO, going with KNative/Kubernetes is probably not the way to proceed here.  You will have to manage a ton of complexity just to get some IP addresses.  Beanstalk will seem like a walk in the park.</p>

<p>Depending on how many IPs you need, you can just setup a few EC2 instances loaded up with IP addresses.  One cheap <code>t3.small</code> instance can host 12 IPv4 addresses (<a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI" rel="nofollow noreferrer">ref</a>) and your JS code can simply send requests from each of the different IP addresses.  (Depending on your JS http client, usually there's a localAddress option you can set.)</p>
