Difference between revisions of "AWS S3 encryption"
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
*At [[rest]]: | *At [[rest]]: | ||
** [[Server Side Encryption]] (SSE): | ** [[Server Side Encryption]] (SSE): | ||
− | **S3 Managed Keys (SSE-S3; 256bit); | + | ** [[S3 Managed Keys]] (SSE-S3; 256bit); |
− | **[[AWS Key Management Service]], Managed Keys (SSE-KMS) | + | ** [[AWS Key Management Service]], Managed Keys (SSE-KMS) |
− | **Server Side Encryption with Customer Provided Keys (SSE-C) | + | ** Server Side Encryption with Customer Provided Keys (SSE-C) |
* Client Side Encryption (user encypts data on their local machine and then upload to AWS S3) | * Client Side Encryption (user encypts data on their local machine and then upload to AWS S3) | ||
Revision as of 03:59, 23 May 2024
Encryption (2017) is supported in AWS S3 (default Advanced Encryption Standard (AES) 256bit)
- In transit (SSL/TLS)
- At rest:
- Server Side Encryption (SSE):
- S3 Managed Keys (SSE-S3; 256bit);
- AWS Key Management Service, Managed Keys (SSE-KMS)
- Server Side Encryption with Customer Provided Keys (SSE-C)
- Client Side Encryption (user encypts data on their local machine and then upload to AWS S3)
Related
See also
- AWS S3,
aws s3, aws s3api, aws s3control, s3:
, Amazon S3 Storage Lens, AWS S3 replication, CRR, SSR, CAR, S3 Replication Time Control (S3 RTC), Website endpoint, Amazon Macie, Versioning, Lifecycle, Encryption, logging, Amazon S3 Inventory, Amazon S3 Batch Operations, Storage Classes, Amazon S3 clients, Terraform S3, AWS canned ACLs, Directory buckets, security,PutObject
Advertising: