🔐
AWS SCS-C01
  • Practice Test Scores
  • Domain 1 - Incident Response
    • Incident Response
    • Exposed AWS Access Keys
    • Compromised EC2 Instance
    • How do you report abuse of AWS resources?
    • GuardDuty
    • Penetration Testing
  • Domain 2 - Logging & Monitoring
    • Some Basics
    • Inspector
    • Security Hub
    • AWS WAF
    • Systems Manager
    • Systems Manager Features
    • CloudWatch Logs
    • Athena
    • CloudTrail
    • Config
    • Trusted Advisor
    • CloudTrail Log File Integrity
    • Macie
    • S3 Event Notifications
    • VPC Flow Logs
    • Centralized Logging Architecture
  • Domain 3 - Infrastructure Security
    • Bastion Hosts
    • Site-to-Site VPN
    • VPC Peering
    • VPC Endpoints
    • Network ACL
    • Firewall vs IPS vs IDS
    • EBS
    • CloudFront
    • Shield
    • Mitigating DDoS Attacks
    • EC2 Key Pair Troubleshooting
    • EC2 Tenancy
    • Artifact
    • Lambda@Edge
    • Simple Email Service (SES)
    • DNS Support in VPC
  • Domain 4 - Identity & Access Management
    • Organizations
    • IAM Policy Evaluation Logic
    • Understanding IAM Policies
    • IAM Tutorial: Delegate access across AWS accounts using IAM roles
    • External ID
    • iptables
    • IAM policy elements: Version
    • IAM policy elements: Variables and tags
    • Policy elements: Principal and NotPrincipal
    • IAM policy elements: Condition
    • Security Token Service (STS)
    • Identity federation in AWS
    • Enabling SAML for your AWS resources
    • Single Sign-On
    • Cognito
    • Directory Service
    • Trusts in Active Directory
    • Example S3 Bucket Policies
    • Cross-account access to S3 buckets using Resource-based policies and IAM policies
    • S3 Access Control Lists (ACLs)
    • Presigned URLs
    • S3 Versioning
    • S3 Cross-Region Replication (CRR)
    • S3 Object Lock
    • Configuring MFA-protected API access
    • IAM Permission Boundaries
  • Domain 5 - Data Protection
  • CloudHSM
  • Key Management Service (KMS)
  • Symmetric CMKs vs Asymmetric CMKs
  • Data Key Caching
  • Deleting KMS CMKs
  • Default KMS Key Policy
  • Managing access to KMS CMKs
  • KMS CMK Key Types
  • Rotating KMS CMKs
  • Example Key Policies for KMS Questions
  • KMS Grants
  • KMS CLI Commands
  • Importing key material in KMS
  • KMS Condition Keys
  • Migrating Encrypted KMS Data Across Regions
  • KMS Encryption Context
  • CloudHSM vs KMS
  • S3 Data Encryption
  • Application Load Balancer (ALB)
  • ELB Listeners Part 1
  • ELB Listeners Part 2
  • AWS Certificate Manager (ACM)
  • Glacier
  • DynamoDB Encryption
  • AWS Secrets Manager
  • Summaries
    • Domain 1
    • Domain 2
    • Domain 3
    • Domain 4
    • Domain 5
Powered by GitBook
On this page
  • Server-side Encryption
  • Server-side Encryption with S3-managed encryption keys (SSE-S3)
  • Server-side Encryption using KMS CMKs (SSE-KMS)
  • Server-side Encryption with customer-provided encryption keys (SSE-C)
  • Client-side Encryption

Was this helpful?

S3 Data Encryption

  • Data protection refers to protecting data while in-transit and at rest.

  • You can protect data in transit using SSL/TLS or client-side encryption.

  • You have the following options for protecting data at rest in S3:

    • Server-Side Encryption:

      • Request S3 to encrypt your object before saving it on disks in its data centres and then decrypt it when you download the objects.

    • Client-Side Encryption:

      • Encrypt data client-side and upload the encrypted data to S3. In this case, you manage the encryption process, the encryption keys, and related tools.

Server-side Encryption

Server-side Encryption with S3-managed encryption keys (SSE-S3)

  • Each object is encrypted with a unique key.

  • As an additional safeguard, it encrypts the key itself with a master key that it regularly rotates.

  • It uses one of the strongest block ciphers available, AES-256, to encrypt your data.

Server-side Encryption using KMS CMKs (SSE-KMS)

  • It is similar to SSE-S3, but with some additional benefits and charges for using this service.

  • There are separate permissions for the use of a CMK that provides added protection against unauthorized access of your objects in S3.

  • It also provides you with an audit trail that shows when your CMK was used and by whom.

  • You can create and manage customer managed CMKs or use AWS managed CMKs that are unique to you, your service, and your Region.

Server-side Encryption with customer-provided encryption keys (SSE-C)

  • The customer manages the encryption keys and S3 manages the encryption, as it writes to disks, and decryption, when you access your objects.

Client-side Encryption

  • To enable client-side encryption, you have the following options:

    • Use a KMS CMK.

    • Use a master key that you store within your application.

PreviousCloudHSM vs KMSNextApplication Load Balancer (ALB)

Last updated 4 years ago

Was this helpful?