Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
michaellzc
force-pushed
the
02-18-revamp_docker_compose_aws_docs
branch
from
86133b1 to
def8771
Compare
|
|
||
| ### Amazon EC2 | ||
|
|
||
| Follow the instructions in the [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to set up an EC2 instance with an EBS volume mounted. Ensure that you select an appropriate instance type based on your expected workload and resource requirements. We recommend using the Amazon Linux 2 AMI. Also, ensure that your EC2 instance is configured to accept incoming traffic from the internet on the standard ports (80 for HTTP and 443 for HTTPS) and that you have SSH access to the instance for management purposes. |
There was a problem hiding this comment.
A couple of thoughts on this section:
- Is there any specific reason we're recommending Amazon Linux 2? I could see customers reaching out to clarify whether other linux distros would be supported since we're explicitly calling this out.
- The last sentence assumes every deployment will be internet exposed. I'd suggest something along the lines of:
Configure inbound rules to allow HTTP/HTTPS (ports 80 and 443) only from the networks that should be able to reach the application (public internet for external deployments, or corporate/private ranges for internal deployments). Ensure you also have administrative access (SSH or Session Manager) for ongoing management of the application.
|
|
||
| Follow the instructions in the [AWS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) to set up an EC2 instance with an EBS volume mounted. Ensure that you select an appropriate instance type based on your expected workload and resource requirements. We recommend using the Amazon Linux 2 AMI. Also, ensure that your EC2 instance is configured to accept incoming traffic from the internet on the standard ports (80 for HTTP and 443 for HTTPS) and that you have SSH access to the instance for management purposes. | ||
|
|
||
| You should also set up automatic snapshots for the EBS volume following [AWS documentation](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-creating-snapshot.html) to ensure that your data is backed up regularly. |
There was a problem hiding this comment.
Should we consider adding a note that EBS backups should be scheduled in coordination with the RDS instance backups? I'm not sure how much this could complicate DR if the backups are taken at different times, but I assume this is a best practice.
|
|
||
| ## Deploying Sourcegraph | ||
|
|
||
| Follow the [installation steps for Docker Compose](/self-hosted/deploy/docker-compose#installation-steps) to complete the deployment of Sourcegraph on your AWS EC2 instance. During the configuration step, ensure to provide the necessary connection details for your RDS instance. |
There was a problem hiding this comment.
I'd suggest linking to our external postgres docs here for clarity since it requires a few clicks to navigate to that page from the docker-compose install instructions.
2 participants
No description provided.