Yes, If you don’t know where you are clicking on AWS it could cost you tens of thousands. I lost about 25000 just trying to explore the services it offered. I accidentally got committed to a long term contract clicking here and there. On support call to cancel the invoice, I learned it cannot be cancelled and the only option was to pay for it.
yeah, initial setup is a PITA. Had to look through a lot of yt videos to understand. I went pretty conservative and only slowly looked at new things until I got it.
There is a big risk if your access gets stolen. So need to setup multiple accounts and use a very limited one day to day. Plus yubikey as totp for AWS as well as gmail etc. AWS pushed me to improve security on all important online accounts.
Also from what i understood the ec2 discounted rates apply only for continuous 24x7 long term usage. Wasn’t clear initially.
They dont seem to be set up for retail. Not having prepaid is pretty terrible. Atleast an option should be there before prepaid vs postpaid, with say some kind of buffer that you yourself decide, then downsides go away.
Also windows servers are much more expensive vs linux in Mumbai atleast.
Then they were bad to you. I have read that they have forgone much worse bills when mistakes were made or access was stolen. In your case, it seems you did not even use the resource, they could have easily cancelled that. Terrible.
Have to be careful with AWS, but once setup, it seems to be simple enough for day to day work. I really like tunneling feature, gives me an option to not expose ports and just give access via aws-cli. I am not an expert, so reduces risk.
This was like a price lock for discounted computing cost for a year. Since they have already pulled that time for me from their computing auction pool , they said such contracts cannot be cancelled. At least that’s what I understood from it. I didn’t want amazon to do debt recovery against me, since I have used the same email for my amazon shopping as well. In all the panic and inexperience , I thought paying up was the easiest way out and I did.
That’s the point, if you know what you are doing, AWS is the best.
@Arockiya_Raja @nivas_k i am confused about 3rd change point about market orders with market protection and all…see i use algotest platform for algo execution and all and there i use market orders for entry…but there is no option as market protection type of thing in there system so how it is going to work please explain…is my orders are going to execute or not
Market orders from algotest will be executed as limit order with market protection. Needless to say, algotest will have to find a workaround.
Still my question is same
During large moves, if execution has to happen at greater than the say 2% (mkt protection) of current ltp, then broker will mark it as limit order (at 2% buffer)- and your order will only be executed if price is met.
I am just placing all as limit order in my algo (not algotest) with a 15% buffer price, so basically like a mkt order ![]()
Not possible in the conventional way anymore, brokers are not allowed to do that now ![]()
Market orders have been dis-allowed by SEBI when placed using algo. ![]()
MPP orders are essentially limit orders that act as market orders. ![]()
As per the exchange circular, Market orders shall not be allowed to be placed via the broker API.
However, orders can still be placed using the market_protection parameter (i.e., market_protection != 0), which effectively places the order with a protection mechanism similar to a limit order within a defined range. Learn more.
You may also want to check with the respective platform you are using to understand how they plan to handle this change on their end.
