The Apache web server lets you control access based on various conditions. For example, suppose you want to restrict access to http://subdomain.domain.com/ (mapped to the /var/www/subdomain directory) from the 192.168.1.0/24 network (within an intranet).
Apache provides access control based on client hostname, IP address, or other characteristics of the client request using mod_authz_core in Apache 2.4 (or mod_authz_host / mod_access in legacy Apache 2.2).
With mpm-itk, a multi-processing module (MPM), you can run each VirtualHost with its own user ID and group ID. This is commonly used to secure shared hosting, since you don’t have to make every VirtualHost folder readable by the Apache user.
mpm-itk is based on the traditional prefork MPM, which means it’s non-threaded; in short, this means you can run non-thread-aware code (like many PHP extensions) without problems.
If you lose your Amazon EC2 SSH key and can’t log in to your instance, this isn’t a big problem as long as your instance is EBS-based and uses an Elastic IP.
1. Upload your new SSH key, or use one generated by AWS.
2. Create an AMI of your instance.
3. Launch a new instance from your AMI and select the new SSH key.
4. Log in to your instance with the default user (ubuntu or ec2-user, depending on your original AMI).
5. Reassign the Elastic IP to the new instance.
6. Turn off the old instance and terminate it.
Modern Alternatives (No Instance Replacement Required): Today you can usually regain access without cloning an AMI by connecting via AWS Systems Manager Session Manager, pushing a temporary key through EC2 Instance Connect, or stopping the instance to attach its root EBS volume to a temporary rescue VM and updating ~/.ssh/authorized_keys directly.