S3 Bucket Policy配置:IP白名单限制同时豁免Snowflake角色访问
S3存储桶同时配置IP白名单与指定IAM角色豁免的实现方案
根因说明
AWS IAM策略遵循「显式拒绝 > 显式允许 > 默认拒绝」的评估逻辑:
- 首次配置失败是因为全局Deny规则未豁免Snowflake专用IAM角色,即使给该角色配置了Allow权限,只要访问IP不在白名单内,就会被优先级更高的Deny规则拦截
- 第二次配置IP限制失效是因为无全局Deny规则时,IP白名单的Allow规则仅对匿名访问生效,同账号下自带S3访问权限的IAM实体无需匹配该Allow规则即可直接访问存储桶
正确配置示例
在原Deny规则中增加IAM角色豁免的条件即可,完整策略如下:
{ "Version": "2012-10-17", "Id": "SourceIP", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::11111111111:role/snowflake-role" }, "Action": "s3:ListBucket", "Resource": "arn:aws:s3:::s3-bucket" }, { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::111111111111:role/snowflake-role" }, "Action": [ "s3:GetObject", "s3:PutObject", "s3:DeleteObject" ], "Resource": "arn:aws:s3:::s3-bucket/*" }, { "Sid": "SourceIP", "Effect": "Deny", "Principal": "*", "Action": "s3:*", "Resource": [ "arn:aws:s3:::s3-bucket", "arn:aws:s3:::s3-bucket/*" ], "Condition": { "NotIpAddress": { "aws:SourceIp": [ "10.10.100.10", "10.10.100.11", "10.10.100.12", "10.10.100.13" ] }, "StringNotEquals": { "aws:PrincipalArn": "arn:aws:iam::11111111111:role/snowflake-role" } } } ] }
配置说明
修改后的Deny规则仅在同时满足两个条件时生效:
- 请求IP不在配置的白名单范围内
- 请求发起的主体不是指定的Snowflake专用IAM角色
如果需要新增其他豁免IP校验的IAM实体,直接在StringNotEquals的aws:PrincipalArn数组中添加对应ARN即可。
内容的提问来源于stack exchange,提问作者Arun Joseph
相关产品推荐
相关产品推荐

