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
  • CI/CD with Altostra CLI and Github Actions
  • Deploying a Project to Multiple Environments

How To

    Working with projects

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

    Working with environments

    • Manage an environment
    • Configure stacks expiration for an environment

    Working with the Editor

    • Quick Start
    • 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

    • account
    • activity-log
    • api-key
    • build
    • config
    • console
    • deploy
    • docs
    • endpoints
    • environments
    • import
    • init
    • invalidate
    • login
    • logout
    • new
    • projects
    • push
    • deploy-cfn
    • deploy-sam
    • deploy-sls
    • stacks
    • sync
    • tasks
    • templates
    • versions
    • whoami

    Options

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

Errors And Solutions

  • Autnentication Required
  • Import Project Troubleshooting

Technical Reference

  • Environments
  • Stacks
  • Projects
  • Project Versions Repository
  • Log Shipping
  • Deployment Modes
  • Altostra Cloud Integration

Integrations

    CI/CD

    • CircleCI

    Git

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

    Messaging

    • Connect a Slack workspace

    Security

    • Connect an Auth0 tenant

Stacks

A Stack is a live instance of a project deployed to a specific environment which can then be updated by further deployments of that same Stack.

You can deploy Altostra projects multiple times to multiple environments, by creating a new unique stack each time you deploy.

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

Terminology

Creating a stack 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 a stack 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 stacks

Branch deployments

If you're using the Branch Deployments strategy with Git, deploy each branch as a separate stack 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 your CI pipeline to create a stack for each Pull Request, and then update the stack on every git push to the Pull Requests's branch.

Multiple stages

If you're using multiple stages for projects, such as Dev, QA, Prod, then create a stack for each stage and update the stacks as needed.

← EnvironmentsProjects →
  • Terminology
  • Use cases for stacks
    • Branch deployments
    • Preview deployments
    • Multiple stages

Ready to Get Started?

Get Started for Free
© 2022 Altostra, Inc.