A .NET application that you manage is running in Elastic Beanstalk. Your developers tell you they will need
access to application log files to debug issues that arise. The infrastructure will scale up and down.
How can you ensure the developers will be able to access only the log files?
A.
Access the log files directly from Elastic Beanstalk
B.
Enable log file rotation to S3 within the Elastic Beanstalk configuration
C.
Ask your developers to enable log file rotation in the applications web.config file
D.
Connect to each Instance launched by Elastic Beanstalk and create a Windows Scheduled task to rotate the
log files to S3.
Explanation:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.loggingS3.title.html
D is not correct. You configure the log rotation from within Elastic Beanstalk, per the doc link provided. B is the answer.
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html
1
0
B is correct according to the link.
0
0
B is correct
0
0
D is correct.
Elastic Beanstalk Windows Server platforms do not support bundle logs. Since the .net application should run on windows, the logs on beanstalk only have the last 100 events.
1
0
b
0
0
Agree wit Joe. Correct Answer is D
0
0
A
Note
Elastic Beanstalk Windows Server platforms do not support bundle logs.
http://docs.aws.amazon.com/es_es/elasticbeanstalk/latest/dg/using-features.logging.html
0
0
Answer – B
The EC2 instances in your Elastic Beanstalk environment generate logs that you can view to troubleshoot issues with your application or configuration files. Logs created by the web server, application server, Elastic Beanstalk platform scripts, and AWS CloudFormation are stored locally on individual instances and can be easily retrieved with the environment management console or the EB CLI. You can also enable log rotation to Amazon S3.
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html
0
0