Security and compliance are given top priority in most companies. A solid security concept saves unpleasant costs, but also minimizes non-quantifiable risks. Therefore, we give some insights into security and compliance issues for a TYPO3 set up on AWS.
You have decided in favour of migrating your TYPO3 installation to AWS? Congratulations! In the next step you need to consider a suitable migration strategy. In this article we present common migration strategies for TYPO3 and share some useful tips.
Solutions based on Cloud-Architectures are omnipresent. In particular, hosting TYPO3 in the AWS cloud may have different advantages. As a starting point for this series of blog posts, we give a concise overview on security, performance, flexibility and cost-efficiency.
Today I would like to use the opportunity to demonstrate the setup of a new TYPO3 installation using composer with only a couple of commands in less than 5 minutes.
On Monday (March 6th, 2017), information about a Zero-Day Vulnerability Remote Code Execution (CVE-2017-5638) in Apache Struts actively exploited in the wild was made public and pretty quickly spread through the well known web channels.
In the last blog post we described how our infrastructure and setup works and what we wanted to achieve with it. Now you can experience it yourself! We just opened our infrastructure to allow public contributions - for example to the blog extension - and here is how it works.
In this post we want to give you a glimpse of how we are working internally, which tools we use and what the benefits of that workflow are to us.
The server that delivered this blog post for you is configured with a decent security setup. One of that is HSTS.