Old         New
First 1TB           $0.140    $0.125
Next 49TB         $0.125    $0.110
Next 450TB       $0.110    $0.095
Next 500TB       $0.095    $0.090
Next 4000TB     $0.080    $0.080 (no change)
Over 5000TB     $0.055    $0.055 (no change)

Here is where you can get full Amazon S3 price details for all regions.

As it says, DynamoDB is a “Fast, Predictable, Highly-Scalable NoSQL Data Store”  Which really means a highly available key-value store.  Amazon has been using DynamoDB for the underlying storage technology for core parts of amazon.com for years.

Here’s Amazon’s page on DynamoDB.

You can read more technical details about DynamoDB here – http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html

Verify a sender email address

1. In the SES section of the AWS Management Console, click on “Verified Senders”:
2. Then click on the “Verify a New Sender” button:
   
3. Enter the Sender’s Email Address and click “Submit”:
   
4. Then you’ll see the confirmation message:
   
5. Go to that email account and click on the link Amazon will email to you to confirm the address.

Create IAM Credentials

1. In the SES section of the AWS Management Console, click on “SMTP Settings”:
   
2. Click on the button “Create My SMTP Credentials”:
   
3. Choose a User Name and click “Create”:
   
4. Save the SMTP Username and SMTP Password that are displayed . We’ll need them when we’re configuring the server.
   

Configure the server

Now for the fun part. Here I assume you’re running Postfix as the MTA on your server.

1. Install stunnel:
   apt-get install stunnel
2. Add these lines to /etc/stunnel/stunnel.conf and make sure it starts properly (you may have to edit /etc/default/stunnel so that it starts automatically on boot):
   [smtp-tls-wrapper]
accept = 127.0.0.1:1125
client = yes
connect = email-smtp.us-east-1.amazonaws.com:465
3. Add this line to /etc/postfix/sender_dependent_relayhost:
   somesender@millcreeksys.com  127.0.0.1:1125
4. Generate the hashfile with this command:
   postmap /etc/postfix/sender_dependent_relayhost
5. Add this line to /etc/postfix/password:
   127.0.0.1:1125 <your SMTP Username>:<your SMTP Password>
6. Fix the permissions on /etc/postfix/password
chown root:root /etc/postfix/password
chmod 600 /etc/postfix/password
7. Generate the hashfile with this command:
   postmap /etc/postfix/password
8. Add these lines to /etc/postfix/main.cf:
   sender_dependent_relayhost_maps = hash:/etc/postfix/sender_dependent_relayhost
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/password
smtp_sasl_security_options =
9. Load the new configuration with this command:
   postfix reload

Additional Notes

After setting it up, look closely at the mail logs on your server to verify that they are being delivered properly.  As I found through testing, in certain misconfigurations your email will not be delivered and will not remain in the queue on the server.  The mail logs are the only place that will indicate that delivery is failing.

If you need to add other senders in the future, edit /etc/postfix/sender_dependent_relayhost accordingly then run:
postmap /etc/postfix/sender_dependent_relayhost
postfix reload

The reason for using sender_dependent_relayhost is because you want to specify what email gets sent through SES. If you try to send all email from the server through SES, you’ll probably have some end up going into a black hole. When I was testing this previous to using sender_dependent_relayhost, I didn’t have my root@ email address verified and so emails ended up bouncing back, then bouncing into oblivion never to be seen again (because it would try to relay email to root@ through SES too.)

http://www.millcreeksys.com/how-to-configure-your-postfix-server-to-relay-email-through-amazon-simple-email-service-ses/

The problem is, if your servers are behind a load balancer which handles SSL encryption for you, this method of checking won’t work.  Fortunately, there are other headers added by the load balancer you can use to detect SSL.  They are the X-Forwarded-* headers.

For example:
$headers["X-Forwarded-For"] == 123.45.67.89 (because $_SERVER['REMOTE_ADDR'] is going to give you the load balancer’s IP address)
$headers["X-Forwarded-Port"] == 443
$headers["X-Forwarded-Proto"] == https

These headers should work with all loadbalancers, including Amazon’s ELB on EC2.

The maximum expected downtime for each server is only a few minutes. Please email me if you have concerns or questions.

Note: if you want to setup SES in a way that scales much better and functions even with non-PHP sites, please read this more recent HowTo: How to configure your Postfix server to relay email through Amazon Simple Email Service (SES)

• Download Amazon’s SES scripts from here

• Extract the files and create a new one named “aws-credentials” with your key data in it; for example:

AWSAccessKeyId=022QF06E7MXBSH9DHM02
AWSSecretKey=kWcrlUX5JEDGM/LtmEENI/aVmYvHNif5zB+d9+ct

• Verify an email address to use with SES

./ses-verify-email-address.pl -k ./aws-credentials -v someaddress@yourdomain.com


• Check the email account for the address you’re verifying and click on the provided link.

• Send a test email:

echo "This is only a test." | ./ses-send-email.pl -k ./aws-credentials -s "test subject for email" -f someaddress@yourdomain.com someaddress@yourdomain.com
(Note – Until you receive production access to Amazon SES, you can only send to addresses you have verified. You can request production access here.)

• Edit the sendmail_path config in your php.ini as follows:

sendmail_path = /path/to/ses-send-email.pl -k /path/to/aws-credentials -f someaddress@yourdomain.com -r


• Restart/reload Apache and that’s it!

(Additional notes – The “From” address you set in your php.ini file will override any mail headers you set in php.  Sending will fail if you try to set the “From” header to an unverified address or when setting the “Reply-To” header at all in php.)

http://blog.facebook.com/blog.php?post=486790652130

Facebook has finally made the change, are you protecting your users?

• “r” – revision you want checked out from git (r=head works also)
• “l” – number of log entries you want to view

For example, if I was running it on this site here is what each URL would do:

• /gitpull.php – show current status and last 3 log entries (make no changes)
• /gitpull.php?l=15 – show current status and last 15 log entries (make no changes)
• /gitpull.php?r=f54f676 – Checkout f54f676 version, show the last 3 log entries
• /gitpull.php?r=head&l=20 – Checkout HEAD version, show the last 20 log entries

You need to make sure that the directory structure is owned by the HTTP daemon user (so that the files can be updated.)  It is best to run it initially from the command line as that user on the server to make sure everything is working properly.

One word of caution; you should restrict access to who can run this script (maybe with HTTP-Auth over HTTPS) because the script isn’t perfect and you don’t want to let anyone make changes to your site.  There are also certain security risks that are increased when you have your website files owned by the webserver user.  It is recommended that you only use this script in a protected environment.