This product is not supported for your selected
Datadog site. (
).
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Id: f0d8781f-1991-4958-9917-d39283b168a0
Cloud Provider: aws
Framework: Terraform
Severity: High
Category: Access Control
Learn More
Description
AWS DB Snapshots contain a complete copy of your database, including all its data structures, stored procedures, and sensitive information. When a DB snapshot is made public by setting shared_accounts
to include all
, anyone with an AWS account can access and restore your database, potentially exposing confidential data or intellectual property. To mitigate this risk, always keep your DB snapshots private by ensuring the shared_accounts
attribute is either not specified or set to an empty array. Compare the secure configuration (shared_accounts = []
) with the vulnerable configuration (shared_accounts = ["all"]
). Implementing proper access controls for DB snapshots is essential for protecting sensitive data and maintaining compliance with data protection regulations.
Compliant Code Examples
resource "aws_db_snapshot" "private_snapshot" {
db_snapshot_identifier = "private-db-snapshot"
db_instance_identifier = "my-db-instance"
}
resource "aws_db_snapshot" "private_snapshot" {
db_snapshot_identifier = "private-db-snapshot"
db_instance_identifier = "my-db-instance"
shared_accounts = []
}
Non-Compliant Code Examples
resource "aws_db_snapshot" "public_snapshot" {
db_snapshot_identifier = "public-db-snapshot"
db_instance_identifier = "my-db-instance"
shared_accounts = ["all"]
}