Add support for sharing encrypted EBS resources cross account #70
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.
Few changes:
encrypted
attribute toAWSVolume
class.CreateVolumeCopy()
with a destination account that is not the same as the source account, we now check if the target volume is encrypted. If so, a one-time use KMS shared key (between source and destination account) is generated. Subsequently, the initial target volume is duplicated + encrypted with the temporary shared key. We then use this temporary volume for the remainder of the code (i.e., getting a new snapshot out of that temporary volume, sharing it with the destination account, and creating a copy within the destination account).After execution, temporary volumes, snapshots and keys are deleted. The copy of the volume that sits in the destination account is encrypted with the default EBS/KMS key particular to that account.
Closes #63
Signed-off-by: Theo Giovanna gtheo@google.com