I was going through my cluttered mailbox when I came across that amazon had launched CloudFront! This is a new web service that can distribute content using a worldwide network of edge locations that provide low latency and high data transfer speeds. It works with S3 out of the box!
This is awesome news because I had been fretting over the issue of slow content delivery in different geographical locations for an upcoming project. Traditional methods would have required the content to be mirrored across geographically targetted locations and then code had to be written to take advantage of these servers in different locations.
The server distribution is as follows currently, which I guess basically serves the major markets in the world today.
United States
- Ashburn, VA
- Dallas/Fort Worth, TX
- Los Angeles, CA
- Miami, FL
- Newark, NJ
- Palo Alto, CA
- Seattle, WA
- St. Louis, MO
Europe
- Amsterdam
- Dublin
- Frankfurt
- London
Asia
I will be playing with the service very soon once I find time and I’ll post my findings.
If you are getting the following error:
Failed to create virtual server : Mailman cannot be enabled unless the administration list mailman has been created.This can be done in the Mailman plugin module.
I had just came across a solution that I have tried and verified to be working from tidiar on the Amazon Web Services Developer Community. The link to the thread is http://developer.amazonwebservices.com/connect/entry.jspa?externalID=767
Click on the Network Configuration link
Click on the Hostname and DNS Client
Set the Hostname field to your EC2 instance external address
Thereafter just head to Virtualmin Mailman Mailing Lists in webmin, if mailman does not exist, you will find a block that looks like this:
This block will show if the default mailman is not created
Fill in an administration username and password. You can leave the Associate with Domain to
Hit “Create” and you are done.
You should see the following box appear on top now:
After default mailman has been created
You can now enable mailman mailing lists when you create your virtual websites under virtualmin and you should not get the error anymore.
Again credits to tidiar on AWS forums for sharing the solution.
Recent Comments