Can someone elaborate on these basic concepts of hosting via Amazon Web Services? -
i read on amazon documentations, i'm still confused or should overwhelmed different terms.
i'm coming traditional web hosting environment concept understand how storage have , how bandwidth i'm allowed.
here understand far amazon , questions lot of it.
ec2 - assume instances can set webserver (iis) , run .net application? or setup me?
ebs - database? if not, database server? database server (sql server 2005 or 2008) installed? snapshot requests? , snapshot put request?
s3 - used for? thought ebs storage, confused here. why need s3?
elastic load balancing - thought load balancing way alleviate burdens on web servers. how work amazon? mean "elastic" load balancing?
data transfer between region - mean? , how control region data transfers , from?
my requirements following
- i need iis webserver run page
- i need database server
- i need location store files (can on same "server" #1)?
- i need database , file servers recoverable. (i heard need store ebs avoid loss of data?)
- in case 1 web server overloaded, performs slow, need switch off server in farm.
- if traffic spikes, need way increase cpu, memory, etc. ability handle traffic nicely (which purpose of elastic i'm assuming)
in addition, don't understand concept of "if not running instance, shut down or else charged". run website ideally keep 24/7. in scenarios conditionally have instances or down?
[edit]
and how monitor usage? don't surprised couple thousands of dollars? can put cap on it? read stories aws users got surprised $300 bill or whatever when didn't have hosted on amazon nor have traffic intensive sites.
sorry, i'm complete newbie "cloud" computing. trying catch here.
thanks lot in advance
i can perhaps answer of questions, not all. ec2 virtual machines preconfigured number of different options. sounds want windows instance. come number of different memory , cpu options depending on think application need.
ebs fault tolerant file-system. you'll put files, including database files.
s3 in essence content delivery network. rest friendly place put files. example if have static content put whole thing in s3 bucket, , not pay compute power, storage, , bandwidth (which cheap).
i should add, there no need use s3, if comfortable using ec2 instance serve content. question of options.
as why shut off instance -- because you're not using it. example, staging server, use test app, in variety of different scenarios. have different ec2 instance per scenario, start them when want run tests , stop when you're done.
as sql server, 1 of ec2 instances amazon offers "pre-configured" includes sql express set up. if don't want sql express, beleive you'll have use 1 of sql server licences , install on server.
the great thing aws low barrier entry. few dollars investment, can poke around day , see there see. when first started aws found helpful start small, single ec2 instance. open rdp ports , connect it. you'll feel right @ home, having own machine in cloud.
let cdn , load balancing things come in time.
on last bit of advice, remember esb data , instance must in same region. if start machine in europe, , esb volume in seattle you're out of luck. you'll have move volume 1 region (and charge data transfer)
Comments
Post a Comment