Stumbled onto this, was strangely hard to find again later. Putting here for posterity: sudo yum install nodejs npm –enablerepo=epel EDIT 3: As of July 2016, EDIT 1 no longer works for nodejs 4 (and EDIT 2 neither). This answer (https://stackoverflow.com/a/35165401/78935) gives a true one-liner. EDIT 1: If you’re looking for nodejs 4, please try … Read more
You can set a bucket policy as detailed in this blog post: http://ariejan.net/2010/12/24/public-readable-amazon-s3-bucket-policy/ As per @robbyt’s suggestion, create a bucket policy with the following JSON: { “Version”: “2008-10-17”, “Statement”: [ { “Sid”: “AllowPublicRead”, “Effect”: “Allow”, “Principal”: { “AWS”: “*” }, “Action”: [ “s3:GetObject” ], “Resource”: [ “arn:aws:s3:::bucket/*” ] } ] } Important: replace bucket in … Read more
Add a new EC2 security group inbound rule: Type: Custom ICMP rule Protocol: Echo Request Port: N/A Source: your choice (I would select Anywhere to be able to ping from any machine)
A fix for this problem is to add swap (i.e. paging) space to the instance. Paging works by creating an area on your hard drive and using it for extra memory, this memory is much slower than normal memory however much more of it is available. To add this extra space to your instance you … Read more
One way to see the contents would be: for my_bucket_object in my_bucket.objects.all(): print(my_bucket_object)
Yes. Use the Tag Editor. Set “Regions” to “All Regions”, “Resource Types” to “All supported resource types” and then click on “Search Resources”.
I found it to be a 2-step process. This assumes that you’ve already set up a keypair to access EC2 instances in the relevant region. Configure Security Group In the AWS console, open the EC2 tab. Select the relevant region and click on Security Group. You should have an elasticbeanstalk-default security group if you have … Read more
I had the same problem an solved it. Have a look at the step-by-step instructions: Go to console.aws.amazon.com Go To Services -> VPC Open Your VPCs select your VPC connected to your EC2 and select Actions => Edit DNS Hostnames —> Change DNS hostnames: to YES
This error message means you failed to authenticate. These are common reasons that can cause that: Trying to connect with the wrong key. Are you sure this instance is using this keypair? Trying to connect with the wrong username. ubuntu is the username for the ubuntu based AWS distribution, but on some others it’s ec2-user … Read more
Using AWS Management Console: Right-Click on the instance Instance Lifecycle > Stop Wait… Instance Management > Change Instance Type