Skip to main content

Self hosted

For enhanced control over your cloud assets, you have the choice to deploy your project independently on your AWS account. This arrangement allows you to harness the capabilities of the genezio CLI without a genezio account. To accomplish this, specify the backend cloudProvider attribute in your genezio.yaml as selfHostedAws.

Here's an example of how to set it up:

name: project-name
yamlVersion: 2
path: .
name: ts
cloudProvider: selfHostedAws

This setup requires AWS CLI authentication on your end. Please verify the presence of your access key and secret access key in ~/.aws/credentials. If you possess multiple access keys, you can choose the one to use by exporting environment variables with AWS_PROFILE=<profile-name>.

Application Architecture‚Äč

The backend application is deployed on AWS Lambda. Each deployed class will have its own separate AWS Lambda instance. An API Gateway is placed ahead of all AWS Lambdas, redirecting the requests to their respective functions.

The frontend application is hosted on S3, utilizing its static website features, while a CloudFront configuration forwards requests to the S3 Bucket hosting the application.

Both frontend and backend code deployment employs the AWS CloudFormation service, creating separate stacks for each.

Each class is deployed on a separate AWS Lambda. API Gateway is forwarding the request to the function that should handle that request.


If your development involves a Dart application, note that you will need a genezio account for Dart code compilation in the Genezio Cloud. We're currently working on integrating with widely used build systems.