Review Deck Flashcards
(142 cards)
Amazon Macie
AI/ML security service that helps prevent data loss by automatically discovering, classifying, and protecting sensitive data stored in Amazon S3.
Machine Learning to recognize sensitive data (e.g., PII, intellectual property, etc.), assigns a business value, and provides visibility into where this data is stored and how it is being used in your organization.
Macie continuously monitors data access activity for anomalies, and delivers alerts when it detects risk of unauthorized access or data leak.
Macie can detect global access permissions set on sensitive data, detect upload of API keys inside source code, and verify data is stored and accessed according to customer compliance standards.
Lambda@Edge
Lets you run Lambda functions to customize the content that CloudFront delivers, executing the functions in AWS locations closer to the viewer. Lambda@Edge functions run in response to CloudFront events, without provisioning or managing servers.
You can use Lambda functions to change CloudFront requests and responses at the following points:
– After CloudFront receives a request from a viewer (viewer request)
– Before CloudFront forwards the request to the origin (origin request)
– After CloudFront receives the response from the origin (origin response)
– Before CloudFront forwards the response to the viewer (viewer response)
HTTP 504
Gateway timeout error, usually results when a server is down.
Amazon MQ
Message broker that supports industry-standard APIs and protocols so you can switch from any standards-based message broker without rewriting messaging code in existing applications.
TRUE/FALSE: Step Scaling & Simple Scaling both require you to create CloudWatch alarms.
TRUE
Step Scaling & Simple Scaling both require you to define whether to…
…add or remove instances, and how many, or set the group to an exact size.
Step Scaling and Simple Scaling policies Both require you to…
…specify the high and low thresholds for the alarms.
Simple vs Step Scaling Policies
The main difference is the step adjustments you get with step scaling policies. Step adjustments increase or decrease capacity of an Auto Scaling group based on the size of the alarm breach.
Target Tracking Scaling Policy
Increase or decrease capacity of an Auto Scaling group based on a target value for a specific metric, adding/removing capacity to keep the metric at/near the specified target value.
In addition, a target tracking scaling policy also adjusts to changes in the metric due to a changing load pattern.
Helps resolve over-provisioning of your resources.
Suspend and Resume scaling…
…is used to temporarily pause scaling activities triggered by scaling policies and scheduled actions.
Cooldown periods…
…help to prevent the initiation of additional scaling activities before the effects of previous activities are visible.
This policy must wait for a scaling activity or health check replacement to complete and a cooldown period to expire before responding to additional alarms.
Simple Scaling
Use cases for signed URLs:
– RTMP distribution–signed cookies aren’t supported for RTMP distributions
– Restrict access to individual files
– Use when cookies aren’t supported by users’ clients
Use cases for signed cookies:
– Provide access to multiple restricted files
– To avoid changing existing URLs
Match Viewer
An Origin Protocol Policy which configures CloudFront to communicate with your origin using HTTP or HTTPS, depending on the protocol of the viewer request. CloudFront caches the object only once even if viewers make requests using both HTTP and HTTPS protocols.
Field-Level Encryption…
…allows secure user-submitted uploads of sensitive information to a web server.
TRUE/FALSE: To use signed urls will require changes to existing urls?
TRUE
TRUE/FALSE: Amazon RDS provides metrics in real time for the operating system (OS) that your DB instance runs on.
TRUE
Two ways you can view metrics for an RDS DB instance:
- By using the console
2. View Enhanced Monitoring JSON output from CloudWatch Logs in a monitoring system of your choice
By default, Enhanced Monitoring metrics are stored in the CloudWatch Logs for…
…30 days
To modify the amount of time the metrics are stored in the CloudWatch Logs…
…change the retention for the RDSOSMetrics log group in the CloudWatch console.
Why are CloudWatch and Enhanced Monitoring Metrics different?
The differences can be greater if your DB instances use smaller instance classes, because then there are likely more virtual machines (VMs) that are managed by the hypervisor layer on a single physical instance. Enhanced Monitoring metrics are useful when you want to see how different processes or threads on a DB instance use the CPU.
CloudWatch gathers metrics about CPU utilization from the hypervisor for a DB instance, and Enhanced Monitoring gathers metrics from an agent on the instance. Because the hypervisor does additional work CloudWatch accounts for that in its CPU usage calculation.
TRUE/FALSE: You can use CloudWatch to monitor CPU Utilization of a database.
False–although you can use CloudWatch to monitor CPU Utilization of a database instance, it will not provide CPU bandwidth usage or total memory consumed by each database process.