ASTROSCALE / CONSOLE GUIDE

Every control.
Explained clearly.

Use this guide to connect AWS, ship Docker applications, manage domains and billing, build a private network, and give agents only the access they need.

01 / FLEET AND APPS

Deploy, operate, and change apps safely.

Fleet is the application inventory. It shows the selected AWS account, Region, hostname, lifecycle state, deployment state, and estimated cost for every app.

  1. 01
    Create a new app

    Choose an AWS account and Region with an available source connection, then supply a Docker-ready repository, branch, listener port, compute size, and hostname. The repository needs a root-level Linux/amd64 Dockerfile, must listen on 0.0.0.0:PORT, and must return HTTP 2xx from /. The first healthy bootstrap deploys the branch automatically.

  2. 02
    Deploy and investigate

    Deploy a branch or immutable ref, then inspect deployment history and the last 500 application log lines. GitHub App continuous deployment is on by default when the repository is installed and mapped; turn it off in App configuration for manual releases.

  3. 03
    Change settings deliberately

    App configuration changes display name, instance type, Spot use, repository, branch, and continuous deployment. Hostname cutovers stage and validate the new record before removing the old one. Region moves are blue/green, require a source connection in the destination Region, and temporarily use two stacks.

  4. 04
    Operate and delete

    Start, stop, or restart an app from its detail page. During deletion every conflicting control is locked and a live trace explains CloudFormation progress. Correct a failure and retry from the same page.

Configuration history

Every infrastructure-affecting configuration, hostname, and Region operation is recorded on the app. Inspect the history before retrying a failed change or investigating a state that was modified outside Astroscale.

02 / RUNTIME AND NETWORK

Keep secrets private and exposure deliberate.

Runtime variables are encrypted and write-only. Networking starts deny-by-default and only opens the exact access you request.

Environment

Add or remove runtime values without exposing secret contents. Changes queue safely while a stopped app is offline.

Public ingress

Add an exact TCP port and IPv4 CIDR only when required. Astroscale keeps 80 and 443 under managed TLS.

Private routes

Connect running apps in the same AWS account and Region only. The destination receives an internal listener on TCP 8080.

Safe removal

Removing a private route revokes its security-group access. Deleting an app cleans up its managed network rules.

03 / AWS ACCOUNTS

Connect an account without access keys.

Quick Create is the normal path. It creates one external-ID protected role with access constrained to Astroscale resources and verifies it before saving the account.

  1. 01
    Prepare a source connection

    In the target AWS Region, authorize a GitHub CodeConnection until it says Available. The GitHub identity completing this step must have the repository access that CodeBuild needs. Every deployment Region needs its own available connection.

  2. 02
    Use AWS Quick Create

    In AWS accounts, enter the connection ARN, generate onboarding, and select Open AWS Quick Create while signed in to the target account. Review the IAM change, acknowledge it, and create the stack.

  3. 03
    Stay in the console

    Astroscale receives and verifies the callback automatically. Add more source connections later when you want to deploy to another Region. The manual CloudShell and pasted-output paths are recovery-only options.

Common blocker

A public repository still needs an available CodeConnection. A connection that is pending, unavailable, owned by another AWS account, or in a different Region cannot source a deployment.

04 / DOMAINS

Buy a domain or connect the one you own.

Domains lets you find a new name, see its annual price before continuing, choose who pays for it, or authorize a specific public Route 53 hosted zone you already control.

  1. 01
    Purchase a new domain

    Search an entered supported domain, review availability and the displayed price, select Astroscale-managed Stripe billing or a connected AWS account, then enter registrant information and confirm. Pending registrations can be cancelled before Route 53 begins registration.

  2. 02
    Connect an existing domain

    Select the AWS account and public hosted zone, then choose Quick Create. The scoped authorization verifies the chosen zone and does not expose other hosted zones. The advanced exact-zone and CloudShell paths remain available only for recovery.

  3. 03
    Attach it to an app

    Select a verified domain in New app or App configuration. You can use the root hostname for a dedicated app or use subdomains for multiple apps. Astroscale refuses to overwrite an unrelated Route 53 record and removes only records it owns.

05 / COSTS AND BILLING

See spend without exposing card data.

Costs is available for every connected account. Billing is required only when your organization uses the Astroscale-managed AWS account.

  1. 01
    Read Cost Explorer data

    Costs shows account totals, per-app tagged spend, unassigned spend, and projections. Refresh requests a current sync, but AWS commonly delays usage data by 24 to 48 hours. Deleted apps can remain in historical results for the active billing period.

  2. 02
    Use managed AWS when needed

    An organization admin opens Billing and uses Stripe-hosted Checkout to add a payment method. Astroscale never handles card details. After confirmation, the managed deployment account is available in New app.

  3. 03
    Review invoices and status

    Billing shows managed-account invoices and account status. Failed payment blocks new managed deployments and lifecycle starts; BYO AWS apps remain billed directly by AWS and unaffected.

06 / SETTINGS AND AGENTS

Manage teammates and automation.

Organization administrators can invite people, install the GitHub App, create scoped agent keys, and connect authenticated MCP clients.

  1. 01
    Invite and revoke teammates

    Send an email invitation, revoke a pending invite, or revoke a membership. The recipient uses the branded one-time enrollment link, changes the temporary password, enrolls MFA, and joins the organization. Astroscale protects the final organization administrator from removal.

  2. 02
    Enable GitHub App deployment

    Install the Astroscale GitHub App for the organization and grant access to selected repositories. Signed pushes then deploy mapped application branches automatically when continuous deployment is enabled.

  3. 03
    Issue scoped API keys

    Create an API key for local automation, copy it once, and revoke it when finished. Give an agent only the scopes it needs; read, create, update, deploy, lifecycle, destroy, and costs are separate permissions.

  4. 04
    Connect MCP

    Add https://mcp.astroscale.dev/mcp to Codex or Claude and sign in using the same Cognito identity and MFA. MCP manages operational app controls including configuration, hostname, Region, networking, costs, and deployments.

Intentional boundary

AWS onboarding, CodeConnection authorization, GitHub App browser consent, domain purchases, Stripe billing, invitations, API-key issuance, and platform administration remain console-only. These steps require consent, payment, or identity safeguards and are not delegated to agents.

PLATFORM ADMINISTRATION

Restricted to the platform owner.

The Platform area lists organizations and identities, can invite a user to a new dedicated organization, and can remove test identities for enrollment testing. It is not visible to normal organizations and is never available through MCP.

Open console ↗MCP reference ↗