Move s3:PutBucketNotification from S3 enum to S3 post-exploitation

[carlospolop]

What

Moves the s3:PutBucketNotification — wire future objects into a pre-authorized Lambda technique out of the S3 enumeration page and into the S3 post-exploitation page.

• Source: aws-services/aws-s3-athena-and-glacier-enum.md
• Destination: aws-post-exploitation/aws-s3-post-exploitation/README.md, under Pivoting (right after the s3:PutObject → SSM AWS-RunRemoteScript object-overwrite technique it most resembles)

Why

s3:PutBucketNotification isn't enumeration — it's a cross-service, delayed code-execution / pivot primitive (route later objects into an already-authorized Lambda and its execution role). It belongs alongside the other object-overwrite → execution pivots in the post-exploitation page.

Details

• Section content moved verbatim; heading demoted ### → #### to sit under Pivoting.
• Its two references were removed from the enum reference list ([38], [39]) and re-added to the post-exploitation reference list as [29], [30], with the inline <sup> markers updated to match.
• Net change is a pure move: 44 insertions / 44 deletions.

🤖 Generated with Claude Code