Tag Info

Hot answers tagged

72

Since it's the first result for google, I reply later. s3cmd can do this : s3cmd du s3://bucket-name


41

GoDaddy [...] I assume their servers are geographically distributed Don't assume, verify with GoDaddy or verify it yourself. A quick traceroute to nsX.secureserver.com (a common DNS server name for GoDaddy) gives me a response from a datacenter here in Scandinavia where I live. So yes, it seems that GoDaddy has its nameservers spread out over at least ...


31

Update 09/04/2014 1:00AM EST Amazon has stated that all Elastic Load Balancers have been updated and are now longer vulnerable. They recommend rotating certs as well. Update 08/04/2014 2:56PM CST Amazon has stated that all Elastic Load Balancers except those in US-EAST-1 have been updated, and the vast majority of those in US-EAST-1 have been updated. ...


29

https://ip-ranges.amazonaws.com/ip-ranges.json This question has been answered before, but here is the link to the forums, select the sticky link to the list of Ip ranges used by Amazon, it gets updated reliably when they add new information. EDIT: Changed link, whenever the post is updated the link breaks, so just gave a static link to the forum page ...


26

I had to wrap my SPF record in quotation marks for it to work. "v=spf1 include:_spf.google.com ~all"


24

Yes, your understanding is correct. There's no AWS charging based on CPU usage -- you pay the same for an instance whether its CPU usage is 0% or 100%.


23

The correct ssh-keygen command is however: ssh-keygen -y -f /path/to/privatekey > /path/to/publickey


22

The AWS CLI now supports the --query parameter which takes a JMESPath expressions. This means you can sum the size values given by list-objects using sum(Contents[].Size) and count like length(Contents[]). This can be be run using the official AWS CLI as below and was introduced in Feb 2014 aws s3api list-objects --bucket BUCKETNAME --output json ...


22

I had the same question as you, so I worked out how to do it. First, I did this from the Ubuntu 32-bit EBS-backed ami from the US-East region, other OS's or images may work differently. However, I suspect that you should be ok, as long as you are using an ext* filesystem. It might work on other filesystems, but you'll have to figure out how to resize them ...


18

Seems like yes (quoting AWS documentation): You can modify rules for a group at any time. The new rules are automatically enforced for all running instances and instances launched in the future. A simple test of disallowing access to a certain (previously accessible) port also confirmed this.


18

The Amazon Linux (which is essentially CentOS, which is essentially Red Hat) equivalent of update-rc.d is chkconfig. http://www.cyberciti.biz/faq/rhel5-update-rcd-command/ chkconfig --add nginx chkconfig nginx on


17

Don't assume anything about GoDaddy. I've found them to be awful on many occasions. I personally have a separate DNS host to my domain registrar, because the DNS host provides a better service (more adjustable records, rather than just A and CNAME). From what I've seen, Route53 is supposed to be quite inexpensive, at least in line with Dynect's offering ...


17

In your AWS Management Console, go to the EC2 Tab. Check the instance you want to change (from micro to large, for example) Put the instance in a 'Stopped' state. Click the 'Instance Actions' menu, and choose 'Change Instance Type' Choose the level you want the instance to run at (small, medium, large) Click 'Yes, Change'. Restart the instance in question. ...


17

The public DNS name (whether elastic IP address or not) is exactly the same as using the public IP address (elastic IP or not) with the one following important difference: If you query the public DNS name from outside of EC2, it resolves to the public IP address. If you query the public DNS name from inside of EC2, it resolves to the private IP address. ...


17

Add a file:// before the file names


17

The A-record alias you create has to be the same as the name of the bucket, because virtual hosting of buckets in S3 requires that the Host: header sent by the browser match the bucket name. There's not really another practical way in which virtual hosting of buckets could be accomplished... the bucket has to be identified by some mechanism, and that ...


17

To communicate outside of the VPC, each non-default subnet needs a routing table and an internet gateway associated to it (the default subnets get an external gateway and a routing table by default). Depending on the way you have created public subnet in the VPC, you might need to explicitly add them additionally. Your VPC setup sounds like it matches ...


17

Don't overcomplicate things. Just point your ELB health checks at a special URL just for them. server { location /elb-status { access_log off; return 200; } }


16

According to this 2011 blog post, the max connections on RDS instances come out this way: t1.micro: 34 connections ($0.035) m1.small: 150 connections ($0.115) m1.large: 640 connections ($0.455) m1.xlarge: 1263 connections ($0.920) m2.xlarge: 1441 connections ($0.655) m2.2xlarge: 2900 connections ($1.315) m2.4xlarge: 5816 connections ($2.630) No AWS docs I ...


16

If you can guarantee that all requests will be coming from ELB (I'm not familiar with it), you could try: real_ip_header X-Forwarded-For; set_real_ip_from 0.0.0.0/0; That should tell nginx to trust an X-Forwarded-For header from anyone. The downside is that if anyone directly accesses your server, they would be able to spoof an X-Forwarded-For header and ...


15

If you download a usage report, you can graph the daily values for the TimedStorage-ByteHrs field. If you want that number in GiB, just divide by 1024 * 1024 * 1024 * 24 (that's GiB-hours for a 24-hour cycle). If you want the number in bytes, just divide by 24 and graph away.


15

Update AWS has just announced the general availability of the functionality to Monitor Estimated Charges Using Billing Alerts via Amazon CloudWatch (it apparently has been available to AWS premium accounts already since end of 2011, see Daniel Lopez' answer to Is there a way to set Amazon AWS billing limit?): We regularly estimate the total monthly ...


15

Things to check: Your elastic IP associated with your instance? Your security group of instance permits incoming connections? Your instance firewall permits incoming connections? Your application listens?


15

In short: Yes, you can, but not without some work. You'll need to do the following: (For these steps, assume that the machine you're having trouble connecting to is called server-01.) First, before starting these steps, take a snapshot of your server. Start a new, temporary instance. Call it server-02. Stop server-01. Don't terminate it, just stop it. ...


14

untested.. but I try this RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [L,R] http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/TerminologyandKeyConcepts.html#x-forwarded-proto


14

Best practices: Whenever you build an AMI (or even set up an instance) always document the exact steps you took to install and configure the software and what data you put on it and where. This has many benefits including making it easy to rebuild the same AMI for a different architecture. Even better, I recommend scripting most or all of the install, ...


14

If an elastic IP is associated with an EC2 instance, that's the instance's external IP. You can demonstrate this by doing curl canhazip.com in the command line.


13

Associating an Elastic IP with the instance is how this is done. Be aware, that unless you are using VPC, that your elastic IP will disassociate if you stop the instance, and you will have to manually reassociate it when you restart the instance.


13

Check /etc/sudoers.d/cloud-init file, ec2-user default user is there, just delete this file.


13

I ran into the same problem when trying to duplicate a machine. The problem turned out to be the kernel. Both when creating the AMI and the instance I selected default for the kernel image. To resolve the problem, I recreated the AMI using the same kernel image as the original instance.



Only top voted, non community-wiki answers of a minimum length are eligible