Hot answers tagged

5

What you might want to achieve is a LOAD BALANCING/CACHE infrastructure. There are several ways to do this. What you have to decide first is how to implement it and where will your Load Balancers be hosted. Option #1 - Load Balance using DNS Round Robin Technically not Load Balancing in the most real sense of the term. You can achieve this by adding 2 or ...


3

If this isn't you, then it must be somebody else... It's common for the web to have Bots, Spiders and Crawlers. Check your log files for the IP to see where the request is coming from. These crawlers usually just use "common" URL paths in the hope that you're using them. If they are just crawling you, then that is not an immediate security threat. But if ...


2

A large point of HTTPS is to make sure that the server you're talking to has a certificate for the name you used to reach it (that is, the name visible in the browser's URL bar). So no, you can't use a default certificate and your own name. If you could, that'd be a security problem. You need to get a certificate that has your domain name in it.


1

Create your www.example.com bucket and set it up for hosting a static website. Apply your policy (pasted here for completion): { "Version":"2012-10-17", "Statement": [{ "Sid": "Allow Public Access to All Objects", "Effect": "Allow", "Principal": "*", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::www.example.com/*" } ] } ...



Only top voted, non community-wiki answers of a minimum length are eligible