AWS IAM Roles: AWS Identity and Access Management (IAM) roles allow for permissions to be assigned to AWS resources without the use of static credentials. Roles provide temporary credentials that are automatically rotated.
Service Role: The 'get-pics' service role created by Rebecca includes a permission policy for read-only access to the S3 bucket and a trust policy that allows the EC2 instance to assume the role.
Temporary Credentials: When the application runs on the EC2 instance, it uses the temporary credentials provided by the role to access the S3 bucket. These credentials are dynamically provided and do not require developer management.
Developer and Admin Roles: Since the EC2 instance has the necessary permissions through the service role, the developer does not need to manage credentials. Similarly, the admin does not need to grant explicit permission to the developer because the permissions are already encapsulated within the role.
Security Best Practices: This approach adheres to AWS security best practices by avoiding the sharing of static credentials and minimizing the need for manual credential management.
Reference:
AWS's official documentation on IAM roles.

FERPA: The Family Educational Rights and Privacy Act (FERPA) is a federal law that protects the privacy of student education records1.
Protection of Student Information: FERPA applies to all schools that receive funds under an applicable program of the U.S. Department of Education. It gives parents certain rights with respect to their children's education records, rights which transfer to the student when they reach the age of 18 or attend a school beyond the high school level1.
Compliance by Cloud Service Providers: Cloud service providers like Daffod, who handle student information collected by educational institutions, must comply with FERPA regulations to ensure the protection and privacy of student data1.
Exclusion of Other Laws: While other laws such as ECPA, CLOUD, and FISMA also deal with privacy and data protection, FERPA is specifically designed to protect the privacy of students' educational records and is the relevant law in this context1.
Reference:
Rick's Cloud article on laws and regulations governing the cloud computing environment1.

AWS Shield Standard is a managed Distributed Denial of Service (DDoS) protection service that is automatically included with AWS services such as Amazon CloudFront and Elastic Load Balancing (ELB). It provides protection against common, most frequently occurring network and transport layer DDoS attacks.
Here's how AWS Shield Standard works to mitigate such attacks:
Automatic Protection: AWS Shield Standard provides always-on detection and automatic inline mitigations that minimize application downtime and latency.
Layer 7 Protection: It offers protection against layer 7 DDoS attacks, which target the application layer and are typically more complex than infrastructure attacks.
Integration with AWS Services: Shield Standard is integrated with other AWS services like ELB and CloudFront, providing a seamless defense mechanism.
Real-Time Visibility: Customers get real-time visibility into attacks via AWS Management Console and CloudWatch.
Cost-Effectiveness: There is no additional charge for AWS Shield Standard; it comes included with AWS services, making it a cost-effective solution for DDoS protection.
Reference:
AWS Shield's official page detailing how it provides managed DDoS protection1.
AWS documentation on best practices for DDoS resiliency, mentioning AWS Shield's role in mitigation2.

Azure AD Pass-Through Authentication (PTA) allows users to sign in to both on-premises and cloud-based applications using the same passwords. This feature is part of Azure Active Directory (AD) and helps organizations enforce their on-premises AD security and password policies in the cloud, thereby providing a seamless user experience while maintaining security.
Here's how Azure AD PTA works:
* Integration with On-Premises AD: Azure AD PTA integrates with an organization's on-premises AD to apply the same security and password policies to cloud resources.
* Authentication Request Handling: When a user signs in, the authentication request is passed through to the on-premises AD for validation.
* Brute-Force Attack Protection: By enforcing the on-premises AD security policies, Azure AD PTA helps to filter out brute-force attacks.
* No Passwords Stored in the Cloud: User passwords remain on-premises and are not stored in Azure AD, which enhances security.
* Simple Sign-On Experience: Users enjoy a simple sign-on experience with the same set of credentials across on-premises and cloud services.
References:
* Microsoft's documentation on deploying on-premises Microsoft Entra Password Protection, which works with Azure AD PTA1.
* A step-by-step guide on implementing Azure AD Password Protection on-premises, which complements the PTA feature2.
* An overview of Azure AD Password Protection and Smart Lockout features, which are part of the broader Azure AD security framework3.