Skip to content

Latest commit

 

History

History

flyte

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

What is this?

This is an example opta configuration file to deploy Flyte on AWS.

You can also use this button to fill in the variable fields in the config.

Deploy to AWS

What does this do?

It deploys a single container version of flyte on EKS in AWS. It uses AWS managed RDS instances and elasticcache. It also sets up various other resources like VPCs, subnets, load balancers etc.

Steps to deploy

  • Fill in the required variables in the config file
  • Put the values-eks.yaml file in the same location as the flyte-aws.yaml file
  • Run opta apply -c flyte-aws.yaml on the config file
  • You will be prompted to approve changes a couple of times as opta will go through various stages. This is expected, just keep approving.

That's it. Flyte is deployed on AWS. You can find the AWS load balancer URL to access the deployment by running opta output

To get DNS to work follow the next section

Getting DNS to work

  • Run opta output -c flyte-aws.yaml to get the nameservers. You will see a section like this:
name_servers = tolist([
  “ns-1384.awsdns-45.org”,
  “ns-2001.awsdns-58.co.uk”,
  “ns-579.awsdns-08.net”,
  “ns-83.awsdns-10.com”,
])
  • Go to your domain registrar (link namecheap, godaddy, etc.) to point the domain to these nameservers.
  • Update delegated field to true in the flyte-aws.yaml file
  • Run opta apply -c flyte-aws.yaml again to generate the TLS certificate

Your domain should now be pointing to the flyte deployment with secure TLS