Skip to content

Commit e37209a

Browse files
fix 154
all the other options are solution for decoupling and event driven architectures, not logging on lambda, by logging to the console, with the right permission in the lambda execution role to log in cloudwatch logs, these console logs will be automatically available for troubleshooting
1 parent cdced04 commit e37209a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1946,8 +1946,8 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
19461946
### A company requires that AWS Lambda functions written by Developers log errors so System Administrators can more effectively troubleshoot issues. What should the Developers implement to meet this need?
19471947

19481948
- [ ] Publish errors to a dedicated Amazon SQS queue.
1949-
- [x] Create an Amazon CloudWatch Events event trigger based on certain Lambda events.
1950-
- [ ] Report errors through logging statements in Lambda function code.
1949+
- [ ] Create an Amazon CloudWatch Events event trigger based on certain Lambda events.
1950+
- [x] Report errors through logging statements in Lambda function code.
19511951
- [ ] Set up an Amazon SNS topic that sends logging statements upon failure.
19521952

19531953
**[⬆ Back to Top](#table-of-contents)**

0 commit comments

Comments
 (0)