Set up AWS Emulator on this VM by following the exe.dev recipe at https://exe.dev/deploy/aws-emulator.md from top to bottom.

The recipe's example VM name is my-aws-emulator. This VM's name is the output of `hostname`: use it wherever the recipe writes my-aws-emulator. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- AWS Emulator from AWS's package, running as `exedev` on 127.0.0.1:9297, back after a reboot
- The emulator's usage telemetry turned off
- The AWS CLI, and `~/aws-emulator.env`, which points the CLI and SDKs at the emulator
- `aws sts get-caller-identity` answers with the emulator's account, 000000000000
- Claude Code, Codex and Pi using exe.dev's LLM integration, with AWS's aws-emulator skill
- A Git project at `~/project` whose AGENTS.md tells agents to use the emulator, never real AWS

Run the VM-side commands in "Set up the VM" only; skip creating the VM.
If `exeuntu configure` reports an existing user config, leave it alone.
If `~/project` or its AGENTS.md already exists, add the AWS section to
it instead of replacing it. Never put real AWS credentials on this VM,
never bind the emulator to anything but 127.0.0.1, never run it with
`--auth off`, and never expose port 9297 through the HTTPS proxy.
Verify with the checks at the end of that section: the service is
active, the health check prints `ok`, the log says telemetry is
disabled, and `aws sts get-caller-identity` shows account 000000000000. Then run the demo in "Try it" once to prove
S3, DynamoDB and Lambda work. Skip the later sections and the FAQ.
Finish by telling the owner that everything in the emulator lives in
memory and is gone when the service restarts.

Finish with the URLs I should open.