fused-setuplisted

# Setting up fused > **Part of the Fused skill set.** This covers install + provisioning only. Once > set up, see **`fused-guide`** to route to the skill for the actual task > (`fused-projects`, `fused-widgets`, etc.). ## Overview Setup has four phases: 1. **Pre-flight** — verify AWS credentials and check for an existing install 2. **Install** — add the package 3. **Provision** — create an environment and AWS resources 4. **Verify** — confirm everything works before doing real work Never skip phase 1. Running `infra apply` or `env create` against the wrong account is hard to reverse. --- ## Phase 1 — Pre-flight checks ### 1a. Verify AWS credentials ```sh aws sts get-caller-identity ``` Expected output: ```json { "UserId": "AIDAQ...", "Account": "123456789012", "Arn": "arn:aws:iam::123456789012:user/yourname" } ``` **If this fails**: credentials are missing or expired. Fix before continuing: - AWS SSO: `aws sso login --profile <profile>` - Static credentials: ensure `~/.aws/credentials` or `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` are set - Instance/container role: verify the metadata endpoint is accessible **Confirm the Account ID is correct** before proceeding. Provisioning into the wrong account will leave orphaned resources. ### 1b. Check for an existing fused installation ```sh fused env list ``` - If the command is not found: fused is not installed → proceed to Phase 2. - If it runs but shows no environments: fused is installed but not conf