Tor bridges in the Amazon cloud
As of May 8, 2015, the Tor Cloud project has been discontinued.
The Tor Cloud project gave people a user-friendly way of deploying bridges on the Amazon EC2 cloud computing platform to help users access an uncensored Internet. By setting up a bridge, they would donate bandwidth to the Tor network and help improve the safety and speed at which users can access the Internet.
The main reason for discontinuing Tor Cloud is the fact that software requires maintenance, and Tor Cloud is no exception. There is at least one major bug in the Tor Cloud image that makes it completely dysfunctional (meaning that users could not use this particular service to access the Internet), and there are over a dozen other bugs, at least one of them of highest priority. Probably as a result of these bugs, the number of Tor Cloud bridges has steadily declined since early 2014.
We have tried to find a new maintainer for Tor Cloud for months, but without success. There have been offers to send us patches, but we couldn't find a Tor person to review and approve them. We encourage everyone who stepped up to start their own cloud bridges project under another name ("Onion Cloud"?), possibly forking the existing Tor Cloud code that will remain available. Tor Cloud is still a good idea, it just needs somebody to implement it.
Or maybe this is a good opportunity for the community to further look into other approaches for providing an easy-to-deploy bridge or relay, like Ansible Tor or cirrus.
If people still want to help users access an uncensored Internet, there remain plenty of ways to help. For example, it's still possible to spin up an instance on Amazon EC2 or any other cloud computing platform and install a Tor bridge manually. Or people can donate to organizations that run Tor relays and bridges like Torservers.net or their partner organizations.
Note that discontinuing the Tor Cloud project has no effect on existing Tor Cloud instances. Whenever one of those instances was started, a template of the operating system and settings was copied, and removing the template has no effect on the copies.
Sorry for any inconvenience caused by this.