simulateCustomPolicy method
- required List<
String> actionNames, - required List<
String> policyInputList, - String? callerArn,
- List<
ContextEntry> ? contextEntries, - String? marker,
- int? maxItems,
- List<
String> ? permissionsBoundaryPolicyInputList, - List<
String> ? resourceArns, - String? resourceHandlingOption,
- String? resourceOwner,
- String? resourcePolicy,
Simulate how a set of IAM policies and optionally a resource-based policy works with a list of API operations and AWS resources to determine the policies' effective permissions. The policies are provided as strings.
The simulation does not perform the API operations; it only checks the authorization to determine if the simulated policies allow or deny the operations.
If you want to simulate existing policies that are attached to an IAM user, group, or role, use SimulatePrincipalPolicy instead.
Context keys are variables that are maintained by AWS and its services and
which provide details about the context of an API query request. You can
use the Condition
element of an IAM policy to evaluate
context keys. To get the list of context keys that the policies require
for correct simulation, use GetContextKeysForCustomPolicy.
If the output is long, you can use MaxItems
and
Marker
parameters to paginate the results.
May throw InvalidInputException. May throw PolicyEvaluationException.
Parameter actionNames
:
A list of names of API operations to evaluate in the simulation. Each
operation is evaluated against each resource. Each operation must include
the service identifier, such as iam:CreateUser
. This
operation does not support using wildcards (*) in an action name.
Parameter policyInputList
:
A list of policy documents to include in the simulation. Each document is
specified as a string containing the complete, valid JSON text of an IAM
policy. Do not include any resource-based policies in this parameter. Any
resource-based policy must be submitted with the
ResourcePolicy
parameter. The policies cannot be "scope-down"
policies, such as you could include in a call to GetFederationToken
or one of the AssumeRole
API operations. In other words, do not use policies designed to restrict
what a user can do while using the temporary credentials.
The regex pattern used to validate this parameter is a string of characters consisting of the following:
-
Any printable ASCII character ranging from the space character
(
\u0020
) through the end of the ASCII character range -
The printable characters in the Basic Latin and Latin-1 Supplement
character set (through
\u00FF
) -
The special characters tab (
\u0009
), line feed (\u000A
), and carriage return (\u000D
)
Parameter callerArn
:
The ARN of the IAM user that you want to use as the simulated caller of
the API operations. CallerArn
is required if you include a
ResourcePolicy
so that the policy's Principal
element has a value to use in evaluating the policy.
You can specify only the ARN of an IAM user. You cannot specify the ARN of an assumed role, federated user, or a service principal.
Parameter contextEntries
:
A list of context keys and corresponding values for the simulation to use.
Whenever a context key is evaluated in one of the simulated IAM
permissions policies, the corresponding value is supplied.
Parameter marker
:
Use this parameter only when paginating results and only after you receive
a response indicating that the results are truncated. Set it to the value
of the Marker
element in the response that you received to
indicate where the next call should start.
Parameter maxItems
:
Use this only when paginating results to indicate the maximum number of
items you want in the response. If additional items exist beyond the
maximum you specify, the IsTruncated
response element is
true
.
If you do not include this parameter, the number of items defaults to 100.
Note that IAM might return fewer results, even when there are more results
available. In that case, the IsTruncated
response element
returns true
, and Marker
contains a value to
include in the subsequent call that tells the service where to continue
from.
Parameter permissionsBoundaryPolicyInputList
:
The IAM permissions boundary policy to simulate. The permissions boundary
sets the maximum permissions that an IAM entity can have. You can input
only one permissions boundary when you pass a policy to this operation.
For more information about permissions boundaries, see Permissions
Boundaries for IAM Entities in the IAM User Guide. The policy
input is specified as a string that contains the complete, valid JSON text
of a permissions boundary policy.
The regex pattern used to validate this parameter is a string of characters consisting of the following:
-
Any printable ASCII character ranging from the space character
(
\u0020
) through the end of the ASCII character range -
The printable characters in the Basic Latin and Latin-1 Supplement
character set (through
\u00FF
) -
The special characters tab (
\u0009
), line feed (\u000A
), and carriage return (\u000D
)
Parameter resourceArns
:
A list of ARNs of AWS resources to include in the simulation. If this
parameter is not provided, then the value defaults to *
(all
resources). Each API in the ActionNames
parameter is
evaluated for each resource in this list. The simulation determines the
access result (allowed or denied) of each combination and reports it in
the response.
The simulation does not automatically retrieve policies for the specified
resources. If you want to include a resource policy in the simulation,
then you must include the policy as a string in the
ResourcePolicy
parameter.
If you include a ResourcePolicy
, then it must be applicable
to all of the resources included in the simulation or you receive an
invalid input error.
For more information about ARNs, see Amazon Resource Names (ARNs) and AWS Service Namespaces in the AWS General Reference.
Parameter resourceHandlingOption
:
Specifies the type of simulation to run. Different API operations that
support resource-based policies require different combinations of
resources. By specifying the type of simulation to run, you enable the
policy simulator to enforce the presence of the required resources to
ensure reliable simulation results. If your simulation does not match one
of the following scenarios, then you can omit this parameter. The
following list shows each of the supported scenario values and the
resources that you must define to run the simulation.
Each of the EC2 scenarios requires that you specify instance, image, and security-group resources. If your scenario includes an EBS volume, then you must specify that volume as a resource. If the EC2 scenario includes VPC, then you must supply the network-interface resource. If it includes an IP subnet, then you must specify the subnet resource. For more information on the EC2 scenario options, see Supported Platforms in the Amazon EC2 User Guide.
-
EC2-Classic-InstanceStore
instance, image, security-group
-
EC2-Classic-EBS
instance, image, security-group, volume
-
EC2-VPC-InstanceStore
instance, image, security-group, network-interface
-
EC2-VPC-InstanceStore-Subnet
instance, image, security-group, network-interface, subnet
-
EC2-VPC-EBS
instance, image, security-group, network-interface, volume
-
EC2-VPC-EBS-Subnet
instance, image, security-group, network-interface, subnet, volume
Parameter resourceOwner
:
An ARN representing the AWS account ID that specifies the owner of any
simulated resource that does not identify its owner in the resource ARN.
Examples of resource ARNs include an S3 bucket or object. If
ResourceOwner
is specified, it is also used as the account
owner of any ResourcePolicy
included in the simulation. If
the ResourceOwner
parameter is not specified, then the owner
of the resources and the resource policy defaults to the account of the
identity provided in CallerArn
. This parameter is required
only if you specify a resource-based policy and account that owns the
resource is different from the account that owns the simulated calling
user CallerArn
.
The ARN for an account uses the following syntax:
arn:aws:iam::AWS-account-ID:root
. For example, to
represent the account with the 112233445566 ID, use the following ARN:
arn:aws:iam::112233445566-ID:root
.
Parameter resourcePolicy
:
A resource-based policy to include in the simulation provided as a string.
Each resource in the simulation is treated as if it had this policy
attached. You can include only one resource-based policy in a simulation.
The regex pattern used to validate this parameter is a string of characters consisting of the following:
-
Any printable ASCII character ranging from the space character
(
\u0020
) through the end of the ASCII character range -
The printable characters in the Basic Latin and Latin-1 Supplement
character set (through
\u00FF
) -
The special characters tab (
\u0009
), line feed (\u000A
), and carriage return (\u000D
)
Implementation
Future<SimulatePolicyResponse> simulateCustomPolicy({
required List<String> actionNames,
required List<String> policyInputList,
String? callerArn,
List<ContextEntry>? contextEntries,
String? marker,
int? maxItems,
List<String>? permissionsBoundaryPolicyInputList,
List<String>? resourceArns,
String? resourceHandlingOption,
String? resourceOwner,
String? resourcePolicy,
}) async {
ArgumentError.checkNotNull(actionNames, 'actionNames');
ArgumentError.checkNotNull(policyInputList, 'policyInputList');
_s.validateStringLength(
'callerArn',
callerArn,
1,
2048,
);
_s.validateStringLength(
'marker',
marker,
1,
320,
);
_s.validateNumRange(
'maxItems',
maxItems,
1,
1000,
);
_s.validateStringLength(
'resourceHandlingOption',
resourceHandlingOption,
1,
64,
);
_s.validateStringLength(
'resourceOwner',
resourceOwner,
1,
2048,
);
_s.validateStringLength(
'resourcePolicy',
resourcePolicy,
1,
131072,
);
final $request = <String, dynamic>{};
$request['ActionNames'] = actionNames;
$request['PolicyInputList'] = policyInputList;
callerArn?.also((arg) => $request['CallerArn'] = arg);
contextEntries?.also((arg) => $request['ContextEntries'] = arg);
marker?.also((arg) => $request['Marker'] = arg);
maxItems?.also((arg) => $request['MaxItems'] = arg);
permissionsBoundaryPolicyInputList
?.also((arg) => $request['PermissionsBoundaryPolicyInputList'] = arg);
resourceArns?.also((arg) => $request['ResourceArns'] = arg);
resourceHandlingOption
?.also((arg) => $request['ResourceHandlingOption'] = arg);
resourceOwner?.also((arg) => $request['ResourceOwner'] = arg);
resourcePolicy?.also((arg) => $request['ResourcePolicy'] = arg);
final $result = await _protocol.send(
$request,
action: 'SimulateCustomPolicy',
version: '2010-05-08',
method: 'POST',
requestUri: '/',
exceptionFnMap: _exceptionFns,
shape: shapes['SimulateCustomPolicyRequest'],
shapes: shapes,
resultWrapper: 'SimulateCustomPolicyResult',
);
return SimulatePolicyResponse.fromXml($result);
}