{"slug": "cloud-computing-workshop-and-ai-integration", "title": "CLOUD COMPUTING WORKSHOP AND AI INTEGRATION", "summary": "A developer documented lessons from the first session of a Cloud-Native Systems & Applied AI Integration workshop at Coimbatore Institute of Technology, using a \"Pizza as a Service\" analogy to explain cloud service models including IaaS, PaaS, SaaS, and AIaaS. The session also covered AWS fundamentals, hands-on work with S3 and CloudFront, and the distinction between the AWS root user and IAM users for enforcing least-privilege access.", "body_md": "What I Learned Today — Session 1\n\nToday was the first half-day of the Cloud-Native Systems & Applied AI Integration hands-on workshop at Coimbatore Institute of Technology.\n\nThe session focused on understanding cloud fundamentals and getting practical experience with AWS.\n\nHere are the major concepts I learned today.\n\nOne of the simplest and most memorable explanations from today's session was the Pizza as a Service analogy.\n\nInstead of starting with complicated cloud terminology, we can understand service models by thinking about ordering pizza.\n\nOn-Premises\n\nYou make everything yourself.\n\nYou provide:\n\nIngredients\n\nKitchen\n\nOven\n\nCooking\n\nServing\n\nMaintenance\n\nIn computing:\n\nHardware\n\nNetworking\n\nStorage\n\nOperating System\n\nRuntime\n\nApplication\n\nData\n\nEverything is managed by you.\n\nIaaS — Infrastructure as a Service\n\nNow imagine renting the kitchen and oven.\n\nThe infrastructure provider manages the physical infrastructure, while you manage the operating system and applications.\n\nAWS\n\n ├── Servers\n\n ├── Networking\n\n └── Storage\n\nYou\n\n ├── OS\n\n ├── Runtime\n\n ├── Application\n\n └── Data\n\nExamples include virtual machines and cloud infrastructure services.\n\nPaaS — Platform as a Service\n\nNow imagine the kitchen is already prepared.\n\nYou just bring your recipe and ingredients and focus on making the pizza.\n\nCloud Provider\n\n ├── Infrastructure\n\n ├── OS\n\n ├── Runtime\n\n └── Platform\n\nYou\n\n ├── Application\n\n └── Data\n\nYou don't need to worry about managing the underlying infrastructure.\n\nSaaS — Software as a Service\n\nNow imagine ordering a pizza.\n\nYou simply use the finished product.\n\nYou\n\n ↓\n\nPizza\n\nYou don't manage:\n\nThe kitchen\n\nOven\n\nIngredients\n\nCooking\n\nMaintenance\n\nSimilarly, with SaaS, you simply use the software while the provider manages the underlying system.\n\nExamples include services such as Gmail, Google Docs, and Microsoft 365.\n\nAIaaS — AI as a Service\n\nToday's discussion also introduced the idea of AI as a Service.\n\nInstead of building and maintaining the complete AI infrastructure yourself, you consume AI capabilities through a service/API.\n\nYour Application\n\n       |\n\n       v\n\n    AI API\n\n       |\n\n       v\n\nAI Model / Infrastructure\n\nThis makes it possible for developers to integrate AI capabilities without necessarily building and training everything from scratch.\n\nThe Complete Pizza Analogy\n\nThe easiest way I remember it now:\n\n```\n         PIZZA AS A SERVICE\n```\n\nOn-Premises\n\n     ↓\n\nMake everything yourself\n\nIaaS\n\n     ↓\n\nRent the kitchen + infrastructure\n\nPaaS\n\n     ↓\n\nUse a ready-to-use kitchen/platform\n\nSaaS\n\n     ↓\n\nOrder the finished pizza\n\nAIaaS\n\n     ↓\n\nOrder AI capabilities when your\n\napplication needs them\n\nThis analogy made the difference between IaaS, PaaS, SaaS, and AIaaS much easier to understand.\n\nWe then moved into the basics of AWS infrastructure.\n\nThe important takeaway for me was that AWS isn't just a single service.\n\nIt is a huge ecosystem of cloud services that can be combined to build applications.\n\nFor example:\n\nAWS\n\n│\n\n├── Compute\n\n├── Storage\n\n├── Networking\n\n├── Databases\n\n├── Security\n\n├── AI / ML\n\n└── Developer Tools\n\nToday, we mainly worked with S3 and CloudFront while also understanding AWS account access and identity.\n\nAnother important concept I learned was the difference between the AWS Root User and an IAM User.\n\nRoot User\n\nThe root user is the original identity associated with an AWS account.\n\nIt has extremely high-level access to the account.\n\nConceptually:\n\nAWS Account\n\n     │\n\n     └── Root User\n\nBecause of its powerful permissions, the root user should not be used for everyday development activities.\n\nIAM User\n\nIAM stands for:\n\nIdentity and Access Management\n\nIAM allows us to create identities with specific permissions.\n\nAWS Account\n\n     │\n\n     ├── Root User\n\n     │\n\n     └── IAM\n\n          ├── Developer\n\n          ├── Administrator\n\n          └── Other users/roles\n\nThis introduced me to an important cloud security principle:\n\nGive users only the permissions they actually need.\n\nThis is the idea of least privilege.\n\nThe next major hands-on topic was Amazon S3 — Simple Storage Service.\n\nI learned that S3 is an object storage service where data is stored as objects inside buckets.\n\nThe basic structure is:\n\nAWS Account\n\n     ↓\n\n    S3\n\n     ↓\n\n   Bucket\n\n     ↓\n\n  Objects\n\n     ↓\n\nFiles / Data\n\nWe created an S3 bucket and explored its configuration.\n\nThe basic workflow was:\n\nCreate Bucket\n\n     ↓\n\nConfigure Bucket\n\n     ↓\n\nUpload Files\n\n     ↓\n\nConfigure Hosting\n\n     ↓\n\nAccess Website\n\nThis gave me my first practical experience with creating cloud storage rather than just reading about it.\n\nAfter creating the bucket, we explored different configuration options.\n\nThis helped me understand that creating a bucket is only the beginning.\n\nWe also need to think about:\n\nBucket configuration\n\nAccess\n\nPermissions\n\nWebsite hosting\n\nObjects stored inside the bucket\n\nWe then uploaded files into the bucket.\n\nS3 Bucket\n\n│\n\n├── index.html\n\n├── style.css\n\n├── script.js\n\n└── assets/\n\nThis was particularly interesting because these files can form the foundation of a static website.\n\nWe also learned how S3 can be configured to host static website content.\n\nThe basic idea is:\n\nBrowser\n\n   |\n\n   | Request\n\n   v\n\n S3 Bucket\n\n   |\n\n   | index.html\n\n   v\n\n Browser\n\nSo a simple frontend application can be stored and served from cloud infrastructure.\n\nThe final major topic of today's session was Amazon CloudFront.\n\nCloudFront is AWS's Content Delivery Network (CDN).\n\nThe basic architecture we worked with was:\n\n```\n          User\n             |\n             v\n      CloudFront\n         Distribution\n             |\n             v\n          S3\n          Bucket\n             |\n             v\n        Website Files\n```\n\nWe learned how to create a CloudFront distribution.\n\nOne of the key steps was configuring the S3 bucket as the origin.\n\nIn simple terms:\n\nCloudFront\n\n    |\n\n    | Origin\n\n    ↓\n\nS3 Bucket\n\nThe origin is essentially the location from which CloudFront obtains the content it needs to deliver.\n\nSo our overall architecture became:\n\n```\n                INTERNET\n                     |\n                     v\n                USER\n                     |\n                     v\n            ┌────────────────┐\n            │   CloudFront   │\n            │  Distribution  │\n            └───────┬────────┘\n                    |\n                 Origin\n                    |\n                    v\n            ┌────────────────┐\n            │      S3        │\n            │     Bucket     │\n            └───────┬────────┘\n                    |\n                    v\n             Website Files\n```\n\nThis was probably the most valuable part of today's hands-on work because I could see how storage and content delivery work together.\n\nMy Key Takeaways from Session 1\n\nToday's session helped me understand the cloud from three different perspectives:\n\nThe biggest takeaway for me is that cloud computing isn't just about using a remote server.\n\nIt's about understanding how different managed services can be combined to build, deploy, secure, and deliver applications.\n\nWhat's Next?\n\nThis was only the first half-day of Session 1.\n\nThe workshop is continuing, and I'm looking forward to getting hands-on with the remaining topics around:\n\nDocker\n\nContainers\n\nKubernetes\n\nGenerative AI\n\nAI Guardrails\n\nAgentic AI\n\nAI/ML deployment\n\nI'll continue documenting the learning journey as the workshop progresses.\n\nSession 1 — First Half: Completed", "url": "https://wpnews.pro/news/cloud-computing-workshop-and-ai-integration", "canonical_source": "https://dev.to/47jp_yokhash_d9d45c50b/cloud-computing-workshop-and-ai-integration-15cl", "published_at": "2026-09-15 06:57:02+00:00", "updated_at": "2026-09-15 07:02:11.482380+00:00", "lang": "en", "topics": ["ai-products", "ai-tools", "developer-tools"], "entities": ["Coimbatore Institute of Technology", "AWS", "Amazon S3", "CloudFront", "IAM", "Gmail", "Google Docs", "Microsoft 365"], "alternates": {"html": "https://wpnews.pro/news/cloud-computing-workshop-and-ai-integration", "markdown": "https://wpnews.pro/news/cloud-computing-workshop-and-ai-integration.md", "text": "https://wpnews.pro/news/cloud-computing-workshop-and-ai-integration.txt", "jsonld": "https://wpnews.pro/news/cloud-computing-workshop-and-ai-integration.jsonld"}}