# systems · systems.sh
Cloud Deployment
Cloud deployment tasks on AWS, Azure or GCP, matched to your course's platform.
Cloud assignments are easy to over-provision by accident, and a leftover instance billing quietly after your demo is a bad surprise for a student account. We deploy exactly what the brief needs, document the setup, and hand over a teardown script so nothing keeps running once you've submitted.
What you get
- Deployed on the exact provider your brief names, not a substitute
- Infrastructure documented — what's running, and why
- Cost-aware setup, so a demo environment doesn't rack up charges
- Security groups and access set deliberately, not left open
- A teardown script included so nothing keeps billing after your demo
- A short architecture diagram for your report
What to send first
- The lab sheet or brief, including the topology or architecture diagram
- The tools required (Packet Tracer, GNS3, AWS, Azure, Docker, GitHub Actions…)
- What evidence the marker wants — configs, screenshots, logs, a report
- Access details only if the brief requires your own account (never your university login)
How it runs
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Cloud Deployment: common questions
Usually not — we build in our own environment and hand over the configuration, infrastructure code and evidence. If the brief insists on your account, we agree scoped access first. We never ask for your university login.
Yes. Evidence is captured as the work is done, labelled to match the brief's tasks, so the report and the submission line up.
It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.
Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.
// related
Often paired with cloud deployment
Networking Configuration
Network design and configuration tasks — subnetting, routing and the diagram to match.
systems.shCybersecurity Reports
Vulnerability assessments and security reports, written to a professional standard.
systems.shCI/CD Pipelines
CI/CD pipelines built to automate the build-test-deploy cycle your brief describes.
./send-brief
Send your brief.
Paste the cloud deployment brief into WhatsApp — the message already names the service. Scope and price come back in writing.