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

S3 Inventory Configuration Results API #4082

Closed
2 tasks
corey-cole opened this issue Apr 13, 2024 · 3 comments
Closed
2 tasks

S3 Inventory Configuration Results API #4082

corey-cole opened this issue Apr 13, 2024 · 3 comments
Assignees
Labels
feature-request This issue requests a feature. s3 service-api This issue is caused by the service API, not the SDK implementation.

Comments

@corey-cole
Copy link

Describe the feature

At present, one can only determine the results of a successful inventory configuration by logging in to the AWS console. The console shows the date and the status of the latest inventory delivery. If it is successful, it links to the S3 location of the delivery.

The following information should be available an API call:

  • Status of latest inventory delivery
  • Error message if status is not successful
  • Base directory of latest delivery if it is successful

Use Case

The inventory manifest is used to drive S3 Batch automation, and one either has to empirically determine what the path should be by concatenating a bunch of strings that come out of another API call plus a list objects call for this created prefix plus some client-side logic for item filtering by date.

Proposed Solution

s3api would have list-bucket-inventory-configuration-results command that takes bucket name and inventory configuration id. Output would be as described above (status, error message, location). Bonus points if it's the last few items with a boolean flag for latest.

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

SDK version used

1.34.83

Environment details (OS name and version, etc.)

Any

@corey-cole corey-cole added feature-request This issue requests a feature. needs-triage This issue or PR still needs to be triaged. labels Apr 13, 2024
@corey-cole
Copy link
Author

95% of the implementation is available in this gist. All this was determined empirically, so the assumptions would need some checking by someone on the service team.

@tim-finnigan tim-finnigan self-assigned this Apr 19, 2024
@tim-finnigan tim-finnigan added investigating This issue is being investigated and/or work is in progress to resolve the issue. and removed needs-triage This issue or PR still needs to be triaged. labels Apr 19, 2024
@tim-finnigan tim-finnigan added s3 service-api This issue is caused by the service API, not the SDK implementation. and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Apr 19, 2024
@tim-finnigan
Copy link
Contributor

tim-finnigan commented Apr 19, 2024

Thanks for the feature request. Since this request involves S3 APIs which are used across SDKs, we'll want to track it in our cross-SDK repository and reach out to the S3 service team for feedback. I went ahead and created aws/aws-sdk#720 for tracking going forward. I'll ask the S3 team about this request and share any updates in that issue.

Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request This issue requests a feature. s3 service-api This issue is caused by the service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants