1. How a trader can deploy his algo on AWS or any cloud service without getting IP overhead.
2. How does a trader overcome issues when he is travelling and runs his algo in different places?
3. Multiple static IPs are required to solve the above issue? Alternatively, can the user change his static IP address before the access token is generated?
4. IP is required only for order placement/modification, so if a user only uses tick data instead of placing an order, will they have an exception for static IP?
Better to address all these issues before implementing.
1. How a trader can deploy his algo on AWS or any cloud service without getting IP overhead.
There will be some overhead. Unavoidable.
2. How does a trader overcome issues when he is travelling and runs his algo in different places?
This is up to the user. However, you're allowed to change the attached static IP at will once a week so such instances are not too big of a hurdle.
3. Multiple static IPs are required to solve the above issue? Alternatively, can the user change his static IP address before the access token is generated?
We'll allow a primary and secondary static IP per app, as provisioned in the circular. Frequent changing of the registered IP will defeat the purpose of prescribing static IPs so won't be allowed.
4. IP is required only for order placement/modification, so if a user only uses tick data instead of placing an order, will they have an exception for static IP?
For AWS user has to again subscribe for ECS static IP to deploy his algo on cloud. Traders will have to spend more money and face an extra hurdle. "Indian users are like a drum; the person who beats the drum gets all of the money, but all beats go to the poor drum. "
"Indian users are like a drum; the person who beats the drum gets all of the money, but all beats go to the poor drum. "