Then dump the static file on S3, and let the interest from the £40K in your bank account pay for it.
- Generate static files using Pelican
- Dump the files to S3
- Set up Route53 to point a domain at the bucket
- Set up CloudFront (Amazon's CDN) to sit in front of the S3 bucket, since I found pure S3 to be too slow
Works incredibly well.
I put my photo/video blog on S3 reasoning that it'll handle spikes better. At one point it reached the front page of HN and cost me $450. Afterward I looked at the logs and found that my single $20 linode would have handled it fine...
But if you're talking about small static websites, AWS gives you an easy interface, Cloudfront, Route53, etc. It's a very easy way to do some very complex things.
You might also look into billing alarms. I've got some simple background jobs that I run on lambda, pulling some files to S3 every hour. It costs me a buck or two a month. But if it ever looks like it might charge me $20, it will alarm and email me.
http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHostin...
http://docs.aws.amazon.com/AmazonS3/latest/user-guide/static...
The "or something" and "which I ignored" aren't making you look like the reasonable actor in these interactions
I doubt it was a mission-critical single static html page.
edit: £70K plus the cost of installation/hardware support/etc/etc.
- "ignored ... a carefully worked out explanation"
- doesn't (or doesn't care enough to) understand the company's established processes ("...or something")
Given that s/he thus didn't (couldn't) relate these in his/her telling of the story, there's at least the possibility that what's missing is less flattering or even completely contradictory to their telling.Just as we can all point to examples of process absurdity, we can all point to examples of
- failures because process didn't exist
- companies with good process
At the very least, from an objective standpoint, the poster's telling of the story reflects poorly on them£70K to host one static webpage is not a good process or "carefully worked out explanation" any way you cut it.
Haha, ours is called "Change Management", but they would more correctly be called "Change Prevention", or "Sanity Obstruction".
£70K of new hardware!
I stuck it on an existing server and nobody noticed though I might have got into trouble with the Change Prevention Board for not using the right form or something...
Edit: He did have a carefully worked out explanation of where the money had to be spent.... which I ignored after hearing "£70K".