Hey everyone, I am a little confused with the instructions on deploying lakeFS on AWS. I was able to follow through with the quickstart tutorial and having lakefs and lakectl run locally. When following https://docs.lakefs.io/deploy/aws.html#on-ec2, I am a bit confused as to what the connection_string and secret_key would be. The secret key can be any randomly-generated string that I make? I am also a complete beginner on AWS and was wondering what it means to 'run the binary on the EC2 instance'. I would have to connect to an EC2 instance and run the command there?

Hi @Harris Vijay, and welcome to lakeFS! lakefs • The connection_string should be the endpoint and port of the newly created RDS (follow AWS documentation on how to connect to the RDS) • secret_key can be any secure randomly generated string (Configuration Reference) • To learn on how to connect to in EC2 instance, please follow this AWS guide. Once you are able to connect to the instance you created, you can then upload the lakeFS configuration and binary and run the lakeFS instance I hope this helps! Let us know if you have any additional questions 🚀

Hey, I am testing out running on ECS https://docs.lakefs.io/deploy/aws.html#on-ecs and confused on how to run the docker container on ECS. I have set up an ECS cluster and RDS database. Don't know how to run that docker run command on ECS. Does it have to do something with ECR? Sorry for these basic questions I am very new to AWS.

Hi @Harris Vijay, we more than happy to help! ECS is a container service that allows you to run and maintain your containers in a clustered manner as tasks. You can create either an EC2 container or a Fragate serverless container. ECR is the Elastic Container Registry allows you to share and deploy software images on containers. You do not necessarily have to use ECR to work with ECS. If you are just starting with AWS, I suggest you first try to run lakeFS on an EC2 instance. On your previous message you were trying to run lakefs on EC2 instance - have you succeeded in doing so?

Thank you for the information. Working through on running the config.yaml on the EC2 instance. When trying to. I am getting a

parse connection string: cannot parse '<databasename>.<http://us-east-1.rds.amazonaws.com:5432|us-east-1.rds.amazonaws.com:5432>' : failed to parse as DSN

Am I not passing in the endpoint and port into connection_string correctly? The database is initialized correctly as I am to connect to it and the state is available. Could it be that the database size is serverless?

In the configuration reference you can find a configuration example for deployment in AWS. The database connection_string should have a postgres prefix (scheme) and contain the database URI along with the username, password, port and database name.

the username and password is from the one when creating the database?

Yes

It works! Thank you so much for you help I really appreciate it! Excited to dive into this and explore all the features!

That's super! Glad we could help!