Skip to content

eli-386 blocking s3 public access at account level#278

Merged
eddalmond1 merged 3 commits intomainfrom
feature/eja-eli-386-block-public-access-to-s3-at-account-level
Aug 7, 2025
Merged

eli-386 blocking s3 public access at account level#278
eddalmond1 merged 3 commits intomainfrom
feature/eja-eli-386-block-public-access-to-s3-at-account-level

Conversation

@eddalmond1
Copy link
Copy Markdown
Collaborator

Description

Adding account level s3 public block

Context

We block public access to s3 buckets we create. Adding in account level protections also means malicious actors / inadvertent s3 creation is protected by default from being made public.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@eddalmond1 eddalmond1 merged commit 52c2d16 into main Aug 7, 2025
22 checks passed
@eddalmond1 eddalmond1 deleted the feature/eja-eli-386-block-public-access-to-s3-at-account-level branch September 26, 2025 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants