Amazon DVA-C02 Practice Test - Questions Answers, Page 18

Amazon EventBridge:A service that reacts to events from various AWS sources, including S3. Rules define which events trigger actions (like invoking Lambda functions).

S3 Object Created Events:EventBridge can detect these, providing seamless integration for automated CSV processing.

S3 Lifecycle Rules:Allow for actions based on object age or prefixes. These can directly trigger Lambda functions for file processing.

Amazon EventBridge Documentation:https://docs.aws.amazon.com/eventbridge/

Working with S3 Event Notifications:https://docs.aws.amazon.com/AmazonS3/latest/userguide/EventNotifications.html

S3 Lifecycle Configuration:https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html

Amazon EFS:A network file system (NFS) providing shared, scalable storage across multiple Lambda functions and other AWS resources.

Lambda Mounting:EFS file systems can be mounted within Lambda functions to access a shared storage space.

Log Appending:EFS supports appending data to existing files, making it ideal for the log file scenario.

Amazon EFS Documentation:https://docs.aws.amazon.com/efs/

Using Amazon EFS with AWS Lambda:https://docs.aws.amazon.com/lambda/latest/dg/services-efs.html

Secrets Management:AWS Secrets Manager is designed specifically for storing and managing sensitive credentials.

Built-in Rotation:Secrets Manager provides automatic secret rotation functionality, enhancing security posture significantly.

IAM Integration:IAM policies and roles grant fine-grained access to ECS Fargate, ensuring the principle of least privilege.

Reduced Overhead:This solution centralizes secrets management and automates rotation, reducing operational overhead compared to the other options.

AWS Secrets Manager:https://aws.amazon.com/secrets-manager/

Secrets Manager Rotation:https://docs.aws.amazon.com/secretsmanager/latest/userguide/rotating-secrets.html

IAM for Secrets Manager:https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_iam-policies.html

HTTP Status Codes:Each HTTP status code has a specific meaning in RESTful APIs.

HTTP 405 (Method Not Allowed):Indicates that the request method (e.g., POST) is not supported for the specified resource.

HTTP 401 (Unauthorized):Represents a failure to authenticate, which is the appropriate response for invalid login credentials.

HTTP Status Codes:https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

Lambda Concurrency:The 'maximum concurrency' setting in event source mappings controls the maximum number of simultaneous invocations Lambda allows for that specific source.

Prioritizing Queues:Setting a lower maximum concurrency for the 'high priority queue' ensures it's processed first while allowing more concurrent invocations from the 'low priority queue'.

Batching:Batch size settings affect the number of messages Lambda retrieves from a queue per invocation, which is less relevant to the prioritization requirement.

Lambda Event Source Mappings:https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventsourcemapping.html

Lambda Concurrency:https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html

Instance Metadata Service:EC2 instances have access to an internal metadata service. It provides instance-specific information like instance ID, security groups, and public IP address.

Accessing Metadata:

Make an HTTP GET request to the base URL:http://169.254.169.254/latest/meta-data/

You'll get a list of available categories. The public IPv4 address is underpublic-ipv4.

Instance Metadata and User Data:https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html

CloudWatch for Log Analysis:CloudWatch is the best fit here because logs are already centralized. Here's the process:

Metric Filter: Create a metric filter on the CloudWatch Logs log group. Design a pattern to specifically identify application error messages.

Custom Metric: This filter generates a new custom CloudWatch metric (e.g.,ApplicationErrors). This metric tracks the error count.

CloudWatch Alarm: Create an alarm on theApplicationErrorsmetric. Configure the alarm with your desired threshold and a 5-minute evaluation period.

SNS Action: Set the alarm to trigger an SNS notification when it enters the alarm state.

CloudWatch Metric Filters:https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html

CloudWatch Alarms:https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html

SNS as a Fan-out Mechanism:SNS is perfect for triggering multiple actions from a single event (here, the image upload).

Workflow:

SNS Topic:Create an SNS topic that will be the central notification point.

S3 Event Notification:Configure the S3 bucket to send 'Object Created' event notifications to the SNS topic.

Lambda Subscription:Subscribe your thumbnail-creating Lambda function to the SNS topic.

Email Subscription:Subscribe an email address to the SNS topic to trigger notifications.

S3 Event Notifications:https://docs.aws.amazon.com/AmazonS3/latest/userguide/EventNotifications.html

SNS Subscriptions:https://docs.aws.amazon.com/sns/latest/dg/SNSMobilePush.html

AWS X-Ray SDK:The primary way to enable X-Ray tracing within applications. The SDK sends data about requests and subsegments to the X-Ray daemon for service map generation.

Instrumenting All Services:To visualize a complete microservice architecture on the service map, each relevant service must include the X-Ray SDK.

AWS X-Ray Documentation:https://docs.aws.amazon.com/xray/

X-Ray SDK for Python:https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-python.html