AWS Systems Manager Parameter Store Provider

Note

The AWS Systems Manager Parameter Store provider is available in SecretSpec 0.18+.

The AWS Parameter Store provider stores secrets as encrypted SecureString parameters.

At a glance

Provider	awsps (0.18+)
URI	awsps://[AWS_PROFILE@]REGION[?options]
Access	Read and write; parameter references are read-only
Best for	AWS workloads using Parameter Store for application configuration
Authentication	Standard AWS SDK credential chain
Build feature	awsps (0.18+)
Default storage	/secretspec/{project}/{profile}/{key}

Quick start

# Set an encrypted parameter
$ secretspec set DATABASE_URL --provider awsps://us-east-1
Enter value for DATABASE_URL: postgresql://localhost/mydb
✓ Secret 'DATABASE_URL' saved to awsps (profile: default)

# Get it back
$ secretspec get DATABASE_URL --provider awsps://us-east-1
postgresql://localhost/mydb

# Run with parameters
$ secretspec run --provider awsps://us-east-1 -- npm start

Setup

Prerequisites

• An AWS account with Systems Manager Parameter Store enabled
• IAM permission to read and write the target parameter hierarchy
• Build with --features awsps using SecretSpec 0.18+

Authentication

The provider uses the standard AWS SDK credential chain, including:

1. AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and optional AWS_SESSION_TOKEN
2. Shared AWS config and credentials files
3. IAM Identity Center (SSO) sessions
4. ECS task roles, EC2 instance profiles, and other workload identities

Set a shared-config profile before the region in the URI:

awsps://production@us-east-1

When the profile and region are omitted, the SDK resolves both from its ordinary environment and shared-config chains:

awsps

Configuration

URI format

awsps://[AWS_PROFILE@]REGION[?prefix=PREFIX][&kms_key_id=KEY][&tier=TIER]

• AWS_PROFILE: Optional profile from the shared AWS config.
• REGION: Optional AWS region. If omitted, the SDK region chain is used.
• prefix: Optional hierarchy before /secretspec. A leading slash is optional and normalized.
• kms_key_id: Optional customer-managed KMS key ID, ARN, or alias used for SecureString writes. If omitted, Parameter Store uses the account’s default key.
• tier: Optional standard, advanced, or intelligent-tiering value. Omitting it uses the account’s Parameter Store default tier.

URI examples

awsps://us-east-1
awsps://production@us-east-1
awsps://us-east-1?prefix=/myteam
awsps://us-east-1?kms_key_id=alias/my-key&tier=advanced
awsps://

Project configuration

secretspec.toml

[providers]
parameters = "awsps://production@us-east-1?prefix=/myteam&kms_key_id=alias/parameter-store"

[profiles.production]
DATABASE_URL = { description = "Database URL", providers = ["parameters"] }

Storage model

Convention secrets are stored at [/prefix]/secretspec/{project}/{profile}/{key}. For example, DATABASE_URL in project myapp and profile production maps to:

/secretspec/myapp/production/DATABASE_URL

With ?prefix=/myteam, it maps to:

/myteam/secretspec/myapp/production/DATABASE_URL

Every value SecretSpec creates is a SecureString. Writes set Overwrite=true, so updating a value creates a new Parameter Store version. Parameter Store retains its normal version history.

Standard parameters accept values up to 4 KB; advanced parameters accept up to 8 KB and incur AWS charges. A standard parameter can be promoted to advanced, but Parameter Store does not downgrade an advanced parameter in place.

Caution

SecretSpec does not change an existing parameter from String or StringList to SecureString. Parameter Store rejects that type change; create a new encrypted parameter or migrate the existing parameter first.

Use existing parameters

In SecretSpec 0.18+, a secret’s ref field can name an existing Parameter Store parameter. item is its full name or ARN. The optional version is appended as a Parameter Store selector and may be a numeric version or label. References are read-only.

[profiles.production]
# Latest value
DATABASE_URL = { description = "DB", ref = { item = "/prod/database-url" }, providers = ["awsps://us-east-1"] }

# Version 7
SIGNING_KEY = { description = "Signing key", ref = { item = "/prod/signing-key", version = "7" }, providers = ["awsps://us-east-1"] }

# Version carrying the "current" label
API_TOKEN = { description = "API token", ref = { item = "/prod/api-token", version = "current" }, providers = ["awsps://us-east-1"] }

Cross-account shared parameters must be read by ARN. SecretSpec still writes only to its convention hierarchy in the provider’s configured account and region.

IAM permissions

Reads require ssm:GetParameter and ssm:GetParameters; convention writes require ssm:PutParameter. A customer-managed KMS key also needs the corresponding KMS permissions for encryption and decryption.

Scope IAM resources to the configured hierarchy where possible. For the /myteam/secretspec/ prefix in us-east-1, that resource pattern is:

arn:aws:ssm:us-east-1:ACCOUNT_ID:parameter/myteam/secretspec/*

CI/CD

Prefer an AWS workload identity or short-lived OIDC credentials:

$ export AWS_REGION=us-east-1
$ secretspec run --provider awsps -- deploy