BSIT400-T301 Cloud Computing & Governance (2257-1)

  What did you find enjoyable or not about this assignment?           I really think that this was a waste of time,  Was it helpful to you in your current job?          No, I work at Walmart at this time. Can you see yourself Blogging in the future when it isn't required for an assignment?          No I do not see myself using doing this.  Can you see this ability as desirable for a company, giving you more weapons in your arsenal and making you a more attractive hire?          No, I do not see this as a way to get hired. 

  Documentation Amazon EC2 User Guide Security in Amazon EC2 Cloud security at AWS is the highest priority. As an AWS customer, you benefit from a data center and network architecture that are built to meet the requirements of the most security-sensitive organizations. Security is a shared responsibility between AWS and you. The  shared responsibility model  describes this as security of the cloud and security in the cloud: Security of the cloud  – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the effectiveness of our security as part of the  AWS Compliance Programs . To learn about the compliance programs that apply to Amazon EC2, see  AWS Services in Scope by Compliance Program . Security in the cloud  – Your responsibility includes the following areas: Controlling network access to your in...

  Step 1: Confirm and Diagnose Capacity Overload Identify affected capacity and error time: Obtain workspace name, capacity name, and exact error occurrence time. Use monitoring tools: For Microsoft Fabric, open the Microsoft Fabric Capacity Metrics app and navigate to the Compute page to check capacity utilization and system events at the error time. Look for overload signs: Confirm if the capacity was overloaded by checking status changes to "Overloaded" and observe resource consumption spikes to understand the timing and severity of the issue (e.g., 100% CU utilization). Step 2: Check for Throttling and Resource Rejections Inspect throttling metrics (interactive delay/rejection and background rejection) via the Throttling tab in monitoring tools. Verify if throttling corresponds to the error time, indicating resource exhaustion leading to delayed or rejected operations. If no throttling is detected, consider that the error might have other causes or anothe...