I'm still shocked to read that people assume that Content Delivery Networks are expensive, most charge as little as 0.20c per a GB.
Serving static websites on CDNs is amazing - you get the performance of a dedicated server without actually paying for it, plus you have a server in all major regions around the world so effective its actually better than a ...
I have decided to serve only gzipped version of my pages
If you're only serving files that you've compressed using gzip, then using Vary: Accept-Encoding will be of no benefit since there won't be uncompressed copies of the files to serve to clients that don't send Accept-Encoding: gzip in the HTTP request. Most clients these days do send this, so you ...
Amazon IAM ( http://aws.amazon.com/iam/ ) service gives you the ability to create accounts for students with separate password/credentials and with access to only specified AWS resources.
You can create one account for all students there, or create a group called "Students" and assign all your students to that group.
After doing that you need to specify an ...
S3 web site hosting is strictly for static content. Nothing stored in S3 is executable by S3, such as PHP scripts.
This is by design, and not a configuration issue with your site.
You can host a static website on Amazon S3. On a static website, individual web pages include static content. They may also contain client-side scripts. By contrast, a ...
Amazon has instructions for deploying WordPress on Elastic Beanstalk. The part that will prevent your problem is the section "Enable WordPress to Store Assets in Amazon S3".
You have to install the "W3 Total Cache" plugin in WordPress and configure it to use "Amazon Simple Storage Service S3". When you have done that, plugins and themes will no longer ...
Firstly, make sure you are only linking to one version of the URL, whether it is /blog/ or /blog/index.html (I'd prefer the former since it's shorter and simpler).
The best solution with regards to SEO would be to use a canonical tag. Put this inside the <head> tag:
<link rel="canonical" href="http://yoursite.com/blog/">
That means that when ...
The S3 server could be farther away from you and so it takes longer for the bytes to travel to you. Using Cloudfront or another CDN puts your content on very fast servers all across the world which will increase the speed not just for you, but for users all over no matter where they are located.
Cloudfront also supports compression all though you have to ...
You may be misunderstanding the concept, here.
Files on S3 cannot be modified, but they can be overwritten, and overwriting a file does not require deleting the old file, first. You simply upload a new file with the same name.
The old file does not go away unless and until the new upload is complete and successful. A failed or partial overwrite of an ...
Rename to static-example-com.s3.amazonaws.com - this would work with the out of the box wildcard cert they supply. Take a look at what AWS recommends here.
Also, Id read through the answer here It looks like others have had the same issue you are having now.
It turned out that HSTS headers were being served by the previous hosting. HSTS set all HTTP requests to example.ca to be internally redirected to HTTPS before being sent.
Because custom domain HTTPS was not yet configured for the S3 bucket, the HTTPS request was timing out. Note that S3 does not support custom domain HTTPS directly, only through ...
Moving images from one host to another isn't enough. First are your images compressed and optimized? Second you should be using a CDN as well as s3 together not just serving static content from s3. The CDN's will cache the static content coming from s3 and serve that to your visitors quicker than s3 would.
S3 isn't meant to be the ONLY tool from AWS for static website hosting. The recommended approach is to put CloudFront in front of the S3 instance so that CloudFront can handle caching. I believe this will also eliminate your issue with paying a bunch for an increase of traffic since CloudFront will use it's cache to serve the files and not hit S3. Of course, ...
The problem is in the "pay as you go" part.
If you get tons of traffic (ie: a DOS attack or a very popular blog post or file) you will PAY for it.
AFAIK there isn't still a feature to put a cap to what you pay. You can set billing alerts, but if your billing reaches your maximum budget the only option you have is to shut the site down or you will pay for ...
While I cannot find any documented page on AWS documentation to confirm this, from personal experience I can verify that unfortunately it is not currently possible to pay Amazon Web Services in GBP (£), or any currency other than USD ($) for that matter.
I'm also a UK-based AWS customer and can confirm that in addition to the exchange rate, the UK banks (e....
I have just checked with several DNS lookup tools that the address is not tampered with in China.
I have even loaded the website using a Chinese proxy. Again, all is normal.
I suspect that the client simply has some adware infection. If there is some proxying going on, it's a small affair, one ISP at most.
My issue was because my CloudFront origin was not in us-east, and when you auto-select your bucket's origin in CloudFront, it doesn't add the location prefix to the url. So make sure you add your s3 location like so:
The website started working but I completely changed my approach.
I ignored the problem that I can't connect through the domain name using HTTP.
Decided to just start setting up HTTPS for the site instead
I followed a tutorial that explained how to set up SSL for an AWS S3 static site using:
Amazon Route 53
Amazon Certificate Manger
Google should only return image results under Google image search. So if you search for site:example.com and click on the image search afterwards, it should just return your results.
Google will index whatever is embedded in the page regardless of whether you're using a CDN or not, and so 'View Image' will display it on the CDN while 'Visit Page' will ...
(Answer By @Frank)
You can enabble logging on the bucket and then use the API to figure out what is going on. You can also access your live usage figures in your AWS Account Console.
According to the Billing FAQ, it is now possible to choose a non-USD currency for your AWS account:
Q: Which currencies can I choose from?
AUD – Australian Dollar
CHF – Swiss Franc
DKK – Danish Krone
EUR – Euro
GBP – British Pound
HKD – Hong Kong Dollar
JPY – Japanese Yen
NOK – Norwegian Krone
NZD – New Zealand Dollar
SEK – Swedish Krona
USD – United States ...
I initially tried mod_rewrite in my .htaccess ...
You could perhaps use mod_rewrite together with mod_proxy to create a reverse proxy to your CDN. This has the advantage of hiding the location of your CDN. For example, in your HTML, reference your assets in a "virtual" subdirectory (or subdomain), eg. /cdn.
It seems you have a lot going on.
Your robots.txt needs to be looked at. I will leave it at that. Then...
Your text sitemap needs to be html for the site and xml for the
search engine, not plain text.
Submit that sitemap to search engines (you can create your sitemap without the #! and it will work.)
Create a Webmaster Tools account for Google > add site >...
Double redirects are less efficient:
The browser makes a GET request for each
Each hostname (or subdomain) requires a separated DNS lookup.
In your chain you will have:
3 GET requests
Two DNS lookups (HTTP and HTTPS use the same DNS lookup for example.com)
If it is convenient, it would be better to configure http:// www.example.com to redirect directly ...
CloudFront supports multiple origin servers, and uses path patterns to determine which origin server to forward the requests to... so multiple, independent backend systems, even systems that aren't inside AWS, can all "own" one or more paths under a single hostname, with one of them being the default and owning all the paths not explicitly ...
Allow: * should actually be be Allow: /.
That could be the issue... because, really, using Allow: is somewhat meaningless by itself -- its purpose is for allowing a sub-path within a denied path. As it stands, it seems possible that your file is being misinterpreted.
Anything not denied is supposed to be implicitly allowed.
If you want to allow ...
Figured it out - in have two buckets in S3 - mydomain.com and www.mydomain.com. mydomain.com is where the site is, and I set www.mydomain.com to redirect to mydomain.com.s3-website-ap-southeast1.amazonaws.com... I moved the files to www.mydomain.com and removed the redirect.
The reason you see a 301 in your curl is because www.mydomain.com redirects to mydomain.com from the S3 endpoint for www.mydomain.com. This is a common configuration when using S3 for your static website. The question is how do you have mydomain.com configured in your DNS zone at Namecheap? If the browser is displaying the S3 url I can only assume that the ...
Facebook uses the facebookexternalhit user agent
Google+ uses a user agent containing "Google"
You should grant them access by user agent.