pulumi insights account new | CLI commands

[EXPERIMENTAL] Create a new Insights account

Synopsis

[EXPERIMENTAL] Create a new Pulumi Insights account.

An Insights account represents a cloud provider account (e.g. AWS, Azure, GCP, OCI, Kubernetes) configured for resource discovery.

pulumi insights account new <name> [flags]

Examples

  # Walk through prompts to create an account
  pulumi insights account new prod-aws

  # Create an AWS Insights account using credentials from an ESC environment
  pulumi insights account new prod-aws \
      --provider aws --environment infra/prod-aws-creds

  # Override the organization and schedule a daily scan
  pulumi insights account new prod-aws --org acme \
      --provider aws --environment infra/prod-aws-creds \
      --scan-schedule daily

  # Pass provider-specific configuration as inline JSON
  pulumi insights account new prod-aws \
      --provider aws --environment infra/prod-aws-creds \
      --provider-config '{"regions":["us-east-1","us-west-2"]}'

Options

      --agent-pool-id string     ID of the agent pool to run discovery workflows (defaults to the org's default pool)
      --environment string       ESC environment containing provider credentials, in the form project/environment with an optional @version suffix
  -h, --help                     help for new
      --org string               Organization that will own the Insights account (defaults to the current default org)
      --output string            Output format. Supported values are: default and json (default "default")
      --provider string          Cloud provider for the account. One of: aws, gcp, azure-native, oci, kubernetes
      --provider-config string   Provider-specific configuration as an inline JSON object (e.g. '{"regions":["us-east-1"]}')
      --scan-schedule string     Automated scan schedule. One of: none, 12h, daily
  -y, --yes                      Skip prompts; fail if any required value is missing

Options inherited from parent commands

      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
  -Q, --fully-qualify-stack-names    Show fully-qualified stack names
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
      --non-interactive              Disable interactive mode for all commands
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

SEE ALSO

• pulumi insights account - [EXPERIMENTAL] Manage Pulumi Insights accounts