feat(rds): support 's3export' for Postgres database instances #16122
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #14546, Postgres database instances did not support
s3export
when most of thes3 import/export
features were added in #10370. This PR fills in that gap now thats3export
is available for Postgres.The supported versions are documented here and I manually verified via AWS CLI that Postgres 13+ supports
s3export
as well.Looking into the test suite, I think it makes more sense to modify the existing test than to create an entirely new one, similar to how other database instances test s3 import/export at the same time. But I can also move it to its own test if necessary.
I also fixed a very minor doc typo in
cluster-instance.ts
.Closes #14546.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license