AWS Services Flashcards
List out the AWS services provided
1
Q
Amazon VPC
A
Amazon Virtual private Cloud.
2
Q
Amazon VPC Description
A
This is the space considered your area in the private cloud. Gives you complete control over your network configuration.
3
Q
Amazon VPC is a ________ service
A
foundation
4
Q
Foundational Service
A
A service that is part of AWS that comes inherently with any of the other services which you use.
5
Q
Amazon VPC scope of implementation
A
Lives within a region, across multiple availability zones within the region. VPC is region by region
6
Q
Amazon VPC Subnet Configuration
A
Allowed, and allows for the specification of public and private subnets
7
Q
AWS Compute
A
The basis for computing/app needs. Example would be EC2
8
Q
AWS Compute Service (list them)
A
- Amazon EC2
- Amazon Lightsail
- Amazon Elastic Container Service
- AWS Lambda
9
Q
AWS Lightsail
A
Simple web app server with SSD, Data Transfer, and a low price.
10
Q
AWS Lightsail use case
A
- Simple Web Applications
- WordPress Blogs and Websites
- Ecommerce Websites
- Single-server Business Software
11
Q
Amazon ECS
A
Elastic Container Service
12
Q
Amazon ECS definition
A
This is a container management service that is elastic, works with Docker, and obfuscates the management of the server (which you would have to do with EC2)
13
Q
Amazon ECS use cases
A
- Web applications
- Microservices
- Batch jobs
- Docker workloads
14
Q
Amazon EC2
A
Amazon Elastice Cloud Compute
15
Q
Amazon EC2 Use Cases
A
- Big data (e.g. Hadoop, Spark)
- Database software (e.g., Aurora, DynamoDB)
- Enterprise applications (e.g., SAP, Oracle, Sharepoint)
- Migrations from on-premises environments, including BYOL
- Open-source cluster management
16
Q
Amazon EC2 description
A
Can suit many use cases, can be elastic, uses an AMI (Amazon Machine Image) to determine OS, can configure storage and other aspects ofthe server
17
Q
AWS Lambda Description
A
Allows you to run and execute code without provisioning/managing servers. Scales automatically. Zero server administration
18
Q
AWS Lambda use cases
A
- Web applications
- Mobile backends
- IoT backends
- Stream processing workloads
- File processing workloads
19
Q
AWS Lambda Limit
A
Limited to 5 minute execution time for code blocks
20
Q
AWS Lambda event triggering
A
Lambda is especially useful for eliminating the need for separate EC2 server for triggering events
21
Q
AWS Elastic Beanstalk Problem Meant to be Solved
A
How can i quickly get my application into the cloud
22
Q
AWS Elastic Beanstalk Description
A
Platform as a service. Everything is created for you so you just put your code into the service. Avbstracts away management of the system, but keeps control in your hands (when to do updates, etc.)
23
Q
AWS Beanstalk Use Case
A
- Deploying applications to the cloud.
24
Q
AWS Elastic Beanstalk Supported Platforms
A
- Packer Builder
- Single Container, multi container, preconfigured docker
- Go
- Java SE (Standard Edition)
- Java with Tomcat
- .NET on Windows Server with IIS
- Node.js
- PHP
- Python
- Ruby
25
AWS Elastic beankstalk components
```
Depending on you:
- Your code
AWS:
- Application Service
- HTTP Service
- Operating System
- Language Interpreter
- Host
```
26
AWS Elastic Beanstalk Environment Types
1. Worker
| 2. Web Server
27
Application Load Balancer
A load balancer is a proxy that distributes a workload among multiple servers. Preventing single server bottlenecks. Application load balancer is the same, but it does it among different applications in your AWS cloud.
28
Application Load Balancer Use Case
When building microservices and using containers, you can set up routing rules to distribute traffic to the appropriate application
29
Amazon Elastic Load Balancer
Provides a single exposed point of access for all backend
30
Auto Scaling
Service that ensures that you have the right number of instances (EC2) to handle your application. Uses cloudwatch to monitor and trigger scaling events
31
Autoscaling Components
1. Launch Configuration (What)
2. Auto scaling group (where)
3. Auto scaling policy (when)
32
Auto Scaling Policy Types
1. Scheduled
2. On Demand
3. Scale-Out Policy
4. Sclae In
33
AWS EBS
AWS Elastic Block Store
34
AWS EBS Storage Hardware Types
HDD and SSD
35
AWS EBS Replication
Automtically replicated across different servers in the AZ
36
AWS EBS Encryption
Easy to add, and can be done at no additional cost
37
AWS EBS - Impact of increasing storage
There's no impact other than the storage being increased. No downtime
38
Command Lsblk
this can be used in the AWS CLI to see the EBS storage mounted to an EC2 instance.
39
Amazon S3
Amazon Simple Storage Service
40
Amazon S3 Service Description
Managed cloud service. Storage that is not tied to any server. Data is accessed through an API.
41
Amazon S3 Security
Encryption is allowed. Data is not available to a public facing end point by default.
42
Amazon S3 Endpoints
must be DNS compliant and unique
43
Amazon S3 Use Cases
- Storing app assets. Instead of going got an app, go directly to S3
- Static web hosting
- Backup/DR
- Staging area for large volumes of data (good when paired with Amazon Athena)
44
Amazon S3 Buckets
Buckets are the different storage areas in the S3 service
45
Amazon S3 Interaction Methods
Able to interact both through CLI and GUI tool
46
Amazon S3 Sync Command
Used to pull data from a specific bucket
47
Amazon Glacier
Data archiving solution. Meant for cold data storage
48
Amazon Glacier Vault
A grouping of glacier storage that has similar access policies (permissions groups)
49
Auto-Archiving S3
S3 can be configured to auto-archive data from S3 to Glacier
50
Amazon Glacier Pricing
The pricing strategy of Amazon Glacier is that payment is done by the speed of data retrieval. Faster retrieval = more cost
51
Amazon Glacier Retrieval Tiers
Amazon Glacier has 3 tiers:
1. Bulk (5-12 hours)
2. Standard (3-5 hours)
3. Expedited (1-5 minutes)
52
Amazon Glacier Encryption
data in Glacier is automatically encrypted at rest
53
Amazon Glacier Use Case
When you need to storage large volumes of data that won't be accessed frequently
54
Amazon RDS
Amazon Relational Database Service. A fully managed database service.
55
Amazon RDS Instance Configuration Options
Able to allocate/pay for:
- CPU
- Memory
- Network Performance
- Storage type
56
Types of RDS Engines
- MySQL
- Amazon Aurora
- SQL Server
- PostgreSQL
- MariaDB
- Oracle
57
Dynamo DB
- NoSQL datastore service. NoSQL database tables as a service
58
Dynamo DB Scaling
You can choose to allow autoscaling of storage, memory, etc. or manually control it
59
Dynamo DB Storage Type
Only SSD
60
Dynamo DB key types
Compound Key
| Single Key
61
Single Key
Only has a partition key which is unique identifier for a record
62
Compound Key
Combination of partition key and sort key to speed up data retrieval. Only partition/sort on non-null values
63
Viewing DynamoDB Tables
Tree and Text (JSON)
64
DynamoDB GUI Querying
is allowed through the AWS console
65
Amazon Redshift
Full managed datawarehouse as a service
66
Amazon Redshift Interaction Language
SQL, so can be used with many BI tools
67
Use Case for Redshift
- increase the agility of the datawarehouse
| - Big data customers which can't afford hardware and other tech resources
68
Amazon Redshift SQL vs NoSQL
Amazon Redshift is SQL and has tables like other RDS's
69
Amazon Aurora
Database backup system. Designed for instance recovery. Heals from a crash in less than 60 seconds
70
Amazon Aurora Benefits
- Managed Service
- Fast and reliable
- Simple
- Compatible
- Pay-as-you-go
71
Amazon Aurora Compatibility
1. Postgresql
| 2. MySQL
72
AWS Trusted Advisor
Consulting service/automated recommendations. Links with cloudwatch
73
AWS Trusted Advisor Uses
- Performance tuning
- Cost analysis
- Security advice/suggestions
74
AWS Security Benefits of Scale
Big benefit is that security issues reported by any customer, is fixed for that customer and all customers on the platform
75
AWS Security Tools
Tools for security are available from AWS and AWS partners
76
Different Access Control Management Options
- IAM
- MFA (multi factor Auth)
- Integration and federation with corporate servers
77
Monitoring and Logging (security)
- All API calls
- Log aggregation options
- Alert notifications
78
AWS Marketplace
Apps are available on the marketplace to increase security. Thinks like anti-malware software and other things
79
AWS Shared Responsibility Model
This is the core ethos behind AWS.
- AWS responsible for the security of managed services, and general cloud infrastructure
- Customers responsible for: what is stored, where it is stored in the cloud, who has access in the VPC, and who has access to the data
80
AWS Security Compliance Programs
3rd part and AWS internal teams are both scanning for vulnerabilities and certifying that the cloud is in fact secure
81
AWS Risk Management 3rd Part Governing Bodies
COBIT: Control objectives for information and related technology
AICPA: American Institute of certified public accountants
NIST: National Institute of Standards and Technology
82
AWS End Point Scanning
Can be requested at any point (as long as policy is not being broken)
83
AWS Security Resources
1. White papers/web content
2. AWS Trusted Advisor
3. AWS Account Team
4. AWS Enterprise Support
5. AWS Professional Services/Partner Network
6. AWS Advisor Bulletins
84
AWS Architecture
Striving for operational excellence
85
Operation Excellence
Tenants:
1. Perform operations as code
2. Annotate Documentation
3. Make frequent, small, reversible changes
4. Refine operations and procedures frequently
5. Anticipate Failure
6. learn from all operational failures
86
Security Design Principles
1. Implement strong identity foundation
2. Enable Traceability
3. Apply security at all layers
4. Automate security best practices
5. Protect data in transit and at rest
6. Prepare for security events
87
Reliability Design Principles
1. Test recoveries
2. Automatically recover from failure
3. Scale horizontally
4. Stop guessing capacity
5. manage change in automation
88
Performance Efficiency Design Principles
1. Democratize advanced technologies
2. Go global in minutes
3. Use serverless architectures
4. Experiment more often
5. Mechanical sympathy (understanding how things work)
89
Cost Optimization Design Principles
1. Adopt a consumption model
2. Measure overall efficiency
3. Stop spending money on data center operations
4. Analyze Attribute Expenditure
5. Use managed services to reduce cost of ownership
90
Fault Tolerance
The ability for a system to remain operational even is some process goes wrong
91
High Availability
Downtime minimization and always functioning and available. Can be assured on servers, AZ's, Regions, and fault tolerant services
92
Elastic IPS
Allows end users to be directed to a functioning server/service is the main were to fail
93
Autoscaling
Launches or terminates instances based upon specified conditions (scheduled or manual)
94
Amazon Cloudwatch
Dsitributed statistics tracking tool, allows the use of custom metrics
95
Amazon Simple queue service
Amazon SQS; distributed messaging system
96
S3
High durability storage service
97
Amazon Simple DB
Scalable service with no single point of failure for traditional data storing
98
Amazon RDS Fault Tolerance
High availability and fault tolerance due to auto backups and other features which can be enabled
99
AWS Architecture: Web Hosting
Common issues this resolves:
- Infrastructure maintenance/issues
- Architecture
- Cost
100
AWS Architecture advantages in the cloud
- No more physical network appliances: no firewalls, or other hardware that can be installed
- There are many firewalls in many places
- Consider multiple datacenters for high availability and reliability
101
Reserved Instance Pricing
Cheaper than spot pricing, due to the fact that you are paying up front, reducing risk from Amazon's standpoint
- Have a full and partial upfront payment plan (partial has less of a discount)
102
Tiered Pricing
Exists for certain services
103
Custom Pricing
Available for special projects with a unique set of requirements
104
No Extra Cost Services
- Amazon VPC
- Elastic Beanstalk
- Cloud Formation
- AWS IAM
- Auto Scaling
105
Pay For
- Compute
- Storage
- Data Transfer Out
106
No Charge For
- Data Transfer In
| - Data transfer between (the same AZ)
107
Amazon EC2 Pricing Consideration/Variations
- Physical Capacity
- AWS Region
- OS
- Number of cores
- Memory
- Monitoring
- Load Balancing
- Number of instance
- Hours of use
108
Amazon S3 Charges by:
- Storage class
- Storage type/volume
- Requests
- Data transfer outside of the region
109
Amazon EBS pricing
- Volumes
- IOPS
- Snapshots
- Data transfers
110
Amazon RDS
- Incurs charges while running
- Database configs
- Purchase type (reserved/vs not)
- Number of instance
- Provisioned storage
- Deployment Type
- Data transfer out
111
Amazon Cloudfront Pricing
Web service for content delivery
- Pricing caries by region
- Edge location
112
Amazon TCO
Total cost calculator
113
AWS Business Support Plan
Does not include access ot well architected review by AWS solutions architects
