Comments for Elastic Security http://elastic-security.com Security for the Cloud Tue, 15 May 2012 00:58:11 +0000 hourly 1 http://wordpress.com/ Comment on Launch of HP Cloud with OpenStack by Launch of HP Cloud with OpenStack « Elastic Security | cloudguys.net http://elastic-security.com/2012/05/10/launch-of-hp-cloud-with-openstack/#comment-381 Tue, 15 May 2012 00:58:11 +0000 http://elastic-security.com/?p=1499#comment-381 [...] the private beta of HP Cloud, in order to be ready from day one. We are happy to start our …elastic-security.com/2012/…/launch-of-hp-cloud-with-opensta…For more on this story click (author unknown) … Related [...]

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Frederic Donnat http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-377 Mon, 16 Apr 2012 22:58:36 +0000 http://elastic-security.com/?p=801#comment-377 Hi Mike,

Yes, just mount /dev/sdx1 (which is your root partition ‘/’) instead of the /dev/sdx one.

Pay attention that in the target region you will have to create the same partition table (/dev/sdx1 for ‘/’ root partition and /dev/sdx2 for swap partition) using fdisk command in Step 3.
In this particular case, you also will have to create the swap space using ‘mkswap’ command.

Hope this helps.
/fred

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Mike http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-376 Mon, 16 Apr 2012 17:41:17 +0000 http://elastic-security.com/?p=801#comment-376 * Launch an instance of the AMI (a micro instance-type should be enough)
* Create a snapshot of the EBS volume
* Create a volume from this newly created snapshot
* Stop the instance
* Launch an instance in the same availability zone of the EBS volume
* Attached the newly created EBS volume to the running instance in that region and check the name of the device (/dev/sdx)

On that last step, when I go to mount it on the new (temp) instance it does not allow me to mount the device (/dev/sdx) however it does allow me to mount the partition (/dev/sdx1).

I do not see anything specifying the partition and my AMI has 2 (a / and a swap) should i continue the process just mounting /dev/sdx1 and ignore the swap partition (/dev/sdx2)

]]> Comment on Monitoring Tool: Amazon EC2 plugins for Nagios by Frederic Donnat http://elastic-security.com/2011/08/04/monitoring-tool-amazon-ec2-plugins-for-nagios/#comment-371 Mon, 12 Mar 2012 17:18:45 +0000 http://elastic-security.com/?p=1257#comment-371 Many thanks, for reporting this Julian.
I updated the article.

]]> Comment on Monitoring Tool: Amazon EC2 plugins for Nagios by Julian Alcala http://elastic-security.com/2011/08/04/monitoring-tool-amazon-ec2-plugins-for-nagios/#comment-370 Mon, 12 Mar 2012 16:39:22 +0000 http://elastic-security.com/?p=1257#comment-370 It looks like the nagios monitor for cloudwatch is linked to the instance check plugin. Can anyone direct me to the cloudwatch check? Thanks for writing this!

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Anand http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-366 Tue, 14 Feb 2012 00:06:07 +0000 http://elastic-security.com/?p=801#comment-366 A few small things to keep in mind for others using this outline
1. You can find out the kernel id to use by simply by using the Amazon console in case your base image was one of the standard ones provided by Amazon
2. You may see a few tar warnings – keep an eye out to see if there is anything strange there. It may be better to redirect the tar output to a file so that you can look through it later
3. It was (for me) a bit non trivial to determine the file system type. The default at this time appears to be ext3 for Amazon base images
Regards
/anand

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Anand http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-365 Mon, 13 Feb 2012 16:40:55 +0000 http://elastic-security.com/?p=801#comment-365 Happy to report that it all worked out – i had screwed up the file system specification (used ext4 instead of ext3)
Many thanks for this writeup.

]]> Comment on AWS Policy Generator by momma mia http://elastic-security.com/2011/01/07/aws-policy-generator/#comment-364 Mon, 13 Feb 2012 16:16:58 +0000 http://elastic-security.com/?p=666#comment-364 very, very nice. thanks for all the help-ah. nice spaghetti for you.

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Anand http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-362 Mon, 13 Feb 2012 04:46:56 +0000 http://elastic-security.com/?p=801#comment-362 I somehow thought that the *base* AMI should have the same Kernel id initially. Thanks for correcting that point

]]> Comment on How-To: Copy an EBS-Backed AMI from one region to another one by Anand http://elastic-security.com/2011/02/10/how-to-copy-an-ebs-backed-ami-from-one-region-to-another-one/#comment-361 Mon, 13 Feb 2012 04:44:35 +0000 http://elastic-security.com/?p=801#comment-361 Hi Fred,
Thanks for the pointer. Actually, I forgot to mention that I had indeed tried the “Finding the right Kernel ID” step. Using the resultant Kernel id from the target did create the AMI but the instances launched from it failed the accessibility status check and I was unable to connect to it. Just to make sure I hadn’t made a mistake in following the steps outlined, i tried twice more with the same end result.
I will do some more investigation and report back

]]>