Questions tagged with Reliability

We are using the Windows AWS Workspaces client to connect to a Linux Workspaces VM. We are finding that whenever we use the "Snipping Tool" app on the local machine (which has the Workspaces client installed) then after a few seconds the Workspaces client will say that its lost connectivity and then disconnect. It is consistently when using the tool and we are having no issues with connectivity / network reliability when we don't use the snipping tool. We are using the latest version of the Workspaces client. Does anyone know why this might be and how to fix it?

Wordpress website (bitnami package) running on Lightsail instance stops displaying after 2-3 days, requiring a restart. Bitnami offers a built-in diagnostic tool which states that ports 22, 80 and 443 are not accessible remotely at the time this issue persists. Lightsail instance networking/firewall settings show that the ports in question are enabled. Rebooting the Lightsail instance resolves the issue, but the problem repeats itself after 2-3 days. We have to keep restarting the server every couple days to keep the website live. Would like to find a reasonable solution.

Has anybody had experience with the Amazonbot web crawler? (especially with it looking like a DOS incident) We have a client where their service (hosted on AWS) kept going down until we identified an unusual amount of traffic from an Amazonbot with the User-Agent of "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/600.2.5 (KHTML\, like Gecko) Version/8.0.2 Safari/600.2.5 (Amazonbot/0.1; +https://developer.amazon.com/support/amazonbot)", after blocking it at an Application Load Balancer level via User-Agent Header rules (since modifying the "robots.txt" did not work / wasn't read) the response time of the clients service dropped significantly and has remained up. If anybody knows what generally causes Amazonbot to crawl sites, or how I can identify the cause for this specific client's site, that would be extremely useful, cheers.

We need to stand up a new server in Central or South America to support our application in Guatemala. What is the best region or edge server to give our application as little latency as possible? For possible server locations, we are looking at: * Querétaro, Mexico city which Maps shows as about 1,040 miles from Guatemala * Bogota, Columbia which Maps shows as about 1330 miles from Guatemala

Based on the recent outage at us-east-1, where we have most of our AWS resources, the company has taken the path to start transitioning into a multi-region architecture, but picking which extra region(s) to use is not a matter of chance and the decision must be thoughtfully taken. Right now the first criteria to consider is cost as most US-based regions are cheaper for example than the one in Sao Paulo. Latency for our customers (distributed across LATAM and US) might be worthwhile considering, but right now everything is working from Virginia. For major disasters maybe replicating to a different country, or perhaps even continent could be the best for geographic isolation, but at a cost. How do you actually decide which regions to use? How to weigh different factors? Is there an actual guide for such?