{"id":7980,"date":"2026-05-07T12:47:56","date_gmt":"2026-05-07T10:47:56","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=7980"},"modified":"2026-05-07T12:47:57","modified_gmt":"2026-05-07T10:47:57","slug":"the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/","title":{"rendered":"The impact of bot attacks on the costs of elastic scaling"},"content":{"rendered":"\n<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">Bot attacks, ranging from simple scrapers to sophisticated DDoS (Distributed Denial of Service) attempts, pose a unique challenge for <strong>modular hosting<\/strong>. Because this service automatically scales CPU and RAM to meet traffic demands, malicious bots can artificially inflate your resource usage, leading to higher operational costs without any increase in actual business value.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/#Context\" >Context<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/#Identifying_the_Problem_Log_Analysis\" >Identifying the Problem: Log Analysis<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/#Steps_to_Protect_Your_Resources_and_Budget\" >Steps to Protect Your Resources and Budget<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/#Practical_Implications\" >Practical Implications<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/en\/knowledgebase\/the-impact-of-bot-attacks-on-the-costs-of-elastic-scaling\/#Summary\" >Summary<\/a><\/li><\/ul><\/nav><\/div>\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Context\"><\/span>Context<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Elastic scaling is designed to handle sudden spikes in genuine traffic (e.g., a mention in the news or a viral social post). However, bots don&#8217;t distinguish between &#8220;good&#8221; and &#8220;bad&#8221; traffic. If 1,000 bots hit your site simultaneously, the server will scale up to stay online, consuming &#8220;Elastic Resources&#8221; that you are billed for. Protecting your store from these attacks is both a security measure and a cost-optimization strategy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Identifying_the_Problem_Log_Analysis\"><\/span>Identifying the Problem: Log Analysis<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<\/div>\n\n<div id=\"mybox-562330758\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Early access<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Still need help?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contact our customer service team.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Message us<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">The first step in cost control is identifying whether your traffic is human or automated. On <strong>mybox.com<\/strong>, you have direct access to the raw data needed for this audit.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Location:<\/strong> Access your hosting via FTP or SSH and navigate to the <code>.logs\/www\/<\/code> directory.<\/li>\n\n\n\n<li><strong>What to look for:<\/strong>\n<ul class=\"wp-block-list\">\n<li><strong>High frequency from a single IP:<\/strong> Thousands of requests in a few minutes from one source.<\/li>\n\n\n\n<li><strong>Suspicious User Agents:<\/strong> Identifiers like &#8220;python-requests,&#8221; &#8220;Go-http-client,&#8221; or unknown scrapers.<\/li>\n\n\n\n<li><strong>Patterns:<\/strong> Repeated requests to expensive resources, such as search pages or login forms, which consume more CPU than static pages.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Steps_to_Protect_Your_Resources_and_Budget\"><\/span>Steps to Protect Your Resources and Budget<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Implementing these defenses prevents &#8220;empty&#8221; traffic from triggering the elastic scaling mechanism.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1. Blocking via .htaccess (LiteSpeed Optimization)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Our servers utilize <strong>LiteSpeed<\/strong>, which processes <code>.htaccess<\/code> rules more efficiently than traditional Apache. You can stop known bad actors at the door by blocking their User Agent strings.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Apache<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Block specific malicious bots\nBrowserMatchNoCase \"BadBot\" bots\nBrowserMatchNoCase \"EvilScraper\" bots\nBrowserMatchNoCase \"MJ12bot\" bots\n\nOrder Allow,Deny\nAllow from ALL\nDeny from env=bots\n<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">2. Cloudflare Integration (The &#8220;Edge&#8221; Shield)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Cloudflare is the most effective way to keep costs down on elastic scaling. By using a CDN, the &#8220;Bad&#8221; traffic is filtered at Cloudflare\u2019s servers <strong>before<\/strong> it ever reaches our infrastructure.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Under Attack Mode:<\/strong> If you notice a massive spike, you can enable this to present a challenge (like a CAPTCHA) to all visitors.<\/li>\n\n\n\n<li><strong>WAF (Web Application Firewall):<\/strong> Automatically blocks known botnets and malicious patterns.<\/li>\n\n\n\n<li><strong>Cost Impact:<\/strong> Since the traffic is blocked at the edge, your hosting plan doesn&#8217;t need to scale up, keeping your bill stable.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">3. Rate Limiting<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">You can configure rules to limit how many times an IP can request a page per minute. This prevents scrapers from crawling your entire catalog in seconds and spiking your CPU usage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Practical_Implications\"><\/span>Practical Implications<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Unplanned Scaling:<\/strong> Without bot protection, a single &#8220;scraping&#8221; bot could double your resource consumption for the hour it is active.<\/li>\n\n\n\n<li><strong>Resource Efficiency:<\/strong> By blocking bots, you leave more &#8220;room&#8221; in your base resource allocation for real customers, delaying the need for elastic scaling and saving money.<\/li>\n\n\n\n<li><strong>Expert Assistance:<\/strong> If you see a spike in your <strong>mybox panel<\/strong> billing but can&#8217;t find the source in your logs, our 24\/7 Helpdesk can help identify the attack pattern and implement blocks for you.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Summary\"><\/span>Summary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In a modular hosting environment, <strong>Traffic = Cost<\/strong>. Malicious bots are essentially &#8220;stealing&#8221; your server resources. By regularly auditing your logs and utilizing tools like <code>.htaccess<\/code> blocks and Cloudflare, you ensure that you only pay for the traffic that actually grows your business.<\/p>\n<\/div>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[17],"manual_kb_tag":[8847,8848,8849,600,980,1154,1161,1349,1350,6655],"class_list":["post-7980","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-elastic-web-hosting","manual_kb_tag-web-scrapers","manual_kb_tag-auto-scaling","manual_kb_tag-hosting-costs","manual_kb_tag-elastic-scaling","manual_kb_tag-distributed-denial-of-service","manual_kb_tag-cost-optimization","manual_kb_tag-elastic-resources","manual_kb_tag-bot-attacks","manual_kb_tag-malicious-bots","manual_kb_tag-ddos-attacks"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manual_kb\/7980","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manual_kb\/7980\/revisions"}],"predecessor-version":[{"id":7981,"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manual_kb\/7980\/revisions\/7981"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/media?parent=7980"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manualknowledgebasecat?post=7980"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/en\/wp-json\/wp\/v2\/manual_kb_tag?post=7980"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}