Automatic Subdomain

To achieve your goal of serving your Django project to different subdomains and automatically adding the name of the server in the Nginx configuration file, you will need to use a combination of Django, Nginx, and Amazon Route 53, which is a scalable Domain Name System (DNS) web service. Here are the steps involved:

1. Amazon Route 53: As a first step, you will need to create a hosted zone in Route 53 for your domain and set up a wildcard DNS record, which allows any subdomain to point to your EC2 server. This is done by creating a record set with the name *.yourdomain.com and type A or AAAA (for IPv4 or IPv6 respectively), pointing to the IP address of your EC2 instance or even better use an ALIAS record pointing to a load balancer. This means that any request to any subdomain of yourdomain.com will be directed to your EC2 instance.

2. Nginx Configuration: To accept requests from all these subdomains, you will need to modify your Nginx configuration file. Nginx supports wildcard server names, so you can use this to accept requests from any subdomain. Here's an example configuration:

   server {
       listen 80;
       server_name *.yourdomain.com;
       location / {
           proxy_pass http://localhost:8000; # This should point to your Django app
           proxy_set_header Host $host;
           proxy_set_header X-Real-IP $remote_addr;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       }
   }
   

   The server_name directive tells Nginx which requests it should handle. In this case, it's any request to a subdomain of yourdomain.com. The proxy_pass directive is used to forward these requests to your Django app.

3. Django Setup: In your Django settings, you will need to modify the ALLOWED_HOSTS setting to allow these subdomains. Since there are potentially infinite subdomains, you will need to add a wildcard to this list as well:

   ALLOWED_HOSTS = ['.yourdomain.com']

   This tells Django to accept any request from a subdomain of yourdomain.com.

Remember that security should be a concern when setting up such a system. For example, any user could potentially create their own subdomain, so you will need to make sure that your Django app can handle this appropriately.

Given the wildcard setup above, you should not need to manually add new subdomains to the Nginx configuration. The setup should already allow for serving your Django project to any subdomain of yourdomain.com.

Lastly, consider setting up HTTPS and obtaining SSL certificates for your subdomains. You can use Amazon Certificate Manager (ACM) to create a wildcard SSL certificate for your domain, and then use AWS Elastic Load Balancing or AWS CloudFront to serve your content over HTTPS.