-
Notifications
You must be signed in to change notification settings - Fork 0
Hosting
This document provides an overview of our hosting setup, including both database and application hosting, using Amazon Web Services (AWS).
Our database is hosted using Amazon RDS with Postgres.
- Endpoint: dart-explore.cm2rk5aogwhi.us-east-1.rds.amazonaws.com
- Port: 5432
- Database: dart-explore
- Managed By: Zane Bartlett
- Security Measures: Secure login and key pair generation are implemented for database access. The database is also contained within the same VPC as all other services for additional network-level security. However, as this is a public facing application, security groups are currently configured to allow necessary traffic.
Refer to the following resources for a better understanding of our database setup:
- Set up RDS instance with Postgres: A video tutorial on using Amazon RDS.
- Amazon RDS User Guide: The official user guide from AWS, providing comprehensive information on RDS setup and management.
Our application is hosted using Amazon EC2.
-
IP Address (IPv4): 34.229.221.248
- Note: This public IP address is subject to change.
- Port: 8080
- Access Example: You can access our application using the following URL - http://34.229.221.248:8080
- Managed By: Zane Bartlett
Refer to the following resources for a better understanding of our application setup:
- Set up EC2: A video tutorial on using Amazon EC2.
- Amazon EC2 User Guide: The official user guide from AWS, providing comprehensive information on EC2 setup and management.
Our service is further optimized through domain routing, SSL/TLS encryption, and a load balancer setup. This process involved registering a domain, obtaining an SSL/TLS certificate, setting up a load balancer, routing traffic to the load balancer, and forwarding traffic to EC2 instances.
- Domain Registrar: Route 53
- Registered Domain Name: dallasbymetro.com
- SSL/TLS Certificate Provider: AWS Certificate Manager
- Load Balancer Name: dallasbymetro-elb
- DNS Configuration: Updated domain's DNS records in Route 53 to route traffic to our Load Balancer
- Traffic Forwarding: Configured Load Balancer to forward incoming requests to our EC2 instances over HTTP
- Managed By: Zane Bartlett
Note: The traffic forwarding via the Load Balancer occurs over HTTP since this internal traffic is secure within the AWS network and is not exposed to the internet.
Refer to the following resources for a better understanding of our setup:
-
Complete guide: A video tutorial through talking about how to set up a load balancer, register a domain, get a certificate, do DNS config, and traffic forwarding.
- Note: We forward to port 8080 instead of 80 like the video walks through as this is what the application is responding to.
On Monitoring & Maintenance: We have implemented basic monitoring features provided by AWS to ensure the smooth running of the application. Regular updates and maintenance are performed as required.
On Security: While this document shares some specific details for transparency, all necessary precautions have been taken to secure the system. This includes secure login measures, key pair generation for the server, and proper passwords at the database and server level.```