Supporting contribution

SAF Sky Quest

Supporting case study

Rapid AWS hosting and event-infrastructure delivery for a Sustainable Aviation Fuel education quiz.

Role: Cloud delivery and event infrastructure — AWS Lightsail, domain/HTTPS, activation operations, runtime-data export, and decommissioning
Context: AIRBUS EDUCATIONAL EXHIBITION IN THAILAND
Period: 15–25 August 2026

Summary

SAF Sky Quest was a rapid cloud-deployment engagement for an Airbus educational activation in Thailand from 15–25 August 2026. The gamified quiz introduced primary- and secondary-school audiences to Sustainable Aviation Fuel and common recyclable/biofuel feedstock concepts. Participants scoring at least 8/10 were eligible for event rewards.

Event context

The activation used a finished quiz application as a short-lived event service. The frontend application was developed by another developer. My responsibility was to get the application hosted, reachable over its custom domain, and ready for operation during the event without presenting the frontend build as my work.

Delivery lifecycle

Deployment lifecycle · supporting case study

From finished app to event closeout

Hydar's rapid hosting and event-infrastructure lifecycle for the SAF Sky Quest activation.

Read this visual as text

A three-stage SAF Sky Quest deployment lifecycle groups six steps: receive the finished frontend application and deploy it to AWS Lightsail; configure a custom domain and Caddy HTTPS and operate during the Thailand activation; export runtime data and decommission the infrastructure. The frontend was developed by another developer; Hydar owned cloud delivery and event operations.

Hydar received the finished frontend application from another developer and deployed it to AWS Lightsail.
He configured the custom domain and Caddy HTTPS and operated the service during the Thailand activation.
He exported runtime data and decommissioned the event infrastructure after the activation.

I received the finished application, deployed it to AWS Lightsail, configured the custom domain and Caddy HTTPS, operated the service during the activation, exported runtime data, and decommissioned the event infrastructure afterward.

Event closeout

The approved public measure is 29 registration records captured. This count describes runtime records captured by the event service; it is not a count of students, schools, or unique users because the underlying Thai registration data has not been interpreted sufficiently to establish identity or uniqueness.

Ownership and limitations

The frontend application belonged to another developer. I owned the rapid hosting and event-infrastructure path: AWS Lightsail deployment, custom-domain and Caddy HTTPS configuration, activation operations, runtime-data export, and decommissioning. This supporting case study does not publish runtime data, participant identities, internal URLs, infrastructure identifiers, credentials, or unsupported event-impact claims.