Skip to content

Conversation

@nitrocode
Copy link
Member

what

  • feat: add source_ip_allow_list_s3_objects

why

  • Prevent S3 lock out by allowing IP addresses to block only object level permissions

references

@nitrocode nitrocode requested review from a team as code owners April 3, 2025 22:32
@nitrocode nitrocode requested review from Gowiem and RoseSecurity April 3, 2025 22:32
@mergify mergify bot added the triage Needs triage label Apr 3, 2025
@nitrocode nitrocode force-pushed the ip-prevent-lock-out branch from f2b5284 to 3aeb54b Compare April 3, 2025 22:34
@nitrocode
Copy link
Member Author

/terratest

@nitrocode nitrocode changed the title feat: add source_ip_allow_list_s3_objects feat: add source_ip_allow_list_s3_objects Apr 3, 2025
@mergify
Copy link

mergify bot commented Jul 2, 2025

💥 This pull request now has conflicts. Could you fix it @nitrocode? 🙏

@mergify mergify bot added the conflict This PR has conflicts label Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflict This PR has conflicts triage Needs triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The statement for var.source_ip_allow_list includes s3:PutBucketPolicy which locks user out of the bucket

2 participants