Altostra Docs

    ›Technical Reference

    Getting Started

    • Welcome to Altostra
    • Connect your accounts
    • Install the developer tools
    • Log in from the CLI

    Tutorials

    • Create a Static Website
    • Create a Scalable Webhook
    • Create a Simple API Project
    • Try Altostra without connecting cloud accounts
    • CI/CD with Altostra CLI and Github Actions

    How To

      Working with projects

      • Create a new project
      • Deploy a project
      • Manage a project

      Working with environments

      • Manage an environment
      • Configure instances expiration for an environment

      Working with the Editor

      • Grant access to vendor services
      • Use the Parameter Store
      • Use a custom CloudFormation resource
      • Attach a custom policy to a Function
      • Connect a Function to VPC
      • Add filter policy to SNS subscription

      Organization account settings

      • Set General Settings
      • Connect a Git account
      • Connect Cloud Accounts
      • Manage log aggregation accounts

    CLI

    • Altostra CLI
    • Commands

      • templates
      • new
      • init
      • push
      • deploy
      • sls-deploy
      • sync
      • invalidate
      • domains
      • console
      • environments
      • images
      • instances
      • build
      • config
      • import
      • projects
      • tasks
      • activity-log
      • login
      • logout
      • account
      • whoami
      • api-key
      • docs

      Options

      • --debug
      • --verbose
      • Scripting options
    • Configuration files

    Errors And Solutions

    • Autnentication Required

    Technical Reference

    • Environments
    • Playground Environment
    • Instances
    • Project image
    • Image Repository
    • Log Shipping
    • Deployment Modes
    • Altostra Cloud Integration

    Integrations

      CI/CD

      • CircleCI

      Git

      • Git integration
      • Connect a GitHub account
      • Connect a Bitbucket account

    Instances

    In Altostra, an Instance is a live release of a project in a specific environment. Think of it as an instance of a Class, in development terms.

    You can deploy Altostra projects multiple times to multiple environments, creating a different instance with each deployment.

    Every instance is self-contained, has its own events-history, and is mapped 1-to-1 to a cloud account stack. All instance resources are deployed together and removed together; they all share the same instance configuration.

    Terminology

    Creating an instance means that you deploy a fresh and unique stack of your project to the cloud. All resources are created from scratch, and all tables and buckets are empty.

    Updating an instance means that you push changes to an existing stack of your project to the cloud. The resources already exist and are updated as needed to fit the changes.

    Use cases for instances

    Branch deployments

    If you're using the Branch Deployments strategy with Git, deploy each branch as a separate instance in Altostra as part of a CI/CD pipeline. That way, developers can test their work in parallel without interfering with each other.

    Preview deployments

    If you need to produce a preview for each Pull Request, configure the CI/CD pipeline can create an Altostran instance for each Pull Request, and then update the instance on every push to the Pull Requests's branch.

    Multiple stages

    If you're using multiple stages for projects, such as Dev, QA, Prod, then create an Altostran instance for each stage and update the instances as needed.

    ← Playground EnvironmentProject image →
    • Terminology
    • Use cases for instances
      • Branch deployments
      • Preview deployments
      • Multiple stages

    Ready to Get Started?

    Get Started for Free
    © 2021 Altostra, Inc.