amazon-simpledb

I've been browsing for a week on how to use AWS. I've always been using cpanel (I'm new to web) but someone recommended AWS to me. From the info I pieced together from various websites, I think I'm supposed to do the following?: 1) copy my website files to S3 2) set up an instance in EC2 3) set up volume in EBS and attach to instance 4) set up elastic IP and attach to instance. 5) ?? The questions are, 1) is this correct? 2) Where and how do I create mySQL database? Do I use SimpleDB, Where can you find it in the management console? I'm using Windows Server 2008 32b on EC2, should I connect to

I am in the process of building an mobile application (iPhone/Android) and want to store the application data onto Amazon's SimpleDB, because we do not want to host our own server to provide these services. I've been going through all of the documentation and the maximum storage size of element values is 1024 bytes. In my case we need to store 1024 up to 10K of text data. I was hoping to find out how other projects are using SimpleDB when they have larger storage needs like our project. I read that one could store pointers to files that are then stored in S3 (file system). Not sure if that is

I'm using Amazon's tools to build a web app. I'm very happy with them, but I have a security concern. Right now, I'm using multiple EC2 instances, S3, SimpleDB and SQS. In order to authenticate requests to the different services, you include your Access Identifiers (login required). For example, to upload a file to S3 from an EC2 instance, your EC2 instance needs to have your Access Key ID and your Secret Access Key . That basically means your username and password need to be in your instances. If one of my instances were to be compromised, all of my Amazon assets would be compromised. The

Sorry if this question is somewhat subjective. I am new to 'could store', 'distributed store' or some concepts like this. I really wonder what do they have in common and want to get an overview on all of them. What do I need to prepare if I want to write a product similar to this? The NoSQL Database site summarizes the concept like this: Next Generation Databases mostly address some of the points: being non-relational, distributed, open-source and horizontal scalable. The original intention has been modern web-scale databases. The movement began early 2009 and is growing rapidly. Often more

I thought that I could use SimpleDB to take care of the most challenging area of my application (as far as scaling goes) - twitter-like comments, but with location on top - till the point when I sat down to actually start implementing it with SDB. First thing, SDB has a 1000 bytes limitation per attribute value, which is not enough even for comments (probably need to break down longer values into multiple attributes). Then, maximum domain size is 10GB. The promise was that you could scale up without worrying about database sharding etc., since SDB will not degrade with increasing loads of data

What scenario makes more sense - host several EC2 instances with MongoDB installed, or much rather use the Amazon SimpleDB webservice? When having several EC2 instances with MongoDB I have the problem of setting the instance up by myself. When using SimpleDB I have the problem of locking me into Amazons data structure right? What differences are there development-wise? Shouldn't I be able to just switch the DAO of my service layers, to either write to MongoDB or AWS SimpleDB? sirmak SimpleDB has some scalability limitations. You can only scale by sharding and it has higher latency than mongodb

Has anyone considered using something along the lines of the Amazon SimpleDB data store as their backend database? SQL Server hosting (at least in the UK) is expensive so could something like this along with cloud file storage (S3) be used for building apps that could grow with your application. Great in theory but would anyone consider using it. In fact is anyone actually using it now for real production software as I would love to read your comments. This is a good analysis of Amazon services from Dare . S3 handled what I've typically heard described as "blob storage". A typical Web