How to revert AWS infrastructure changes with awless?

Use 'awless log' to view execution IDs, then 'awless revert [id]' to roll back the entire template run. This undoes all resources created in that execution, leveraging the logged actions for safety.

Awless vs Terraform for AWS management: which should I use?

Awless is better for quick, reversible deployments with offline analysis, while Terraform excels in stateful, incremental infrastructure management. Choose awless for simplicity and experimentation, Terraform for complex, production-grade workflows.

Can awless manage all AWS services like Lambda or DynamoDB?

Awless supports key infrastructure services (EC2, IAM, S3, etc.) but may not cover every AWS service. For full coverage, you might need to supplement with the official AWS CLI or other tools.

How does awless handle offline queries of my AWS resources?

Run 'awless sync' to fetch and store resources locally in a graph database. Then, use commands like 'awless show --local' to inspect properties and relationships without an active cloud connection.

Setting up smart SSH with awless for a private instance behind a jump host?

Use 'awless ssh instance-name --through jump-server', where awless resolves names from the local graph and configures SSH tunneling automatically, simplifying access to isolated instances.

Is awless suitable for large-scale production deployments?

While awless enforces security best practices and allows reverts, its lack of state management and experimental features may make it less ideal for critical, state-aware production environments compared to more mature IaC tools.

awless — Powerful AWS CLI Tool

What is awless?

Awless is a command line interface for managing Amazon Web Services that combines a powerful templating language with local graph synchronization. It simplifies infrastructure creation, exploration, and management by providing smart defaults, offline capabilities, and enriched resource relationships. The tool focuses on making AWS operations more intuitive and efficient for developers and operators.

Target Audience

DevOps engineers, cloud administrators, and developers who regularly manage AWS infrastructure via the command line and value automation, reproducibility, and offline analysis.

Value Proposition

Developers choose Awless for its unique combination of a simple templating language, local graph sync for offline work, and smart SSH connectivity. It reduces AWS management complexity by abstracting cryptic IDs, enforcing best practices, and providing powerful revert capabilities, all through a clean, hierarchical CLI.

A Mighty CLI for AWS

Use Cases

Best For

Creating and reverting AWS infrastructure using a simple templating language
Exploring and analyzing cloud resources and their relationships offline
SSH connectivity to AWS instances using resource names instead of IDs
Managing multi-region and multi-account AWS environments from the CLI
Enforcing security best practices and smart defaults in AWS deployments
Logging and rolling back infrastructure changes for safe experimentation

Not Ideal For

Teams requiring stateful infrastructure management with dependency tracking, as awless uses an all-or-nothing deployment model without persistent state files.
Projects needing exhaustive, up-to-date support for all AWS services, since awless is more infrastructure-centric and may lag behind AWS's rapid service releases.
Organizations standardized on cloud-native IaC ecosystems like AWS CDK or CloudFormation, which offer tighter AWS integration and larger community support.

Pros & Cons

Pros

Simple Templating Language

Awless provides a compiled templating language for creating and reverting complex AWS infrastructures with smart defaults, as demonstrated in templates like deploying a CockroachDB cluster.

Offline Resource Exploration

By syncing resources to a local graph storage, awless enables querying and inspecting AWS resources offline, allowing commands like 'awless list --local' to work without an internet connection.

Smart SSH Connectivity

The CLI simplifies SSH access by using resource names instead of cryptic IDs, with built-in support for jump hosts, as shown in examples like 'awless ssh my-instance --through jump-server'.

Action Logging and Revert

All CLI executions are logged, and any template or resource creation can be reverted via 'awless revert', providing a safety net for infrastructure changes and rollbacks.

Cons

No State Management

Awless admits it does not keep state of cloud resources, unlike tools like Terraform, which can complicate incremental updates and dependency management in complex environments.

Limited AWS Service Coverage

Focused on core infrastructure services, awless may not support all AWS services exhaustively, potentially requiring fallback to the official AWS CLI for newer or niche services.

Experimental Features

Components like community inspectors are marked as experimental in the README, indicating immaturity and potential instability for advanced analysis or production use.

Frequently Asked Questions

What is awless?

Target Audience

DevOps engineers, cloud administrators, and developers who regularly manage AWS infrastructure via the command line and value automation, reproducibility, and offline analysis.

Value Proposition

Use Cases

Best For

Creating and reverting AWS infrastructure using a simple templating language
Exploring and analyzing cloud resources and their relationships offline
SSH connectivity to AWS instances using resource names instead of IDs
Managing multi-region and multi-account AWS environments from the CLI
Enforcing security best practices and smart defaults in AWS deployments
Logging and rolling back infrastructure changes for safe experimentation

Not Ideal For

Teams requiring stateful infrastructure management with dependency tracking, as awless uses an all-or-nothing deployment model without persistent state files.
Projects needing exhaustive, up-to-date support for all AWS services, since awless is more infrastructure-centric and may lag behind AWS's rapid service releases.
Organizations standardized on cloud-native IaC ecosystems like AWS CDK or CloudFormation, which offer tighter AWS integration and larger community support.

Pros & Cons

Pros

Simple Templating Language

Awless provides a compiled templating language for creating and reverting complex AWS infrastructures with smart defaults, as demonstrated in templates like deploying a CockroachDB cluster.

Offline Resource Exploration

By syncing resources to a local graph storage, awless enables querying and inspecting AWS resources offline, allowing commands like 'awless list --local' to work without an internet connection.

Smart SSH Connectivity

The CLI simplifies SSH access by using resource names instead of cryptic IDs, with built-in support for jump hosts, as shown in examples like 'awless ssh my-instance --through jump-server'.

Action Logging and Revert

All CLI executions are logged, and any template or resource creation can be reverted via 'awless revert', providing a safety net for infrastructure changes and rollbacks.

Cons

No State Management

Awless admits it does not keep state of cloud resources, unlike tools like Terraform, which can complicate incremental updates and dependency management in complex environments.

Limited AWS Service Coverage

Focused on core infrastructure services, awless may not support all AWS services exhaustively, potentially requiring fallback to the official AWS CLI for newer or niche services.

Experimental Features

Components like community inspectors are marked as experimental in the README, indicating immaturity and potential instability for advanced analysis or production use.

Frequently Asked Questions

awless

What is awless?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

awless

What is awless?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?