Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task timed out after 300.07 seconds #12

Open
HareshChhelana opened this issue Feb 7, 2018 · 1 comment
Open

Task timed out after 300.07 seconds #12

HareshChhelana opened this issue Feb 7, 2018 · 1 comment

Comments

@HareshChhelana
Copy link

HareshChhelana commented Feb 7, 2018

{
"errorMessage": "2018-02-07T13:38:33.285Z 7d79ae5e-0c0b-11e8-9c34-071d38a89c78 Task timed out after 300.07 seconds"
}

Getting above error when try to run below code

const mpromise = require('promise');

const setupS3Chrome = () => {
return new mpromise(function (resolve, reject) {
const params = {
Bucket: config.remoteChromeS3Bucket,
Key: config.remoteChromeS3Key
};
console.log(params);
s3.getObject(params).createReadStream().on('error', err => reject(err)).pipe(tar.x({
C: config.setupChromePath
})).on('error', err => reject(err)).on('end', () => resolve());
});
};

@HareshChhelana HareshChhelana reopened this Feb 7, 2018
@HareshChhelana HareshChhelana changed the title Unhandled rejection NoSuchKey: The specified key does not exist. Task timed out after 300.07 seconds Feb 7, 2018
@lucianweber
Copy link

I had the same problem. In my case, I had not configured my VPC correctly in order for my Lambda Function to have access to the internet.

You should check out this article.
After I had configured my VPC correctly (2 private subnets, 1 public subnet) and added only the two private subnets to my Lambda Function, I was able to access the Internet from within and the S3 Download started working too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants