Using the dashboard

Start with a project

1. Open Projects and choose New project.
2. Enter the project name, choose the deployment model, and select the AWS region.
3. Save the project. Laminar keeps the project as the home for its environments, resources, deployments, and operational history.

Choose the deployment model that matches your application. See Runtimes for the differences between Lambda, Fargate, and EC2.

Navigate a project

The main dashboard navigation takes you to Overview, Projects, Team, and Settings. When you open a project, a second navigation row appears with that project's focused areas.

• Overview shows the selected environment and project health.
• Deployments starts a deployment and shows deployment activity and history.
• Resources opens the project resource workspace.
• Metrics, Logs, and AI Diagnose help investigate runtime behavior.
• Environments and Settings manage project configuration.

Deploy an application

1. Open a project and select Deployments.
2. Choose the environment, review the detected runtime and deployment settings, then start the deployment.
3. Follow the deployment activity and open the deployment details to review logs, status, and the resulting endpoint.

The CLI is useful for repeatable local and CI deployments. The dashboard is the place to review shared project state and deployment history. See Deploying for the command-line workflow.

Manage environments

Each project can have multiple environments, such as development, staging, and production. Select an environment from the project overview before changing its variables or deploying to it.

• Keep values that differ by environment scoped to that environment.
• Use secrets for credentials and sensitive configuration; do not put them in source code.
• Deploy to a non-production environment first when you need to verify a change.

Add application resources

Open Resources inside a project to connect the services your application needs. Each resource area has its own create, status, and management workflow.

• Databases for RDS or Aurora.
• Caches for Redis-backed sessions and application data.
• Queues for background work and asynchronous processing.
• Storage for private S3 buckets and application files.
• Domains for custom hostnames and TLS configuration.

Resource connection details are returned by the resource workflow and should be provided to the selected environment through env or secret configuration.

Inspect and troubleshoot

Use the project navigation to move between deployments, metrics, logs, and AI Diagnose. Start with the deployment status, then open logs for the failing environment and compare the event time with metrics.

• Metrics shows invocations, errors, and latency.
• Logs shows runtime events for the selected environment.
• AI Diagnose summarizes likely causes and next steps from available deployment state and logs.

Work with your team

Use Team to invite collaborators and manage organization access. Use Settings for workspace-level preferences and account controls. Keep project access narrow and invite only the people who need to deploy or operate an environment.