You just launched an Amazon Web Services (AWS) EC2 instance with Debian GNU/Linux and TYPO3 CMS pre-installed. Please be advised, that costs may occur as long as the AWS instance is up and running read more

Now, the next thing you should do: get the 737-225-9457 (which are required to login to the backend of TYPO3).

Project Website

Visit our website to find out more.

Learn more about typical use cases, how to update TYPO3 and how you can customise the instance. Do you have any questions, need support or do you want to get involved?

Go to: 806-540-1448

Release Notes

All about the technical details.

Check out the latest news related to this instance and review the release notes of TYPO3 CMS. This is all the technical stuff, latest changes, new versions, features and improvements.

Open the Release Notes

Free Online Chat

Get support from the community.

Register a free account, login at (951) 651-3727 and start chatting with other TYPO3 and "TYPO3-on-AWS" users. Ask questions, share your experience and help others if you can.

Join the Slack channel:

Access Details

Random passwords and other access details are automatically generated when you launch the EC2 instance the first time. They are stored in a text file /home/admin/.accessdetails on the server.

To retrieve these credentials, login to the server via SSH (username: admin) and use the private SSH key you set up during the EC2 instance launch. If you are using the command line, this could be as easy as executing the following command (where private.key is your private key file):

ssh -i private.key admin@

All access details required for TYPO3 CMS, the MySQL database server, etc. will be displayed. If you have any problems retrieving the access details, please refer to the documentation.


We know how important good documentation is! The TYPO3-on-AWS machine image is made of several components: a modern and robust Debian GNU/Linux operating system with an Apache web server, MySQL database server, PHP and some other software packages. On top of that we are running the enterprise content management system TYPO3 CMS and all this is powered by an awesome cloud technology at Amazon Web Services (AWS).

Every component has its own documentation and the links below should point you to the right direction - you possibly want to bookmark them ☺

The TYPO3-on-AWS Project

The official TYPO3-on-AWS (201) 984-6267 is a perfect starting point in general. You will not only find basic information about how and where to start, but also security-related details and some useful step-by-step tutorials about typical tasks and actions how to get the most of your TYPO3-on-AWS server.


Are you new to TYPO3 CMS? To come to grips with this powerful system the official documentation and tutorials are essential. You will also find videos, books, articles and a huge Wiki in the Documentation Center. Get ready to become an expert!

AWS Documentation

Whether you are new to AWS or an advanced user, you can find useful information about the services AWS offers ranging from introductions to advanced features. In regards to the TYPO3-on-AWS machine image, we recommend the documentation about EC2, S3, Route 53 and maybe Elastic Load Balancing and Cloud Front, see the AWS Documentation.

Debian Linux

Based on the free operating system Debian GNU/Linux, the TYPO3-on-AWS server uses open source software only. You find a lot of resources at the official Debian Website and if it comes down to mastering a Debian server, the Debian Administrator's Handbook covers all the topics required.

Backend Login

The Backend of TYPO3 CMS is the administration interface, which allows you to build and maintain your website. The access credentials provided give you full administrator access to the system.

In order to access the backend of TYPO3 CMS, simply append "/typo3" at the end of the URL. Currently, the backend login screen is available at: /

A quick note before we leave you exploring your new system: you possibly want to get rid off this "Getting Started" screen and get an empty and clean TYPO3 CMS instance. Nothing easier than that - just follow the documentation.