AWS for Backend Developers (EC2, S3, RDS, Lambda) · 课时

保护 S3 数据访问

使用存储桶策略、ACL 和预签名 URL，为 S3 存储桶和对象配置访问控制。

保护 S3 数据访问 是 CoddyKit 上的免费 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 AWS for Backend Developers (EC2, S3, RDS, Lambda) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

S3 Security: Why It Matters

Amazon S3 is a highly durable and available storage service, but securing your data is paramount. Misconfigured S3 buckets can expose sensitive information to the public internet.

In this lesson, we'll explore key mechanisms AWS provides to control who can access your S3 data.

Access Control Basics in S3

S3 uses several layers to manage access:

Bucket Policies: JSON-based policies applied to a bucket.
Access Control Lists (ACLs): Legacy, finer-grained permissions on buckets and objects.
Pre-signed URLs: Temporary, time-limited access to specific objects.

Understanding these helps you implement the principle of least privilege.

Understanding Bucket Policies

A Bucket Policy is a resource-based policy written in JSON. It defines permissions for actions on a bucket and its objects.

These policies are powerful because they can grant or deny access to specific AWS accounts, IAM users, roles, or even anonymous users.

Anatomy of a Bucket Policy

Bucket policies consist of statements with these main elements:

Effect: Allow or Deny.
Principal: Who is allowed or denied (e.g., an IAM user ARN).
Action: What actions are allowed (e.g., s3:GetObject, s3:PutObject).
Resource: On which resource the action is allowed (e.g., arn:aws:s3:::your-bucket/*).

Bucket Policy Example: Read-Only

Here's a policy that grants an IAM user (arn:aws:iam::123456789012:user/DevUser) read-only access to all objects in my-example-bucket.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::123456789012:user/DevUser"
      },
      "Action": [
        "s3:GetObject",
        "s3:GetObjectVersion"
      ],
      "Resource": "arn:aws:s3:::my-example-bucket/*"
    }
  ]
}

Introduction to S3 ACLs

Access Control Lists (ACLs) are a legacy access control mechanism that predates bucket policies. They grant specific permissions (READ, WRITE, FULL_CONTROL) to other AWS accounts or predefined S3 groups.

ACLs are typically used for cross-account access or when an object is owned by a different account than the bucket.

ACL vs. Bucket Policy

While both control access, Bucket Policies are generally preferred for their flexibility and centralized management. They allow complex conditions and fine-grained permissions.

ACLs are simpler and are primarily used for granting basic read/write access to individual objects or when ownership of objects differs from the bucket owner (e.g., when objects are uploaded by another account).

What are Pre-signed URLs?

A Pre-signed URL gives temporary, time-limited access to a specific S3 object. An authorized user (or application with appropriate credentials) generates this URL.

It's perfect for scenarios like securely sharing a private file for a few minutes or allowing a user to upload a file directly to S3 without exposing your AWS credentials.

Generate a Pre-signed URL

Here's a Python example using the boto3 library to create a pre-signed URL for downloading an object. The URL will be valid for 3600 seconds (1 hour).

import boto3

def create_presigned_url(bucket_name, object_name, expiration=3600):
    s3_client = boto3.client('s3')
    try:
        response = s3_client.generate_presigned_url('get_object',
                                                    Params={'Bucket': bucket_name,
                                                            'Key': object_name},
                                                    ExpiresIn=expiration)
    except Exception as e:
        print(f"Error generating presigned URL: {e}")
        return None
    return response

if __name__ == '__main__':
    # Replace with your bucket and object details
    my_bucket = "your-unique-bucket-name"
    my_object = "my-secret-document.pdf"

    url = create_presigned_url(my_bucket, my_object)
    if url:
        print(f"Pre-signed URL for {my_object}:")
        print(url)
    else:
        print("Failed to generate URL.")

Quick Check

Which S3 access control method is generally preferred for comprehensive, centralized permissions on a bucket and its objects?

Recap: Securing S3 Data

We covered three key ways to secure your S3 data:

Bucket Policies: Powerful, JSON-based rules for comprehensive bucket-level access control.
ACLs: Legacy, object-level permissions for specific scenarios like cross-account uploads.
Pre-signed URLs: Temporary, time-limited access to individual objects, perfect for sharing or direct uploads.

Always apply the principle of least privilege when securing your S3 resources!

常见问题解答

「保护 S3 数据访问」课时是免费的吗？

是的 — 「保护 S3 数据访问」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程的其余内容，请升级到 CoddyKit PRO。 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程共包含 4 节课。

「保护 S3 数据访问」这节课中我会学到什么？

使用存储桶策略、ACL 和预签名 URL，为 S3 存储桶和对象配置访问控制。你通过在浏览器中直接运行的动手代码来练习 AWS for Backend Developers (EC2, S3, RDS, Lambda)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 AWS for Backend Developers (EC2, S3, RDS, Lambda) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「保护 S3 数据访问」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课中编写并运行代码吗？

能。每节 AWS for Backend Developers (EC2, S3, RDS, Lambda) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 AWS for Backend Developers (EC2, S3, RDS, Lambda)