Clarification on Static IP Requirements for Algo Trading Scenario + Cloud Setup Question

Developer API
1

Hi team,

I need some clarification on the new static IP requirement for algo trading. From what I’ve understood so far:

  • Static IP is mandatory only for order-based APIs.
  • The registered IP can only be shared among immediate family members.
  • Data APIs (market data, feeds, etc.) don’t require static IP.

Here’s my scenario:

  • I have two users running on the same EC2 instance.
    • User 1: Captures market data (no order API usage).
    • User 2: Runs an order bot using the order API.
  • If I assign and register a static IP for the EC2 instance (for the order bot), but not for the data-only bot, will this setup work?
  • In other words, do I need to register a static IP for the user who is not using order APIs and will operate on the same instance (I’m not registering any IP for this Bot but it would be using the same one as the order bot)?

Additionally:

  • What are the deadlines by which static IP registration comes into effect? Things seem tentative, and I haven’t seen a clear final date yet.

And this question to the broader dev community here & not to the Team at UPSTOX (esp. cloud folks):

I’d like to know if there’s a way to configure a single EC2 instance with 2 static IPs:

  • One IP is registered and bound for the order API bot.
  • The second IP is used for any other user having their own order bot, with all its network traffic routed separately so I don’t need a second EC2 instance.
  • It’s a Python Application, run using CRON Jobs

Any AWS/Cloud networking insights would be super helpful here.

Thanks in advance!

2

Yes it will work.

Deadline is 1st October, 2025

1 Like
3

Hello @Raghav_35590666 I’m not a hundred percent sure, but from what I understand of the SEBI rules, we need to input an IP address for order punching and data retrieval shouldn’t be a problem. So basically, you just need 1 IP address for each user doing order punching.

I’m not sure about the AWS part for multiple static IPs, but you can check out this video: https://www.youtube.com/watch?v=RjfHIzisILA. I hope SEBI moves another 2 or 3 months for this rule to be implemented. but as now its gonna be Oct 1st 25. The main problem is even the brokers dont have more clarity on the Algo registration for orders more than 10orders/sec.

1 Like
4

Thanks @jtutanota. I also believe that we need more clarification from the exchanges or SEBI. And it will definitely take time before such regulations and compliance can be implemented by the brokers on their side.

P.S - Will definitely go through the video you shared. Thanks Again!

1 Like
5

Yes, it’s possible to setup 2 or more static IP to the same VM in GCP. I have implemented it. So it also must be possible in AWS, I assume. @Raghav_35590666

6

Yeah, configured the same in AWS using a secondary network interface attached to one VM and assigned its own Elastic IP.

Still need to route on the OS level or bind on the application level. Currently using Namespace to create a secondary namespace with this new interface and executing the application on that namespace. This worked for my use case.