Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Computing in the Clouds with AWS Post 302218433 by Linux Bot on Friday 25th of July 2008 05:40:04 AM
Old 07-25-2008
Computing in the Clouds with AWS

Tim Bass
07-25-2008 02:34 AM
The admin*team at The UNIX Forums*have been considering moving the UNIX and*Linux*Forums to the clouds - the Amazon Web Services (AWS) cloud.* Amazon EC2 is one option to scale the forums, which is a*LAMP application.*

Amazon EC2 allows*us to rent dedicated servers (instances) on-demand to run applications, such as the forums.* Then we can run and host on EC2 any Linux application; but unlike classic hosting where*folks install your application and set up your server for you, Amazon Web Services provide*only*the infrastructure.

Here are some links about AWS:

Maybe you will elevate your event processing application to the clouds?



Source...
 

5 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Event Cloud Computing - IBM Turning Data Centers Into ?Computing Cloud?

Tim Bass Thu, 15 Nov 2007 23:55:07 +0000 *I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. Virtualization and Cloud Computing

The Attack of the Spiders from the Clouds

Tim Bass 07-31-2008 08:09 AM We have seen a lot of discussions of cloud computing in the news recently, as a technology to permit “users to access technology-enabled services*without knowledge of, expertise with, nor control over the technology infrastructure that supports them.”* *This sound... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. Virtualization and Cloud Computing

The Attack of the Spiders from the Clouds

We have seen a lot of discussions of cloud computing in the news recently, as a technology to permit "users to access technology-enabled services without knowledge of, expertise with, nor control over the technology infrastructure that supports them." This sound great doesn't it?! Users with... (0 Replies)
Discussion started by: Linux Bot
0 Replies

4. UNIX for Dummies Questions & Answers

How to edit clouds with gimp, artistic painting.

Every cloud has a silver lining. Right, graphics person stumbled into the software world. :p Basically need to Gimp a cloud to paint a silver lunar crescent to create a nocturnal/diurnal atmosphere to a background picture. Am currently using gimp 2 but have in the past used psp and... (1 Reply)
Discussion started by: Maskros
1 Replies

5. Virtualization and Cloud Computing

Private, Public and Hybrid Clouds

Hi all, Private, Public and Hybrid Clouds I'm now testing OpenStack; Home OpenStack Open Source Cloud Computing Software -Infrastructure as a Service (IaaS) -Platform as a Service (PaaS) -Software as a Service (SaaS) It is an Open Source software. I'm interested to know whether... (0 Replies)
Discussion started by: satimis
0 Replies
S3GET(1p)						User Contributed Perl Documentation						 S3GET(1p)

NAME
s3get - Retrieve contents of S3 items SYNOPSIS
s3get [options] s3get [options] [ bucket/item ...] Options: --access-key AWS Access Key ID --secret-key AWS Secret Access Key Environment: AWS_ACCESS_KEY_ID AWS_ACCESS_KEY_SECRET OPTIONS
--help Print a brief help message and exits. --man Prints the manual page and exits. --verbose Output what is being done as it is done. --access-key and --secret-key Specify the "AWS Access Key Identifiers" for the AWS account. --access-key is the "Access Key ID", and --secret-key is the "Secret Access Key". These are effectively the "username" and "password" to the AWS account, and should be kept confidential. The access keys MUST be specified, either via these command line parameters, or via the AWS_ACCESS_KEY_ID and AWS_ACCESS_KEY_SECRET environment variables. Specifying them on the command line overrides the environment variables. --secure Uses SSL/TLS HTTPS to communicate with the AWS service, instead of HTTP. ENVIRONMENT VARIABLES
AWS_ACCESS_KEY_ID and AWS_ACCESS_KEY_SECRET Specify the "AWS Access Key Identifiers" for the AWS account. AWS_ACCESS_KEY_ID contains the "Access Key ID", and AWS_ACCESS_KEY_SECRET contains the "Secret Access Key". These are effectively the "username" and "password" to the AWS service, and should be kept confidential. The access keys MUST be specified, either via these environment variables, or via the --access-key and --secret-key command line parameters. If the command line parameters are set, they override these environment variables. CONFIGURATION FILE
The configuration options will be read from the file "~/.s3-tools" if it exists. The format is the same as the command line options with one option per line. For example, the file could contain: --access-key <AWS access key> --secret-key <AWS secret key> --secure This example configuration file would specify the AWS access keys and that a secure connection using HTTPS should be used for all communications. DESCRIPTION
Retrieves S3 items, and outputs them to stdout. BUGS
Report bugs to Mark Atwood mark@fallenpegasus.com. Occasionally the S3 service will randomly fail for no externally apparent reason. When that happens, this tool should retry, with a delay and a backoff. Access to the S3 service can be authenticated with a X.509 certificate, instead of via the "AWS Access Key Identifiers". This tool should support that. It might be useful to be able to specify the "AWS Access Key Identifiers" in the user's "~/.netrc" file. This tool should support that. Errors and warnings are very "Perl-ish", and can be confusing. Trying to access an item that does not exist or is not accessable by the user generates less than helpful error messages. Trying to retrieve a bucket instead of an item is silently skipped. TODO
option to write to files instead of stdout option to write to paths instead of stdout option to write to a tar file stream, for multiple items option to write extended file attributes based on S3 & HTTP metadata option to have a progress bar AUTHOR
Written by Mark Atwood mark@fallenpegasus.com. Many thanks to Wotan LLC <http://wotanllc.com>, for supporting the development of these S3 tools. Many thanks to the Amazon AWS engineers for developing S3. SEE ALSO
These tools use the Net::Amazon:S3 Perl module. The Amazon Simple Storage Service (S3) is documented at <http://aws.amazon.com/s3>. perl v5.10.0 2009-03-08 S3GET(1p)
All times are GMT -4. The time now is 11:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy