EC2 describe_images timeout
See original GitHub issueFacing a lambda timeout issue using EC2 client describe_images(**kwargs). There are ~10000 AMI’s owned by account. Is there a workaround since there is no equivalent MaxResults
as available in the describe_snapshots method?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
EC2 describe Images API takes a lot of time to return results
EC2 describe Images API takes a lot of time to return results ... I specifically checked this twice or thrice and it takes...
Read more >describe-images with owners timeout bug · Issue #4794 - GitHub
For some reason, when I filter these images with owners, it hangs for a very long time. Without ownerId, its fine. This test...
Read more >describe-images — AWS CLI 1.27.34 Command Reference
If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds. --cli-connect-timeout...
Read more >describe-images — AWS CLI 2.9.7 Command Reference
The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout....
Read more >Amazon EC2 - Jenkins Plugins
By default, instances are terminated when the idle timeout period expires. You can change this by specifying the Stop/Disconnect on Idle ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can increase the read timeout by providing it in the config. The default value is 60 seconds. Ex:
It would also probably be useful to request that EC2 add pagination to this operation. You can do this on their service forum.
Let me know if that works.
@JordonPhillips Had raised the issue with AWS. They mentioned that it was a fringe case.
@jonathanwcrane Have they updated the API to include pagination? I had used the timeout coupled with loops and sqs queues to deregister and then delete. The queue was used since the de-registration process is not instantaneous.