aws-sdk-js-v3
aws-sdk-js-v3 copied to clipboard
Batch request for describeSnapshotAttribute
Describe the feature
I'd like to request two enhancements in the ec2 client.
- The describeSnapshot call should have a range parameter which should allow to list the snapshots within the specified dates. lets say from past 1 month.
- We should have the createVolumePermission returned within the describeSnapshot
Use Case
- I need to fetch the snapshots and im using this call . I have like a lot of snapshots and i only want to fetch the snapshots from the last 1 month. And i simply cannot because there is no range filter. The attribute we currently have as start-time needs to have the exact time stamp it was initiated.
- And this issue eventually arises the second issue for me which is describeSnapshotAttributes, as this call would just allow me to make one call at a time and it takes a lot of time for me to make this call for each snapshot. and i only need createVolumePermission attribute from this call. The workaround for this would be to actually have the createVolumePermission attribute present in the describeSnapshot call as well.
Proposed Solution
Solution 1: Add the range filter in describeSnapshot call Solution 2: Add the createVolumePermission attribute in describeSnapshot itself instead of the describeSnapshotAttributes
Other Information
No response
Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
SDK version used
v3
Environment details (OS name and version, etc.)
mac
Hi @alphadev4 - thanks for reaching out.
The changes you're requesting have to be made in service side EC2 and SDK team does not have direct control over the service models or the ability to make the requested changes. However, we've escalated your request to the EC2 team on your behalf (Reference: P152746014).
Since there's no pending action item for SDK team, I'm going to close this. Please feel free to reach out to service team directly via AWS Support.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.