Skip to content
stack
Get started
Provider · Cloud

AWS — Ashlr Stack Provider

AWS: S3, Lambda, RDS. IAM access keys stored in Phantom. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Cloud · API key KEY-ONLY · supplied credential attachment
AWS — S3, Lambda, RDS. IAM access keys stored in Phantom.
Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results. 

stack add aws

Or retrieve catalog matches for what you're building via stack recommend: 

stack recommend "raw cloud infrastructure for scale"

Auth flow

Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.

How-to: Create an IAM access key pair in the AWS console and paste both halves.

Secret slots

stack add aws has these 3 catalog secret slots; verify which values its adapter actually materializes through Phantom:

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_REGION

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

  • GCP — Google Cloud Platform. Service-account JSON + project ID stored in Phantom.
  • DigitalOcean — Droplets, Kubernetes, managed databases. Personal access token verified via /v2/account.
  • Hetzner — Affordable European cloud servers. API token verified via /v1/locations.

Catalog notes

v1 stores the keys only — no resource provisioning. Scope the IAM policy narrowly.

FAQ

Do I need a AWS account to use it with Stack?

Use an existing AWS account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://console.aws.amazon.com and supply the required inputs; inspect verification and persistence results.

Where does Stack store my AWS credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove aws` for local AWS configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying AWS credentials through https://console.aws.amazon.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.

Outbound