Altostra Docs

    ›Working with the Editor

    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

    Grant access to vendor services

    A vendor-service resource lets grant access to an entire service instead of on specific resource. For example, when using AWS, and you wish to grant a Lambda Function access to the S3 service, so it can manage buckets. This is in contrast to granting the Lambda Function permissions to access a bucket and the objects in it.

    Add a Vendor service to your Blueprint

    We'll use the S3 service as an example.

    1. Add the S3 service to your Blueprint.
      Vendor services
    2. Create a connection from the function to the S3 service you've just added.
    3. Set the desired access-level to the service.
      Vendor services access

    When you deploy the project, an access policy is created that grants the function the permissions required.

    ← Configure instances expiration for an environmentUse the Parameter Store →
    • Add a Vendor service to your Blueprint

    Ready to Get Started?

    Get Started for Free
    © 2021 Altostra, Inc.