Configuration¶
This page shows the CrewAI directories, the Bedrock permission, and the offline fixture. The starter does not read a customer config file for the supplied two-agent task.
Where things live¶
| Path | What it is |
|---|---|
/opt/crewai/ |
CrewAI 1.15.28 and its Python 3.12 environment. Root-owned. |
/home/ubuntu/crewai-workspace/ |
Workspace created on first boot, mode 0700. |
/home/ubuntu/crewai-results/ |
One directory per run, mode 0700. |
/etc/crewai/ |
Instance identity. Preserved across restarts. |
/opt/sushi/docs/demo.sh |
Real-model walkthrough. |
/opt/sushi/docs/README.md |
Image notes. |
/usr/share/doc/crewai/ |
Dependency notices, including native components. |
/opt/crewai/sources/ |
Source archives. |
/opt/sushi/evidence/ |
Installed inventories. |
sushi-crewai-firstboot is a one-shot unit. After success, its status is
active (exited). It does not wipe an existing workspace.
Amazon Bedrock¶
The default demo calls Amazon Nova Lite in us-east-1. Attach an instance
profile that allows:
Keep IMDSv2 reachable by ubuntu. The process takes temporary credentials
from the instance role. It does not read a local AWS key file, and it does
not write credentials into the result directory.
Each run makes 2 to 8 model calls. Each HTTP request times out after 60 seconds. The run stops at eight calls.
Offline fixture¶
This command runs the same two-agent shape without a model charge. It writes
a new result directory and records offline-fixture in the manifest.
sudo -iu ubuntu bash -c 'sushi-crewai self-test --output "/home/ubuntu/crewai-results/fixture-$(date +%s)-$(cat /proc/sys/kernel/random/uuid)"'
That result shows local execution only. It does not prove that Bedrock is
reachable or that a model response was good. sushi-crewai read ...
--require-provider rejects this manifest on purpose.
Tools you cannot widen from the starter¶
The analyst's only tool is sum_sales_csv for the current dataset. It does
not open other paths, execute code, or use the network. The reporter has no
tools. Code execution, delegation, memory, planning, telemetry, and hosted
tracing stay off.
boto3 and the other optional CrewAI extras are not installed. Adding an
integration means installing and reviewing that dependency yourself. The
pinned environment under /opt/crewai/ is the tested build.
Last updated October 27, 2026 · Suggest an improvement