AWS Serverless provides extensive CloudFront logging. However, the logs are significantly different from standard Apache logs - they are not easy to work with, either for diagnosing issues or analysing traffic.
CloudFront
My AWS monthly bill is normally less that $10 (USD, before taxes), of which the t2.micro server is about 55%, EBS storage another 44%, and the remaining 1% is email and S3 usage. The August bill was over $21, with the AWS Web Access Firewall (WAF) being 55% of the total.
The Apache .htaccess file is often used to modify how users interact with websites, such as:
Configuring AWS CloudFront is complicated. I find it useful to create a 'cheatsheet' of the steps and key values that I need to complete the configuration. As an example, assume I am transferring an existing https://subdomain.example.ca site to AWS serverless.
I run a number of Drupal, MediaWiki, and static websites on an AWS EC2 t2-micro server. The server Linux/Apache/MySQL/PHP stack is no longer supported, primarily because of conflicting server and Drupal requirements made upgrading difficult. My plan is to create static versions of the MediaWiki and Drupal sites.