amazon-ami

I have managed to successfully launch the most recent RStudio AWS EC2 instance (louisaslett.com, RStudio-1.1383_R-3.4.2…ubuntu-16.04-LTS-64). R operates mostly as expected in this instance, and I can install and open a number of packages. However I get an error if I try to install either of the rgdal of gdalUtils packages. Below is the console output when I attempt to install rgdal. The output for the gdalUtils install is too long to include here, but both include the text "error: upgrade GDAL to 1.11.4 or later" which I suspect is the problem, but have no idea how to correct. Any thoughts or

Is there a way to specify the AWS AMI with particular OS (say Ubuntu) when launching Spark on Amazon cloud with provided scripts? What is the default AMI, operating system that is launched by EC-2 script? Is it eligible for "Free Tier" program by AWS? The script ( spark_ec2.py ) takes the AMI list from https://github.com/mesos/spark-ec2/tree/branch-1.3/ami-list by default. You can override it by creating a fork with your preferences and selecting it with --spark-ec2-git-repo and --spark-ec2-git-branch . 来源： https://stackoverflow.com/questions/28524380/spark-ami-for-aws-ec-2

I'm using the Java API for Amazon AWS. I successfully authenticate, then get all images and my images are not among them (my AMIs are private, but I suppose that I will still see them since I have been authenticated). Here is my source... final AmazonEC2 client = new AmazonEC2Client(credentails); for(Image image: client.describeImages().getImages()){ if(image.getOwnerId().equals("1234567890")){ //... do something usefull with the AMI } } And my "OwnerId" is not among the received ones. What is the problem, I won't make my AMIs public, how can I get my AMIs? ANSWER: I was in a wrong region, and

I'm a new user of Amazon EC2. I want to compile the pptpd package on EC2, but receive the following error: [root@ip-10-112-xxx-xxx /]# /var/tmp/rpm-tmp.2eILT0: line 58: /usr/bin/make: No such file or directory I searched the entire root directory tree, but make isn't available: [root@ip-10-112-59-187 /]# find . -name "make" ./etc/mail/make I'm wondering whether make is actually installed on the Amazon Linux AMI initially? If not, how do I install it? Preface The Amazon Linux AMI is (loosely) based on CentOS and a perfectly decent OS for EC2, in fact it has been tailored by Amazon for EC2

I can build AMI images just fine. But they've stopped working with EC2 User Data: There is user data: $ cat /tmp/user_data.sh #!/bin/bash touch /tmp/i_have_user_data /root/i_have_user_data And I can launch a plain Ubuntu image: aws ec2 run-instances --instance-type m3.medium --image-id ami-eed10e86 --user-data file:///tmp/user_data.sh And it works: ubuntu@ip-10-165-90-180:~$ ls /tmp/i_have_user_data /tmp/i_have_user_data But if I build an AMI based on that one, with Packer: "builders": [ { "type": "amazon-ebs", "region": "us-east-1", "source_ami": "ami-eed10e86", "instance_type": "m3.large",

When we launch an instance from an AMI. At first the instance is accessible(ssh). Once we stop/start the instance or reboot it the machine becomes inaccessible via ssh,we can ping it though. We see below error in System log. AMI ID used - ami-72dc9220 Instance - i-0896a15f - Linux rhel6.4 M1.large instance. ../ ******************* BLKFRONT for device/vbd/2049 ********** backend at /local/domain/0/backend/vbd/236/2049 Failed to read /local/domain/0/backend/vbd/236/2049/feature-barrier. Failed to read /local/domain/0/backend/vbd/236/2049/feature-flush-cache. 14680064 sectors of 512 bytes *******

I've created an AMI(EBS AMI) using the Amazon AWS console. That AMI has 2 snapshots attached to it. Now I want to backup that AMI to a S3 bucket. Is this possible? I actually need to do this to be able to then move that AMI to a bucket in a different region and register that AMI for use in that different region. Any clues? Update My initial answer still applies concerning the question as such (see below), however, given you actually need to do this to be able to then move that AMI to [...] a different region , you will be pleased that AWS has just released Cross Region EC2 AMI Copy to address