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 Package: Server-side Encryption #82

Merged
merged 2 commits into from
May 13, 2017
Merged

Conversation

jonsharratt
Copy link
Member

What did you implement:

By default add AES256 encryption for data sitting in S3.

Use Server-Side Encryption with Amazon S3-Managed Keys (SSE-S3)
Each object is encrypted with a unique key employing strong multi-factor encryption. As an additional safeguard, it encrypts the key itself with a master key that it regularly rotates. Amazon S3 server-side encryption uses one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256), to encrypt your data.

How did you implement it:

  • Added bucket policy to enforce encrypted data to ensure all objects are published encrypted.

How can we verify it:

  • npm t
  • Deploy registry and attempt publish and dist-tags operations

Todos:

  • Write tests
    Write documentation
  • Fix linting errors
  • Tag ready for review or wip

Is this a breaking change?: YES

@jonsharratt jonsharratt changed the title S3 Pacakge: Server-side Encryption S3 Package: Server-side Encryption May 11, 2017
@jonsharratt jonsharratt removed the wip label May 13, 2017
@jonsharratt jonsharratt merged commit 356adb8 into master May 13, 2017
@jonsharratt jonsharratt deleted the default-encryption branch May 13, 2017 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant