security Flashcards
Well-architected framework
design principles and best practices for running workloads in the cloud.
- Operational Excellence
- Security
- Reliability
- Performance Efficiency
- Cost optimization
Operational Excellence
CODECOMMIT Focuses on creating applications that effectively support production workloads. -plan for and anticipate failure -script operations as code -deploy smaller, reversible changes -Learn from failure and refine
Security
CLOUDTRAIL
Focus on putting mechanisms in place that help protect your systems and data
-Automate security tasks
-encrypt data in transit and at rest
-Assign only the least privilege’s required
-track who did what and when
-ensure security at all application layers
Reliability
RDS Focuses on designing systems that works consistently and recover quickly -Recover from failure automatically -Scale horizontally for resilience -Reduce idle resources -Manage change through automation -Test recovery procedures
Performance efficiency
LAMBDA Effectively use of computing resources to meet system and business requirements while removing bottlenecks -Use serverless architectures first -Use multi-region deployments -Delegate tasks to a cloud vendor -Experiment with virtual resources.
Cost Optimization
S3 intelligent -tiering
Focuses on delivering optimum and resilient solutions at the least cost to the user.
-Utilize consumption-based pricing
-Implement cloud financial management
-Measure overall efficiency
-Pay only for resources your application requires.
CodeCommit
to enable tracking of code changes and version-control
Cloudformation templates of your infrastructure
CloudTrail
You can configure central logging of all actions performed in your account
RDS
You can use Multi-AZ Deployments for enhanced availability and reliability of RDS databases
Lambda
To run code with zero administration
S3 Intelligent-Tiering
automatically move your data between access tiers based on your usage patterns.
IAM
Allows you to control access to your AWS Services and resources.
- Helps secure your cloud resources
- You define who has access.
- You define what they can do
- a free global service
Identities
WHO can access your resources
- root user
- individual user
- groups-roles
Access
WHAT resources they can access
- policies
- aws managed policies
- customer managed policies
- permissions boundaries
Authentication
Where you present your identity and provide verification
Authorization
Determines which services and resources the authenticated identity has access to.
Users
Users are entities that you create in IAM to represent the person or application needing to access your AWS resources.
Root user
Created when you first open your AWS account.
- close account
- change email address
- modify support plan
Individual users
created in IAM and are used for everyday tasks.
- Perform Administrative tasks
- Access application code
- Launch EC2 instances
- configure databases
Applications
You create a user in IAM so you can generate access keys for application running on-premises that needs access to your cloud resources.
Principle of least privilege
Giving a user the minimum access required to get the job done
Developers
Responsible for building applications
Project managers
Responsible for managing the budget
CLI
Command line interface.
Allows you to access resources in your AWS account through terminal or command windows. Access keys are needed when using the CLI and can be generated using IAM.
Groups
Collection of users of IAM users that helps you apply common access controls to all group members
- -used to group users that perform similar tasks
- access permissions apply to all members of the group
- access is assigned using policies and roles.