Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT
ADVERTISEMENT

Links 1 through 10 of 24 by Peter Skomoroch tagged ec2+gotchas

Share It With Others!

Due to how Amazon EC2 virtualizes disks, the first write to any location on an instance's drives will perform slower than subsequent writes. For most applications, amortizing this cost over the lifetime of the instance will be acceptable. However, if you require high disk performance, we recommend initializing drives by writing once to every drive location before production use.

To perform the initialization on all drives at the same time:

dd if=/dev/zero bs=1M|tee /dev/sdb|tee /dev/sdc|tee /dev/sde > /dev/sdd

[Note] Note

This can take a long time (about 8 hours for an extra-large instance).

Share It With Others!

ssh-keygen -b 1024 -f user -t dsa

if using this with NFS ensure that the entire home directory has the correct permissions or authentication will fail.

Share It With Others!

Keep user-data small when using right_aws gem with EC2:

When launching an instance with large user-provided metadata, the right_aws gem switch from GET to POST, causing an error in generate_request:

NameError: undefined local variable or method `service' for #<RightAws::Ec2:0x365e98>
from /Library/Ruby/Gems/1.8/gems/right_aws-1.10.0/lib/ec2/right_ec2.rb:147:in `generate_request'

Share It With Others!

Share It With Others!

On the other hand, as the Ingress firewall is running in AWS, from the firewall’s standpoint, to support passive mode FTP the following communication channels need to be opened:

Share It With Others!

can't ssh to instance i-3456925d
Posted: Apr 3, 2008 9:52 PM PDT
Click to reply to this thread Reply

After bundling a new image and rebooting the existing instance, I am not able to ssh ... the ssh command does not even timeout ??

Share It With Others!

A machine in the "running" state may not have finished booting. Try executing a no-op command (e.g. echo > /dev/null) via SSH until it succeeds. alternative, have the machine itself initiate contact after booting (by sending a message to a specific server

Share It With Others!

fta: "just did my first test-run of a Hadoop cluster on Amazon EC2. It’s not as tricky as it appears, although I ran into some snags, which I’ll document here."

Share It With Others!

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT