Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not make readable copy of email

See original GitHub issue

I double-checked all the permissions according to readme, but still get the error:

START RequestId: af224ff3-fb47-11e6-9444-1f9e512246cc Version: $LATEST
2017-02-25T10:46:38.924Z	af224ff3-fb47-11e6-9444-1f9e512246cc	{ level: 'info',
  message: 'Fetching email at s3://musweb.mail/o3vrnil0e2ic28trm7dfhrc2v0clambda4nbp0g1' }
2017-02-25T10:46:40.344Z	af224ff3-fb47-11e6-9444-1f9e512246cc	{ level: 'error',
  message: 'copyObject() returned error:',
  error: 
   { [AccessDenied: Access Denied]
     message: 'Access Denied',
     code: 'AccessDenied',
     region: null,
     time: Sat Feb 25 2017 10:46:40 GMT+0000 (UTC),
     requestId: '4CC93788EF0116A6',
     extendedRequestId: 'nGtVxfT3aT/uqPpufrdvjJrLy/ClZ4WeJoqh8AK9eXy5keqqx3Q89SSnkrvIYyxnSS31STpGF00=',
     cfId: undefined,
     statusCode: 403,
     retryable: false,
     retryDelay: 50.05418912041932 },
  stack: 'AccessDenied: Access Denied
    at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/services/s3.js:538:35)
    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:671:14)
    at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:673:12)
    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:115:18)' }
2017-02-25T10:46:40.404Z	af224ff3-fb47-11e6-9444-1f9e512246cc	{ level: 'error',
  message: 'Step returned error: Error: Could not make readable copy of email.',
  error: [Error: Error: Could not make readable copy of email.],
  stack: 'Error: Error: Could not make readable copy of email.
    at Response.<anonymous> (/var/task/index.js:145:11)
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:358:18)
    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:671:14)
    at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:673:12)' }
2017-02-25T10:46:40.405Z	af224ff3-fb47-11e6-9444-1f9e512246cc	{"errorMessage":"Error: Step returned error.","errorType":"Error","stackTrace":["/var/task/index.js:302:28","process._tickDomainCallback (node.js:407:9)"]}
END RequestId: af224ff3-fb47-11e6-9444-1f9e512246cc
REPORT RequestId: af224ff3-fb47-11e6-9444-1f9e512246cc	Duration: 1942.54 ms	Billed Duration: 2000 ms

Issue Analytics

State:
Created 7 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

george-viaudcommented, Jun 22, 2017

To anyone having what appears to be S3 access errors, make sure your prefix matches. I just spent quite a bit of time trying to debug an S3 access issue due to a typo in my prefix when setting up lambda (doh). This thread helped me a lot in discovering this - thank you.

1reaction

mvasincommented, Mar 1, 2017

Thank you so much for the Hangouts session, Jakub! The biggest problem seemed to be confusing interface of rule sets in SES. I was sure I had one rule, but it happened to be 1) inactive 2) there happened to be another rule.