Getting started¶
Launch Gitea Git hosting in your AWS account, connect privately and verify the result of your first task.
1. Launch and wait for startup¶
Use the Software Sushi Marketplace version described on this page, Ubuntu 24.04 x86_64, and at least t3.small / 2 GiB RAM with 24 GiB encrypted gp3 root storage. Keep IMDSv2 enabled. These are minimum starting sizes, not throughput benchmarks. Inbound application ports must remain closed.
For Session Manager, attach a customer-owned instance role with the required Systems Manager permissions and provide outbound HTTPS/DNS connectivity to the relevant endpoints. Your workstation needs AWS CLI, the Session Manager Plugin and permission to start sessions. SSH is an alternative when TCP 22 is restricted to your administrative CIDR. The application itself does not need a model-provider key.
Connect to your instance, then run the following. The second command starts a login shell as ubuntu; run the remaining commands inside that shell.
sudo cloud-init status --wait
sudo -iu ubuntu
umask 077
sudo systemctl is-active gitea.service
bash /opt/sushi/docs/demo.sh
Wait for cloud-init to finish and every listed service to report active. The demo checks the installed service; it does not validate your own data or workload. A failed service needs diagnosis before you submit work. Do not recreate the instance identity or run a second server to bypass a startup failure.
2. Use the private connection¶
First boot creates a unique TLS identity and ~/.config/sushi/gitea/access.json for the ubuntu account, with mode 0600. The matching server.crt sits beside it. The installed sushi-gitea-api helper reads these files and verifies TLS without printing credentials. Run it on the instance as ubuntu.
To reach port 8443 from your own workstation, open a separate terminal and replace the placeholders below with your customer profile, Region and instance ID:
aws --profile <customer-profile> --region <region> ssm start-session \
--target <instance-id> \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["8443"],"localPortNumber":["8443"]}'
Keep that terminal open. Forwarding a port does not install the API helper on your workstation or copy its identity files. For a workstation client, transfer only the required certificate and private client file through an authenticated channel, retain private permissions and configure the client to read credentials from that file. Do not put credentials in URLs, command arguments, user data or support logs. Do not disable certificate verification.
3. Create a private repository¶
The installed API helper authenticates as the generated administrator without printing its credentials. This creates a uniquely named private repository and independently rereads its metadata.
Run in a new private working directory as ubuntu. The commands write requests and responses there; retain or securely remove them according to your data policy.
REPO="customer-example-$(python3 -c 'import uuid; print(uuid.uuid4().hex)')"
export REPO
python3 - <<'PYGIT'
import json, os
from pathlib import Path
Path('repo.json').write_text(json.dumps({
'name': os.environ['REPO'], 'private': True, 'auto_init': True}))
PYGIT
sushi-gitea-api POST /api/v1/user/repos --input repo.json > repo-created.json
sushi-gitea-api GET "/api/v1/repos/sushi/$REPO" > repo-readback.json
python3 - <<'PYGIT'
import json, os
from pathlib import Path
result = json.loads(Path('repo-readback.json').read_text())
assert result['private'] is True and result['name'] == os.environ['REPO']
print('Private repository verified:', result['full_name'])
PYGIT
For the native web interface, forward port 8443, verify the server certificate copied from this exact instance over an authenticated channel, and open the forwarded HTTPS endpoint. Retrieve the generated account only through your private instance session; keep populated login fields out of recordings. Do not accept an unexpected certificate or disable verification.
For Git clone/push, the installed /opt/sushi/docs/README.md documents the certificate and private credential-helper pipe. Run that helper only through Git; running it directly prints a secret. Create an issue and pull request, inspect the diff and merge your own test change. After reboot, reload the issue and merged pull request, then clone into a fresh directory and compare the committed content. This checks persistence as well as repository creation.
Package limits. One instance with local repositories and SQLite. Registration, SSH Git hosting, LFS, Actions and the mailer are disabled. No external database, high availability, public hostname or DNS automation is configured. The generated administrator is sushi.
The fuller walkthrough and installed operating notes are in /opt/sushi/docs/DEMO.md and /opt/sushi/docs/README.md. These describe this package’s API and defaults. General upstream examples may use different endpoints or include features outside this package.
Last updated October 17, 2026 · Suggest an improvement