The operations team and the development team want a single place to view both operating system and application logs.
How should you implement this using AWS services?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A.
Option B is incorrect because CloudTrail is not designed specifically to collect operation system or application logs.
Option C is incorrect because the Kinesis stream is more suitable for real-time data processing.
CloudWatch Event is also not required in this scenario.
Option D is incorrect because it does not mention how to view the logs through the EC2 console.
EC2 is not a suitable service for users to view the logs.
You can use Amazon CloudWatch Logs to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon EC2) instances, AWS CloudTrail, and other sources.
You can then retrieve the associated log data from CloudWatch Logs.
For more information on Cloudwatch logs, please refer to the below link:
http://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.htmlThe best option to implement a single place to view operating system and application logs using AWS services is to use Amazon CloudWatch Logs. This allows for the logs to be stored centrally, and accessed by both the operations and development teams.
Option A suggests using AWS CloudFormation to create a CloudWatch Logs group and sending logs to CloudWatch using the CloudWatch Logs Agent. This is a good approach as CloudFormation is a powerful tool for automating infrastructure deployments and CloudWatch Logs is a highly scalable and reliable logging service offered by AWS. The CloudWatch Logs Agent can be used to collect logs from EC2 instances and other sources, and send them to CloudWatch Logs for storage and analysis.
Option B suggests using AWS CloudFormation and configuration management to set up remote logging to send events via UDP packets to CloudTrail. This option is not recommended as CloudTrail is a service that tracks and logs all AWS API calls made in an account. It is not designed to handle application or operating system logs.
Option C suggests setting up remote logging to send events to an Amazon Kinesis stream and forward these logs into Amazon CloudWatch Event or Amazon Redshift, depending on available analytic tools. While this option provides flexibility in terms of where the logs are sent, it also adds complexity to the overall logging solution.
Option D suggests merging application logs with operating system logs and using IAM Roles to allow both teams to view the output from the Amazon EC2 console. This option is not recommended as merging logs can make it difficult to search and analyze logs. Additionally, providing access to the EC2 console can create security risks.
In conclusion, the best option is A, using AWS CloudFormation to create a CloudWatch Logs group and send logs to CloudWatch using the CloudWatch Logs Agent. This provides a scalable and reliable logging solution that can be easily accessed by both the operations and development teams.