That's a good point about filtering out the routing errors before they even hit the application. I've not used a WAF before, have you written up anything on how to do this with a Rails application (or can you point me somewhere for that)? I definitely appreciate keeping the useless or malicious traffic away from the app itself.
As for Twilio SIM support, the narrowband SIM you have works on T-Mobile's NB-IoT network in the US. That's the only narrowband partnership we have right now and I don't know anything more than that.
We do have regular Twilio Wireless SIMs that are great for building IoT devices too. They work all around the world. We also have the Twilio Super SIM coming soon that will switch networks (rather than roaming) and will also work globally. Would you be interested in working with these at all?
I do have AWS WAF video tutorials but I have not had time to publish them.
For AWS WAF they have a WAF marketplace where you can purchase WAF rules that will filter them out for you. So AWS WAF I believe can cost around $7 per / month. The purchased rules from a vendor vary but can be additional $20 on top per month.
To be cost-effective you can just write your own rules in AWS WAF and this is what I do. You can add rules based on regex patterns and so I just look in my rollbar for bizarre routes with bizarre User Agents and I add them to my AWS WAF ruleset. I also prefer this approach because I get to familiarize myself with the kind of traffic.
AWS has a free CloudFormation in the AWS Docs that sets up a honey pot for you. I've modified this template for myself to deal with and be alerted of scrapers.
Thank you for sharing more information on the variety of SIMs.
Wireless and Super SIM I didn't investigate so maybe there is something feasible here.
I appreciate you dug that up for me.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Andrew,
That's a good point about filtering out the routing errors before they even hit the application. I've not used a WAF before, have you written up anything on how to do this with a Rails application (or can you point me somewhere for that)? I definitely appreciate keeping the useless or malicious traffic away from the app itself.
As for Twilio SIM support, the narrowband SIM you have works on T-Mobile's NB-IoT network in the US. That's the only narrowband partnership we have right now and I don't know anything more than that.
We do have regular Twilio Wireless SIMs that are great for building IoT devices too. They work all around the world. We also have the Twilio Super SIM coming soon that will switch networks (rather than roaming) and will also work globally. Would you be interested in working with these at all?
Hey Phil,
I do have AWS WAF video tutorials but I have not had time to publish them.
For AWS WAF they have a WAF marketplace where you can purchase WAF rules that will filter them out for you. So AWS WAF I believe can cost around $7 per / month. The purchased rules from a vendor vary but can be additional $20 on top per month.
To be cost-effective you can just write your own rules in AWS WAF and this is what I do. You can add rules based on regex patterns and so I just look in my rollbar for bizarre routes with bizarre User Agents and I add them to my AWS WAF ruleset. I also prefer this approach because I get to familiarize myself with the kind of traffic.
AWS has a free CloudFormation in the AWS Docs that sets up a honey pot for you. I've modified this template for myself to deal with and be alerted of scrapers.
Thank you for sharing more information on the variety of SIMs.
Wireless and Super SIM I didn't investigate so maybe there is something feasible here.
I appreciate you dug that up for me.