- Newest
- Most votes
- Most comments
Hello. In AWS Identity and Access Management (IAM), you can use policies to control what actions a user or role can perform on AWS resources, but IAM policies are typically not used to filter or limit the specific resources that are visible to a user. IAM policies focus on granting or denying permissions for actions on resources, rather than controlling which resources are visible in a listing. Because in most cases you must provide a List of permissions on all resources contained in one AWS service.
However, if you want to restrict a user's ability to list or access specific AWS resources (e.g., Lambda functions or SQS queues) while allowing access to others, you can use resource-based policies and service-specific mechanisms to achieve this.
For example use "Conditions":
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "lambda:ListFunctions",
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "lambda:InvokeFunction",
"Resource": "arn:aws:lambda:us-east-1:123456789012:function/allowed-function",
"Condition": {
"StringEquals": {
"aws:RequestTag/Environment": "Production"
}
}
}
]
}
Best regards, Andrii
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
I'm grateful for the answer, though I'm also saddened to know there's no way to control the visibility of the items more granularly. Anyway, thank your for the quick response!