-
Notifications
You must be signed in to change notification settings - Fork 0
Cloud Deployment & Documentation: Setup Elastic IP #41
Comments
So the chain looks like this now: DNS Server resolves: The DNS server is queried to resolve "Northseattlecollegeevents.com" to an IP address. The DNS records for "Northseattlecollegeevents.com" are checked, and the corresponding Elastic IP address (e.g., 44.238.195.106) associated with the EC2 instance is retrieved. Domain Points to Elastic IP: If DNS settings are properly configured, "Northseattlecollegeevents.com" resolves to the Elastic IP address (e.g., 44.238.195.106) associated with your EC2 instance. This is achieved by setting up an A record in the domain's DNS settings pointing to the Elastic IP address. Example DNS Record: Request Sent to Instance: The user's web browser sends an HTTP request to the Elastic IP address (44.238.195.106), which reaches your EC2 instance. Instance Responds: Your EC2 instance, configured with Nginx and PM2 running the Next.js application, receives the request. Nginx, configured with a server block for "Northseattlecollegeevents.com," forwards the request to the PM2 server running the Next.js application. Example Nginx Server Block: nginx server {
} The Next.js application served by PM2 processes the request and generates the appropriate response, which is then sent back through Nginx to the user's web browser. |
As a dev I would like to have a static IP, since we are using AWS I need to use elastic IP
The text was updated successfully, but these errors were encountered: