Presentation Script

Good morning. My name is Haider Nousher, and my student

ID is 26008510. Today, I will present my cloud-native medical
imaging application designed using AWS services for the CSC-
44110 Data Management and Cloud Technologies assignment.

For the first task, I will explain the cloud service models—
Infrastructure as a Service, Platform as a Service, and Software
as a Service—and demonstrate how they support my proposed
medical imaging application.

Slide 1

Speaker Notes (Approximately 55–60 Seconds)

Task 1 introduces the three cloud service models used within the proposed
medical imaging application. Infrastructure as a Service is implemented
using Amazon EC2, which provides virtual servers to host the web application
and specialised diagnostic software. This approach offers the flexibility
required by healthcare organisations while allowing administrators to
configure security and operating systems according to organisational
requirements. Platform as a Service is represented by AWS Lambda, which
automatically executes tasks such as processing uploaded medical images,
extracting metadata and notifying clinicians without requiring server
management. Finally, the completed application is delivered as a Software as
a Service solution, enabling authorised healthcare professionals to securely
access patient records and diagnostic images through a web browser.
Combining these three service models creates a cloud-native architecture
that achieves high scalability, operational efficiency, strong security and an
improved user experience.
Slide 2

Task 2 – Speaker Notes (Approximately 2 Minutes)

This diagram presents the overall architecture of the proposed cloud-native

medical imaging application developed using Amazon Web Services. The
architecture is designed to provide secure, scalable and reliable access to
patient information, diagnostic reports and medical images for authorised
healthcare professionals.

The workflow begins when doctors, radiologists, hospital staff or authorised

patients access the application through a web browser. Their requests are
first directed to Amazon Route 53, which provides reliable Domain Name
System, or DNS, services and routes users to the application endpoint. The
requests are then forwarded to an Elastic Load Balancer, which distributes
incoming traffic across the application to improve performance, reliability
and availability, particularly during periods of high demand.

The core application is hosted on Amazon EC2, where the medical imaging
web application processes user requests, authenticates users and
coordinates communication with other AWS services. Patient information,
appointments and diagnostic reports are stored within Amazon RDS because
this structured clinical information is best managed using a relational
database. Medical images such as MRI, CT, X-ray and ultrasound scans are
stored separately in Amazon S3, which provides highly durable, scalable and
cost-effective object storage suitable for large imaging datasets. Image
metadata, including file identifiers, timestamps and image attributes, is
stored in Amazon DynamoDB to enable rapid searching and retrieval without
affecting the performance of the relational database.

When new medical images are uploaded, AWS Lambda automatically

processes the files by extracting metadata and initiating application
workflows. Amazon SNS then sends notifications to healthcare professionals
when new diagnostic images or reports become available, supporting timely
clinical decision-making.

To ensure the security and reliability of the system, AWS Identity and Access
Management implements role-based access control so that only authorised
users can access sensitive healthcare information. AWS Key Management
Service encrypts stored data to protect patient confidentiality, while Amazon
CloudWatch continuously monitors application performance, resource
utilisation and operational events.

Overall, this architecture integrates compute, storage, database, networking

and security services into a cloud-native solution that is scalable, secure and
resilient. The design enables efficient management of large medical imaging
datasets while supporting future expansion and maintaining high availability
for healthcare services.

Slide 3 and 4

Speaker Notes (Approximately 2 Minutes)

The proposed architecture integrates multiple AWS services to provide a

secure, scalable and reliable medical imaging platform. Amazon EC2 hosts
the web application that allows doctors and radiologists to access patient
records and diagnostic images. Elastic Load Balancer distributes incoming
requests across application instances to improve availability and maintain
performance during periods of high demand. Medical images, including MRI,
CT and X-ray files, are stored in Amazon S3 because it offers highly durable,
cost-effective and virtually unlimited object storage. Structured information
such as patient details, appointments and diagnostic reports is maintained in
Amazon RDS, while Amazon DynamoDB stores image metadata to support
rapid searching and retrieval. AWS Lambda automates image processing
tasks, including metadata extraction and workflow execution, without
requiring dedicated servers. Amazon SNS delivers notifications to healthcare
professionals when new diagnostic reports become available. Security is
implemented using AWS Identity and Access Management to enforce role-
based access control, AWS Key Management Service to encrypt sensitive
healthcare information and Amazon CloudWatch to continuously monitor
application performance and operational health.

From a cloud computing perspective, the architecture demonstrates key

characteristics including scalability, reliability, security and cost optimisation.
Amazon S3 and DynamoDB automatically scale as the volume of medical
images increases, while AWS Lambda adjusts compute resources according
to demand without manual intervention. The architecture also addresses big
data requirements by supporting the efficient storage and processing of large
diagnostic imaging datasets. Although the design depends heavily on AWS
managed services and requires careful identity management, these
limitations are outweighed by improved operational efficiency, reduced
infrastructure management and enhanced system resilience. Overall, the
proposed cloud-native architecture provides a secure, scalable and future-
ready platform that effectively supports modern medical imaging services.

Task 4 – Speaker Notes (Approximately 3 Minutes)

For Task 4, I completed five modules from the AWS Academy Cloud
Foundations course, and I achieved a score of one hundred percent in each
knowledge check. These modules include Module 1, Cloud Concepts; Module
2, Cloud Economics and Billing; Module 3, AWS Global Infrastructure; Module
4, AWS Cloud Security; and Module 5, Networking and Content Delivery.
Successfully completing these modules provided the theoretical foundation
required to design the proposed medical imaging application using AWS
cloud services.

Module 1 introduced the fundamental principles of cloud computing,

including cloud service models, deployment models and the key benefits of
cloud technologies. This knowledge helped me understand why cloud-native
solutions are increasingly adopted by healthcare organisations to improve
scalability, availability and operational efficiency. It also enabled me to justify
the use of Infrastructure as a Service, Platform as a Service and Software as
a Service within the proposed medical imaging application.

Module 2 focused on cloud economics and billing. Through this module, I

learned how AWS pricing models support cost optimisation by allowing
organisations to pay only for the resources they consume. This concept
influenced my design decisions by encouraging the use of managed services
such as Amazon S3, Amazon RDS and AWS Lambda, which minimise
infrastructure management while improving cost efficiency. I also considered
how healthcare organisations can optimise operational expenditure through
automatic scaling and resource management instead of investing in
expensive on-premises infrastructure.

Module 3 covered AWS Global Infrastructure, including Regions, Availability

Zones and Edge Locations. This module demonstrated how AWS delivers high
availability, fault tolerance and low-latency services across geographically
distributed environments. These concepts influenced my proposed
architecture by supporting reliable application deployment and ensuring
continuous access to patient information and medical images, which are
essential requirements within healthcare environments.

Module 4 focused on cloud security and introduced the AWS Shared

Responsibility Model, AWS Identity and Access Management, encryption and
compliance. These topics directly influenced the security architecture of my
design. I selected AWS IAM to implement role-based access control, ensuring
that only authorised healthcare professionals can access patient records. I
also incorporated AWS Key Management Service to encrypt sensitive medical
information and Amazon CloudWatch to monitor application activity and
improve operational security. These security mechanisms contribute to
protecting confidential healthcare data and supporting regulatory
compliance.

Module 5 introduced networking and content delivery services, including

Amazon Virtual Private Cloud, Route 53 and networking security concepts.
This module improved my understanding of secure network design and
traffic management. Consequently, I incorporated Amazon Route 53 to
provide reliable Domain Name System resolution and Elastic Load Balancing
to distribute incoming requests across application resources. These services
improve application availability, responsiveness and user experience while
supporting future growth in system demand.

Overall, completing these AWS Academy modules significantly strengthened

my understanding of cloud computing principles and AWS services. The
knowledge gained throughout the course directly informed the design of the
proposed medical imaging application by enabling appropriate decisions
regarding compute, storage, networking, databases and security. Rather than
selecting AWS services independently, each design decision was based on
established cloud computing principles, AWS best practices and the
operational requirements of healthcare systems. As a result, the proposed
architecture delivers a secure, scalable, resilient and cost-effective cloud-
native solution capable of supporting modern medical imaging services while
remaining flexible for future expansion.
 Thank you for listening to my presentation. I hope it has
clearly demonstrated my proposed AWS cloud solution, design
decisions, and understanding of cloud technologies. I
appreciate your time and consideration.