Overview

Implements layered S3 security controls across five workflows: securing new buckets,

auditing existing configurations, remediating findings, configuring encryption, and

enabling monitoring. Follows AWS Well-Architected security best practices.

Execute commands using the AWS MCP server when connected (sandboxed execution, audit logging, observability). Fall back to AWS CLI or shell otherwise.

Common Tasks

0. Verify Dependencies

Check for required tools before starting.

Constraints:

You MUST inform the user if required tools are missing

You SHOULD confirm credentials with

aws sts get-caller-identity

See

references/iam-permissions.md

for IAM permissions by workflow.

1. Classify the Request

User intent

Workflow

Secure a new bucket

A: Secure New Bucket

Audit / review existing bucket

B: Audit Existing Bucket

Fix a specific finding

C: Remediate Issue

Configure encryption

D: Configure Encryption

Enable logging / monitoring

E: Enable Monitoring

Constraints:

You MUST ask for all required parameters upfront

You MUST confirm bucket name and region before any write operation

You MAY infer region from user context if clearly stated

You SHOULD run

aws iam simulate-principal-policy

to validate permissions before write operations

You SHOULD display write commands and wait for confirmation before executing

put-bucket-policy Safety Rules

These rules apply to ALL workflows that call

put-bucket-policy

:

You MUST attempt to retrieve the existing policy first (

aws s3api get-bucket-policy

) —

put-bucket-policy

replaces the entire policy

If a policy exists, you MUST back it up before modifying:

aws s3api get-bucket-policy --bucket --output text > backup-policy-$(date +%s).json

If

NoSuchBucketPolicy

is returned, proceed with a new policy — no backup is needed

You MUST merge new statements into the existing policy's Statement array (if one exists)

You MUST validate merged JSON syntax before applying (e.g.

echo '' | python3 -m json.tool

)

You SHOULD display the full

put-bucket-policy

command and wait for confirmation

2. Workflow A — Secure New Bucket

See

references/workflows.md

for full CLI steps.

Required steps (execute in order, do not skip):

Create bucket with

--bucket-namespace account-regional

Enable versioning

Enable encryption (SSE-S3 + Bucket Keys + block SSE-C)

Enable logging (ask user which option — conditional)

Enforce HTTPS-only via

DenyInsecureTransport

bucket policy

Enable ABAC

Constraints:

You MUST pass

--bucket-namespace account-regional

on

create-bucket

call — this is REQUIRED, not optional. Example:

aws s3api create-bucket --bucket --bucket-namespace account-regional --region

You MUST NOT change Block Public Access — S3 enables it by default on new buckets

You MUST NOT change ACL ownership controls — S3 disables ACLs (

BucketOwnerEnforced

) by default

You MUST apply a bucket policy with a

DenyInsecureTransport

statement that denies

s3:*

when

aws:SecureTransport

is

false

— this is REQUIRED, not optional. Example:

aws s3api put-bucket-policy --bucket --policy '{"Version":"2012-10-17","Statement":[{"Sid":"DenyInsecureTransport","Effect":"Deny","Principal":"","Action":"s3:","Resource":["arn:aws:s3:::/*","arn:aws:s3:::"],"Condition":{"Bool":{"aws:SecureTransport":"false"}}}]}'

You MUST ask the user which logging option they want before step 4

You MUST follow the

put-bucket-policy safety rules

for steps 4 and 5

You SHOULD confirm each step succeeded before proceeding

3. Workflow B — Audit Existing Bucket

See

references/audit-checklist.md

for the full checklist.

Constraints:

You MUST run all read-only audit commands before reporting findings

You MUST NOT execute any write or modify commands during an audit

You MUST report each control as PASS / FAIL / NOT CONFIGURED with severity

For logging: report PASS if either S3 server access logging OR CloudTrail data events are enabled; NOT CONFIGURED only if neither

4. Workflow C — Remediate Issue

See

references/remediation.md

for fix commands by issue type.

Constraints:

You MUST identify the issue type before applying any fix

You MUST follow the

put-bucket-policy safety rules

when modifying policies

You MUST re-run the relevant audit check after applying the fix to confirm resolution

5. Workflow D — Configure Encryption

See

references/encryption.md

for encryption options and commands.

Constraints:

You MUST default to SSE-S3 with S3 Bucket Keys and SSE-C blocked unless the user explicitly requests KMS

When using SSE-KMS, you MUST use a customer managed key — NEVER the AWS managed

aws/s3

key

You MUST specify customer-managed KMS keys by full ARN, not alias

You MUST include

BucketKeyEnabled: true

and

BlockedEncryptionTypes: [SSE-C]

in all configurations

Note

The S3 API accepts aws/s3 and aliases without error — agent-enforced constraints. Verify with get-bucket-encryption after applying. 6. Workflow E — Enable Monitoring See references/workflows.md for full CLI steps. Constraints: You MUST check whether a GuardDuty detector already exists before creating one You MUST use the trail's home region (not the bucket's region) for CloudTrail commands You SHOULD enable all four core recommended AWS Config rules Troubleshooting ObjectLockConfigurationNotFoundError — Object Lock is not enabled. Treat as NOT CONFIGURED, not a failure. AccessDenied on audit commands — Check IAM policy, bucket policy, Block Public Access, VPC endpoint policy, and SCPs/RCPs. Use aws iam simulate-principal-policy to diagnose. put-bucket-policy silently removes existing statements — See put-bucket-policy safety rules . GuardDuty BadRequestException: detector already exists — Run aws guardduty list-detectors first; only call create-detector if empty. CloudTrail changes not taking effect — Verify you are using --region , not the bucket's region. Find it with aws cloudtrail describe-trails --query 'trailList[*].[Name,HomeRegion]' . Additional Resources references/iam-permissions.md — IAM permissions by workflow references/audit-checklist.md — Per-control checklist with severity and pass conditions references/encryption.md — Encryption options, KMS guidance, SSE-C blocking references/remediation.md — Fix commands for common findings references/workflows.md — Full CLI command sequences for Workflows A and E AWS S3 Security Best Practices AWS Well-Architected Security Pillar