Usage: localstack auth clear-token [OPTIONS]
Options:
  -h, --help  Show this message and exit.

Usage: localstack auth set-token [OPTIONS] AUTH_TOKEN
Set up your auth token to activate your LocalStack for AWS license.
This differs from localstack auth login, which is used for platform features such as syncing Cloud Pods with your web account.
  The auth token you configure here will be passed to the
  `LOCALSTACK_AUTH_TOKEN` environment variable of the LocalStack container
  when you run `localstack start`.
  AUTH_TOKEN: Your Localstack auth token that you can find in
  https://app.localstack.cloud.
Options:
  -h, --help  Show this message and exit.

Usage: localstack auth show-token [OPTIONS]
  Show the token that LocalStack picks up from your environment. This can
  either be the auth token set via `localstack auth set-token`, or the value
  of `LOCALSTACK_AUTH_TOKEN`.
Options:
  --plain     Setting this flag will output only the value of the token in
              plain text, so it can be used as input to other programs, like
              `LOCALSTACK_AUTH_TOKEN=$(localstack auth show-token --plain)`.
  -h, --help  Show this message and exit.

Usage: localstack auth login [OPTIONS]
  Login to the LocalStack Platform.
  This command performs a login to your LocalStack account, giving you access
  to features that require platform permissions, such as uploading cloud pods
  to your account.
  This command is deprecated and it will be removed soon. To use LocalStack
  features that requires authentication to the LocalStack platform (e.g.,
  Cloud Pods), please run `localstack auth set-token <AUTH_TOKEN>`, or set the
  environment variable `LOCALSTACK_AUTH_TOKEN` to a valid auth token.
  (DEPRECATED)
Options:
  -u, --username USER  Username (email address) for login  [required]
  -p, --password PWD   Password for login  [required]
  -h, --help           Show this message and exit.

Usage: localstack auth logout [OPTIONS]
  Log out from the LocalStack Platform.
  This command performs a logout from the LocalStack platform and deletes all
  session information on your machine. (DEPRECATED)
Options:
  -h, --help  Show this message and exit.

Usage: localstack config show [OPTIONS]
  Print the current LocalStack config values.
  This command prints the LocalStack configuration values from your
  environment. It analyzes the environment variables as well as the LocalStack
  CLI profile. It does _not_ analyze a specific file (like a docker-compose-
  yml).
Options:
  -f, --format [table|plain|dict|json]
                                  The formatting style for the command output.
                                  [default: table]
  -h, --help                      Show this message and exit.

Usage: localstack config validate [OPTIONS]
  Validate your LocalStack configuration (docker compose).
  This command inspects the given docker-compose file (by default docker-
  compose.yml in the current working directory) and validates if the
  configuration is valid.
  It will show an error and return a non-zero exit code if:
  - The docker-compose file is syntactically incorrect.
  - If the file contains common issues when configuring LocalStack.
Options:
  -f, --file PATH  Path to compose file  [default: docker-compose.yml]
  -h, --help       Show this message and exit.

Usage: localstack status docker [OPTIONS]
  Query information about the currently running LocalStack Docker image, its
  container, and the LocalStack runtime.
Options:
  -f, --format [table|plain|dict|json]
                                  The formatting style for the command output.
                                  [default: table]
  -h, --help                      Show this message and exit.

Usage: localstack status services [OPTIONS]
  Query information about the services of the currently running LocalStack
  instance.
Options:
  -f, --format [table|plain|dict|json]
                                  The formatting style for the command output.
                                  [default: table]
  -h, --help                      Show this message and exit.

Usage: localstack update all [OPTIONS]
  Update all LocalStack components.
  This is the same as executing `localstack update localstack-cli` and
  `localstack update docker-images`. Updating the LocalStack CLI is currently
  only supported if the CLI is installed and run via Python / PIP. If you used
  a different installation method, please follow the instructions on
  https://docs.localstack.cloud/.
Options:
  -h, --help  Show this message and exit.

Usage: localstack update docker-images [OPTIONS]
  Update all Docker images LocalStack depends on.
  This command updates all Docker LocalStack docker images, as well as other
  Docker images LocalStack depends on (and which have been used before / are
  present on the machine).
Options:
  -h, --help  Show this message and exit.

Usage: localstack update localstack-cli [OPTIONS]
  Update the LocalStack CLI.
  This command updates the LocalStack CLI. This is currently only supported if
  the CLI is installed and run via Python / PIP. If you used a different
  installation method, please follow the instructions on
  https://docs.localstack.cloud/.
Options:
  -h, --help  Show this message and exit.

Usage: localstack aws iam [OPTIONS] COMMAND [ARGS]...
  Access LocalStack IAM features.
  This command provides tools to make it easier to write IAM policies for your
  cloud application.
Options:
  -h, --help  Show this message and exit.
Commands:
  stream   Stream policies for all requests enforced on LocalStack
  summary  Summary of policies for all requests enforced on LocalStack

Usage: localstack dns systemd-resolved [OPTIONS]
  Manage the LocalStack DNS configuration using systemd-resolved (Ubuntu,
  Debian, etc.).
  This command sets (or reverts) the LocalStack DNS, running in the current
  LocalStack runtime, in systemd-resolved for the docker network interface.
  Most current Linux systems - like Ubuntu, Debian, or Fedora - use systemd-
  resolved for the network name resolution.
Options:
  -s, --set / -r, --revert  Set or revert DNS settings  [default: set]
  -h, --help                Show this message and exit.

Usage: localstack ephemeral create [OPTIONS]
  Create a new ephemeral LocalStack instance in the cloud.
  Specify an instance name and optional parameters like lifetime and
  environment variables. The instance will be created with the specified
  configuration and its connection details will be returned.
  Examples:
      localstack ephemeral create --name my-test-instance
      localstack ephemeral create --name my-instance --lifetime 60
      localstack ephemeral create --name my-instance --env DEBUG=1
Options:
  --name TEXT         Name of the ephemeral instance  [required]
  --lifetime INTEGER  Lifetime of the instance in minutes
  -e, --env TEXT      Additional environment variables that are passed to the
                      LocalStack instance
  -h, --help          Show this message and exit.

Usage: localstack ephemeral delete [OPTIONS]
  Delete a specific ephemeral LocalStack instance.
  Specify the name of the instance you want to delete. Once deleted, the
  instance cannot be recovered.
  Example:
      localstack ephemeral delete --name my-test-instance
Options:
  --name TEXT  Name of the ephemeral instance to delete  [required]
  -h, --help   Show this message and exit.

Usage: localstack ephemeral list [OPTIONS]
  List all available ephemeral LocalStack instances.
  This command shows all ephemeral instances associated with your account,
  including their names, status, and other relevant details.
  Examples:
      localstack ephemeral list
Options:
  -h, --help  Show this message and exit.

Usage: localstack ephemeral logs [OPTIONS]
  Fetch logs from a specific ephemeral LocalStack instance.
  Retrieve the logs of a running ephemeral instance by specifying its name.
  The logs are returned in chronological order.
  Example:
      localstack ephemeral logs --name my-test-instance
Options:
  --name TEXT  Name of the ephemeral instance to fetch logs from  [required]
  -h, --help   Show this message and exit.

Usage: localstack extensions dev [OPTIONS] COMMAND [ARGS]...
  Developer tools for developing LocalStack extensions.
Options:
  -h, --help  Show this message and exit.
Commands:
  disable  Disables an extension on the host for developer mode.
  enable   Enables an extension on the host for developer mode.
  list     List LocalStack extensions for which dev mode is enabled.
  new      Create a new LocalStack extension from the official extension...

Usage: localstack extensions init [OPTIONS]
  Initialize the LocalStack extensions environment.
  The environment variable `LOCALSTACK_VOLUME_DIR` currently defaults to
  ~/.cache/localstack, where the extension environment will be installed into
  ./lib/extensions/
Options:
  -h, --help  Show this message and exit.

Usage: localstack extensions install [OPTIONS] NAME
  Install a LocalStack extension.
  This command installs a LocalStack extension, where the name can be any
  valid pip dependency identifier. Additionally, we support the installation
  of distribution files from disk, which you can indicate by a ``file://``
  prefix in the name
  Example invocations:
      localstack extensions install localstack-extension-stripe
      localstack extensions install "git+https://github.com/localstack/localstack-stripe.git#egg=localstack-stripe"
      localstack extensions install file://./dist/localstack-extension-hello-world-0.1.0.tar.gz
      localstack extensions install file://.  # assumes the current directory is a source distribution
Options:
  -h, --help  Show this message and exit.

Usage: localstack extensions list [OPTIONS]
  List installed extension.
  The environment variable `LOCALSTACK_VOLUME_DIR` currently defaults to
  ~/.cache/localstack, where the extension environment will be installed into
  ./lib/extensions/
Options:
  -h, --help  Show this message and exit.

Usage: localstack extensions uninstall [OPTIONS] NAME
  Remove a LocalStack extension.
  This command removes a previously installed LocalStack extension, where the
  name can be any valid package name.
  Example invocations:
      localstack extensions uninstall localstack-extension-stripe
Options:
  -h, --help  Show this message and exit.

Usage: localstack license activate [OPTIONS]
Options:
  -h, --help  Show this message and exit.

Usage: localstack license info [OPTIONS]
Options:
  -h, --help  Show this message and exit.

Usage: localstack pod delete [OPTIONS] NAME [REMOTE]
  Delete a Cloud Pod registered on a remote (by default, the LocalStack
  platform).
  This command will remove all the versions of a Cloud Pod, and the operation
  is not reversible.
Options:
  -h, --help  Show this message and exit.

Usage: localstack pod list [OPTIONS] [REMOTE]
  List all the Cloud Pods available for a single user, or for an entire
  organization, if the user is part of one.
  With the --public flag, it lists the all the available public Cloud Pods. A
  public Cloud Pod is available across the boundary of a user and/or
  organization. In other words, any public Cloud Pod can be injected by any
  other user holding a LocalStack for AWS license.
Options:
  -p, --public               List all the available public Cloud Pods
  -m, --mine                 List only the Cloud Pods created by the current
                             user
  -f, --format [table|json]  The formatting style for the list pods command
                             output.  [default: table]
  -h, --help                 Show this message and exit.

Usage: localstack pod load [OPTIONS] NAME [REMOTE]
  Load the state of a Cloud Pod into the application runtime. Users can import
  Cloud Pods from different remotes, with the LocalStack platform being the
  default one. Users can also load a specific version by appending a version
  number to the pod name after a colon (e.g., `localstack pod load my-pod:3`).
  If not specified, the latest version will be loaded. Use the `localstack pod
  versions` to list all the available versions.
  Loading the state of a Cloud Pod into LocalStack might cause some conflicts
  with the current state of the container. LocalStack will attempt a best-
  effort merging strategy between the current state and the one from the Cloud
  Pod. For a service X present in both the current state and the Cloud Pod, we
  will attempt to merge states across different accounts and regions. If the
  service X has a state for the same account and region both in the running
  container and the Cloud Pod, the latter will be used. If a service Y is
  present in the running container but not in the Cloud Pod, it will be left
  untouched. This is the default merge strategy which is activated by either
  the `--strategy account-region-merge` option or by omitting the `--strategy`
  option at all.
  In addition to the default one, LocalStack provides two more strategies:
  - overwrite, in which the state of LocalStack is completely reset before loading the state from the Cloud Pod.
  This strategy is activated with the `--strategy overwrite` option .
  - service-merge: in which LocalStack merges the state of a service under the same account and region when
  there is no resource overlap. In such a case, the loaded resources are preferred.
  This option is activated with the `--strategy service-merge` option.
  To load a local copy of a LocalStack state, you can use the 'localstack
  state import' command.
Options:
  -s, --secret TEXT               Secret for the Cloud Pod encryption.
                                  Encryption is an Enterprise only feature.
  --strategy [overwrite|account-region-merge|service-merge]
                                  The merge strategy to adopt when loading the
                                  Cloud Pod.  [default: account-region-merge]
  -y, --yes                       Automatic yes to prompts. Assume a positive
                                  answer to all prompts and run non-
                                  interactively.
  --dry-run                       Checks the resources added or modified in
                                  the application runtime by loading a Cloud
                                  Pod.
  -h, --help                      Show this message and exit.

Usage: localstack pod remote [OPTIONS] COMMAND [ARGS]...
  Manage cloud pod remotes
Options:
  -h, --help  Show this message and exit.
Commands:
  add     Add a remote
  delete  Delete a remote
  list    Lists the available remotes

Usage: localstack pod save [OPTIONS] NAME [REMOTE]
  Save the current state of the LocalStack container in a Cloud Pod.
  A Cloud Pod can be registered and saved with different storage options,
  called remotes. By default, Cloud Pods are hosted in the LocalStack
  platform. However, users can decide to store their Cloud Pods in other
  remotes, such as AWS S3 buckets or ORAS registries.
  An optional message can be attached to any Cloud Pod. Furthermore, one could
  decide to export only a subset of services with the optional --services
  option.
  To use the LocalStack platform for storage, the desired Cloud Pod's name will suffice, e.g.:
  localstack pod save <pod_name>
  Please be aware that each following save invocation with the same name will
  result in a new version being created.
  To save a local copy of your state, you can use the 'localstack state export' command.
Options:
  -m, --message TEXT             Add a comment describing this Cloud Pod's
                                 version
  -s, --services TEXT            Comma-delimited list of services to push in
                                 the Cloud Pod (all by default)
  --visibility [public|private]  Set the visibility of the Cloud Pod [`public`
                                 or `private`]. Does not create a new version
  -S, --secret TEXT              Secret for the Cloud Pod encryption.
                                 Encryption is an Enterprise only feature.
  -f, --format [json]            The formatting style for the save command
                                 output.
  -h, --help                     Show this message and exit.

Usage: localstack pod versions [OPTIONS] NAME
  List all available versions for a Cloud Pod
  This command lists the versions available for a Cloud Pod. Each invocation
  of the save command is going to create a new version for a named Cloud Pod,
  if a Pod with such name already does exist in the LocalStack platform.
Options:
  -f, --format [table|json]  The formatting style for the version command
                             output.  [default: table]
  -h, --help                 Show this message and exit.

Usage: localstack replicator resources [OPTIONS]
Options:
  -h, --help  Show this message and exit.
*** Preview Feature ***
This feature is currently in preview mode in our Teams offering and it's availability may change in future releases.

Usage: localstack replicator start [OPTIONS]
  Starts a job to replicate an AWS resource into localstack. You must have
  credentials with sufficient read access to the resource trying to replicate.
  At the moment only environment variables are recognized.
  `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_DEFAULT_REGION` must
  be set. `AWS_ENDPOINT_URL` and `AWS_SESSION_TOKEN` are optional.
Options:
  --replication-type [MOCK|SINGLE_RESOURCE|BATCH]
                                  Type of replication job: MOCK,
                                  SINGLE_RESOURCE, BATCH  [default:
                                  SINGLE_RESOURCE]
  --resource-arn TEXT             ARN of the resource to recreate. Optional
                                  for SINGLE_RESOURCE replication
  --resource-type TEXT            CloudControl type of the resource to
                                  recreate. Optional for SINGLE_RESOURCE
                                  replication
  --resource-identifier TEXT      CloudControl identifier of the resource to
                                  recreate. Mandatory if --resource-type is
                                  used
  --target-account-id TEXT        Localstack account ID where the resources
                                  will be replicated. Defaults to
                                  000000000000. See <docs> to enable same
                                  account replication
  --target-region-name TEXT       Localstack region where the resources will
                                  be replicated. Only provide if different
                                  than source AWS account.
  --delay TEXT                    Delay for the MOCK replication work
  -h, --help                      Show this message and exit.
*** Preview Feature ***
This feature is currently in preview mode in our Teams offering and it's availability may change in future releases.