Syllabus - COSC 480/592 Cloud Computing

AWS LMS login

Lab due dates

COSC 480/592 schedule (subject to changes by the instructor with appropriate notice).

ACF stands for Academy Cloud Foundations

CAA stands for Cloud Computing Architecture

Instructor: Dr. Andrii Kashliev, akashlie@emich.edu

Important: All students are responsible for understanding and following all the rules and policies in this syllabus, including those in the Other policies section. Please do not hesitate to contact Dr. Kashliev with any questions.

Tutoring Lab: Pray-Harrold 513 M-R 10am-8pm, F noon-2pm. Staffed with graduate assistants and tutors, our tutoring lab is a great place to get help and get your questions answered. Bring your laptop, show them your code, tell them where you're stuck, ask questions, etc.

Drone Use Policy

  • Lab space and keys. You can use drones in PH 311. Each student will receive a key to 311.

  • Do not mess with computers in PH 311. There are a number of computers in PH 311 used for research and other purposes that belong to other faculty. Please be respectful and do not touch these machines.

  • Sharing drones. Due to a limited number of drones, teams are expected to share drones with other teams. This should not be burdensome, since each team will spend most of their time coding and figuring things out while occasionally testing their code by flying a drone. Please be respectful and considerate of other teams' needs.

  • Laws. Government regulations prohibit using drones in certain spaces. For this reason, the drones should remain inside 311 at all times. You are not allowed to carry/fly drones outside of 311 under any circumstances. Please note that there are hidden security cameras across EMU campus, including some inside Pray Harold which are accessible to EMU Police Department. Students that violate this policy will not be allowed to continue working on this project and will receive 0 for this project.

  • Safety. When in 311, never prop the door open. The door must remain shut at all times.

  • Never leave 311 unattended - even for 30 seconds - always lock the door if no one remains inside.

  • Safety. Always wear safety goggles when flying a drone.

  • When finished, put drone batteries into the charging hub to charge them.


Course Details

This course introduces students to cloud computing. Students will learn about compute, storage, and network resources in the cloud; security, identity, and access management; database options and elasticity tools available in one of the leading cloud platforms, such as AWS. Students will also learn and apply best practices of cloud systems design, automation, serverless architectures, deployment, and implementation.

Prereq: COSC 311

Textbook: no textbook is required for this course. All materials will be provided to you in electronic form.

Final Exam: see the date above.


  • Identify the value and benefits of cloud computing

  • Understand methods and tools to maintain security and protect data

  • Explain the financial advantages of the cloud

  • Navigate a cloud management console

  • Differentiate between cloud storage options

  • Be able to insert data into and query open source NoSQL database instances running in the cloud

  • Understand cloud compute and networking options

  • Describe and use cloud database options

  • Identify deployment and management options

  • Make decisions based on recommended architectural principles and best practices

  • Create a cloud migration roadmap and plan

  • Use cloud to make infrastructure scalable

  • Create a business continuity plan and achieve high availability

  • Create event-driven scaling

  • Automate the deployment of cloud resources

  • Design architectures to decouple infrastructure and reduce interdependencies

  • Optimize data storage for static content

  • Identify best practices prescribed in the Well-Architected framework

  • Identify and solve common configuration and design issues

  • Differentiate between architectures for data processing and analytics, mobile back-ends, and video transcoding

  • Be prepared for a standard industry-recognized certification exam in cloud computing, such as AWS Certified Solutions Architect – Associate


Submission Policy

Submissions: For all assignments, labs, etc, including group assignments and projects, each student is required to individually submit the deliverables via Canvas. It is understandable that for a group project such deliverables may be similar or identical for all students in a team. Nonetheless, to earn credit for any group assignment, each student must submit deliverables individually via Canvas. You may be asked to submit some assignments/projects for grading through Canvas. If you are having technical problems with Canvas, send your completed work by email as attachment to the grader so that we have a record that you finished the work on time. If the assignment is coding-based: all code submitted for grading must run successfully. If the code you submitted has a syntax or a runtime error, the assignment/project will automatically receive 0.

Late Submission Policy: Unless otherwise noted, each assignment must be submitted through Canvas by the due date. Immediately after the due date the assignment will disappear in Canvas and you will not be able to submit your assignment, i.e. you will automatically receive a 0 for this assignment.

Each student is granted two late excuses in the entire semester. Late excuses do not apply to and cannot be used for demos. When using his/her late excuse, a student is allowed to submit an assignment up to 48 hours late with or without a valid reason. To use your late excuse, please send an email to the graduate assistant (grader), and include the course number and “LATE EXCUSE” in the subject line. Include your completed homework in your email as an attachment so that we have a record that you finished the work within 48 hours of the due date. The grader will open the assignment in Canvas for you so that you could submit it there. The grader will grade the work that you submit through Canvas. Note that you only have two late excuses for the entire semester, so use this option wisely.

Other policies