/explore
|
You are here 
|
wweb.dev | ||
| | | | |
200ok.ch
AWS S3 has a great, but little known functionality: You can request metadata about the content of the bucket in XML. This makes it a great storage space for all kinds of batch oriented applications. No need for a self-written API. |
|
| | | | | ||
| | | | |
willhaley.com
My guide is largely based on the Deploying to Amazon S3 guide from Semaphore, but with some pre-requisite steps and fine-tuning to S3. Switching your DNS provider for your domain to Amazon's Route 53 may be a requirement. Depending on your DNS provider, your DNS configuration, and your willingness to jump through hoops like setting up a reverse proxy on another server, you may be forced to transfer your domain. You should absolutely read the DNS and hosting section of Amazon's Static Website Using a Custom Domain guide before proceeding. |
|
| | | | | ||
| | | | |
sanderknape.com
|
|
| | | | | ||
| | | | |
juffalow.com
Learning new technologies goes always better if you have something to test it on. When I wanted to start using AWS I decided to move there my blog (you are currently reading). And these are the steps it takes. |
|
| | | |||
