Objective “To create a web platform that allows authenticated users to request EC2 instances, with options to define instance parameters, monitor status, and manage instances directly from the platform.”

Core Features: User Authentication & Authorization “Secure login system for users, with role-based access controls (Admin, Regular User).”

Implementation: “Django’s built-in authentication or integration with AWS Cognito for authentication and user management.”

Instance Request Form “A form where users can specify the configuration of the EC2 instance they need, like instance type, region, operating system, etc.”

Implementation “Build a form in Django to collect these parameters, validating inputs before processing”

Automated EC2 Provisioning “Automatically provision EC2 instances based on user input, with specified configurations.”

Implementation: “Use Boto3 (AWS SDK for Python) to interact with AWS EC2 and create instances. Add custom logic to check if requested configurations are within predefined policies or limits (e.g., max instance size).”

Instance Dashboard “A dashboard where users can view the status of their requested instances, including instance ID, IP address, current status (running, stopped), and resource utilization.”

Implementation: Poll AWS EC2 or use CloudWatch to display instance details and status updates.

Manage and Terminate Instances “Allow users to start, stop, and terminate their instances via the platform, with real-time feedback on instance state.”

Implementation: “Use Boto3 to send stop/start/terminate commands to EC2 and update the dashboard accordingly. Optionally, allow setting up time-based auto-termination to avoid unnecessary costs.”

Notifications and Alerts “Notify users when their instance is ready, when it’s been idle for too long, or when cost thresholds are reached.”

Implementation: “Use AWS SNS or SES for notifications, or integrate with Django’s email framework to send alerts.”

Cost Tracking and Reporting “Feature: Track instance usage and estimated costs, displaying usage data for individual users and offering reports for admins.”

Implementation: “AWS Cost Explorer API or AWS Billing API to pull cost information. Display this in the platform, so users and admins are aware of spending.”

Security and Compliance “Limit EC2 instance types or regions based on compliance or organizational policies”

Implementation: “Validate user requests against a policy engine in Django before provisioning, ensuring requests meet predefined security and usage standards.”

AWS Services to Use

1. EC2: Core resource for instance management.
2. IAM: For setting permissions on the AWS side, ensuring the platform can manage instances securely.
3. SNS/SES: For notifications.
4. CloudWatch: For monitoring instance status and usage metrics.
5. Cost Explorer or Billing API: For cost tracking and reporting.

Technical Workflow

1. User Request: User fills out a form to request an instance.
2. Validation: Platform checks request parameters against policy rules.
3. Provisioning: If validated, the platform triggers an EC2 instance creation using Boto3.
4. Notification: User receives a notification when the instance is ready.
5. Instance Management: User manages instance lifecycle (start/stop/terminate) directly from the platform.
6. Monitoring and Reporting: Real-time updates on instance status and monthly reports on costs.

Learning Objectives for Students

1. Platform Engineering: Students gain experience in provisioning, managing, and tracking infrastructure resources from a centralized platform.
2. AWS Integration: Familiarity with AWS SDK (Boto3) and services like EC2, IAM, CloudWatch, and SNS.
3. Cost Management: Understanding AWS cost implications and tracking methodologies.
4. Security and Compliance: Enforcing security policies and automating compliance on a cloud platform.