DogNamedRottles
Registered Member
- Dec 19, 2021
- 52
- 58
I'm building a scraping bot for a friend of mine to monitor his amazon products. His inventory is quite small (30-50 products) and the amount of times he has to check his products is infrequent (once a month or quarter)
To provide more context, I have the service built out and it's able to navigate to Amazon and the product pages without a captcha block so long as I am using my home ip and the browser stealth plugin is enabled for Playwright. The issue I'm concern about is when this is deployed to a hosting platform like DigitalOcean or Railway that Amazon will start blocking requests more often because the ip will now be from a datacenter. I thought of serveral solutions around this.
1.) If my buddy is not planning on monetizing this, then have him take advantage of his office ip and deploy the service on a physical device. His inventory isn't that large and the monitoring would be so infrequent that Amazon wouldn't detect any bot activity. I would have to install a physical server though and setup networking so that he can access the service himself.
2.) Deploy to a VPS and use a rotating residential proxy. That I would think would be enough to handle the anti-bot detection. The drawbacks are that proxies are expensive and I would have to implement some retry capability to allow for resilience. And I don't think friend will be able to justify the cost on a monthly basis. However, I would suggest to him if he's planning on monetizing this with his partners since then we can justify the cost since now we have people paying for it.
However, my question is if I'm going in the right direction with this? Or am I overthinking the potential issues?
To provide more context, I have the service built out and it's able to navigate to Amazon and the product pages without a captcha block so long as I am using my home ip and the browser stealth plugin is enabled for Playwright. The issue I'm concern about is when this is deployed to a hosting platform like DigitalOcean or Railway that Amazon will start blocking requests more often because the ip will now be from a datacenter. I thought of serveral solutions around this.
1.) If my buddy is not planning on monetizing this, then have him take advantage of his office ip and deploy the service on a physical device. His inventory isn't that large and the monitoring would be so infrequent that Amazon wouldn't detect any bot activity. I would have to install a physical server though and setup networking so that he can access the service himself.
2.) Deploy to a VPS and use a rotating residential proxy. That I would think would be enough to handle the anti-bot detection. The drawbacks are that proxies are expensive and I would have to implement some retry capability to allow for resilience. And I don't think friend will be able to justify the cost on a monthly basis. However, I would suggest to him if he's planning on monetizing this with his partners since then we can justify the cost since now we have people paying for it.
However, my question is if I'm going in the right direction with this? Or am I overthinking the potential issues?