Help Center/ Identity and Access Management_Identity and Access Management (New Edition)/ Service Authorization Reference/ Identity Policy–based Authorization/ Management & Governance/ Resource Formation Service (RFS)
Updated on 2025-12-08 GMT+08:00
View PDF
Share

Resource Formation Service (RFS)

IAM provides system-defined identity policies to define typical cloud service permissions. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by STS, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column is empty (-) for an action, the action does not support any condition keys.

    For details about the condition keys defined by STS, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for IAC.

Table 1 Actions supported by IAC

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

rf:privateTemplate:list

Grants permission to obtain private template list of project.

list

privateTemplate *

-

-

rf:privateTemplate:create

Grants permission to create a private template.

write

privateTemplate *

-

-

rf:privateTemplate:delete

Grants permission to delete a private template.

write

privateTemplate *

-

-

rf:privateTemplate:showMetadata

Grants permission to display the details of private template.

read

privateTemplate *

-

-

rf:privateTemplate:updateMetadata

Grants permission to update the metadata of private template.

write

privateTemplate *

-

-

rf:privateTemplate:listVersions

Grants permission to display all version details of private template.

list

privateTemplate *

-

-

rf:privateTemplate:createVersion

Grants permission to create a private template version.

write

privateTemplate *

-

-

rf:privateTemplate:showVersionContent

Grants permission to obtain the content of private template version.

read

privateTemplate *

-

-

rf:privateTemplate:deleteVersion

Grants permission to delete a private template version.

write

privateTemplate *

-

-

rf:privateTemplate:showVersionMetadata

Grants permission to get the metadata of private template version.

read

privateTemplate *

-

-

rf:stack:create

Grants permission to create a stack.

write

stack *

-

rf:stack:createStack

rf:stack:deploy

Grants permission to deploy a stack.

write

stack *

-

rf:stack:deployStack

rf:stack:list

Grants permission to list all stacks.

list

stack *

-

rf:stack:listStacks

rf:stack:getMetadata

Grants permission to get the metadata of a stack.

read

stack *

-

rf:stack:getStackMetadata

rf:stack:delete

Grants permission to delete a stack.

write

stack *

-

rf:stack:deleteStack

rf:stack:getTemplate

Grants permission to get the template of a stack.

read

stack *

-

rf:stack:getStackTemplate

rf:stack:listEvents

Grants permission to list deployment events of a stack.

list

stack *

-

rf:stack:listStackEvents

rf:stack:listResources

Grants permission to list all resources of a stack.

list

stack *

-

rf:stack:listStackResources

rf:stack:listOutputs

Grants permission to list all outputs of a stack.

list

stack *

-

rf:stack:listStackOutputs

rf:stack:createExecutionPlan

Grants permission to create an execution plan.

write

stack *

-

-

rf:stack:getExecutionPlanMetadata

Grants permission to get the metadata of an execution plan.

read

stack *

-

-

rf:stack:getExecutionPlan

Grants permission to get an execution plan.

read

stack *

-

-

rf:stack:applyExecutionPlan

Grants permission to apply an execution plan.

write

stack *

-

-

rf:stack:listExecutionPlans

Grants permission to list all execution plans.

list

stack *

-

-

rf:stack:deleteExecutionPlan

Grants permission to delete an execution plan.

write

stack *

-

-

rf:stack:continueRollback

Grants permission to continue rolling back the stack.

write

stack *

-

rf:stack:continueRollbackStack

rf:stack:continueDeploy

Grants permission to continue to deploy the stack.

write

stack *

-

rf:stack:continueDeployStack

rf:stack:estimateExecutionPlanPrice

Grants permission to estimate the price of an execution plan.

read

stack *

-

-

rf:stack:update

Grants permission to update stack properties.

write

stack *

-

rf:stack:updateStack

rf:stackSet:create

Grants permission to create a stack set.

write

stackSet *

-

-

rf:stackSet:list

Grants permission to list all stack sets.

list

stackSet *

-

-

rf:stackSet:showTemplate

Grants permission to show the template of a stack set.

read

stackSet *

-

-

rf:stackSet:showMetadata

Grants permission to show the metadata of a stack set.

read

stackSet *

-

-

rf:stackSet:deploy

Grants permission to deploy a stack set.

write

stackSet *

-

-

rf:stackSet:delete

Grants permission to delete a stack set.

write

stackSet *

-

-

rf:stackSet:update

Grants permission to update stack set properties.

write

stackSet *

-

-

rf:stackSet:listStackInstances

Grants permission to list all stack instances.

list

stackSet *

-

-

rf:stackSet:createStackInstances

Grants permission to create stack instances.

write

stackSet *

-

-

rf:stackSet:deleteStackInstances

Grants permission to delete stack instances.

write

stackSet *

-

-

rf:stackSet:showOperationMetadata

Grants permission to show the metadata of an stack set operation.

read

stackSet *

-

-

rf:stackSet:listOperations

Grants permission to list all stack set operations.

list

stackSet *

-

-

Each API of IAC usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by IAC APIs

API

Action

Dependencies

GET /v1/{project_id}/templates

rf:privateTemplate:list

-

POST /v1/{project_id}/templates

rf:privateTemplate:create

-

DELETE /v1/{project_id}/templates/{template_name}

rf:privateTemplate:delete

-

GET /v1/{project_id}/templates/{template_name}/metadata

rf:privateTemplate:showMetadata

-

PATCH /v1/{project_id}/templates/{template_name}/metadata

rf:privateTemplate:updateMetadata

-

GET /v1/{project_id}/templates/{template_name}/versions

rf:privateTemplate:listVersions

-

POST /v1/{project_id}/templates/{template_name}/versions

rf:privateTemplate:createVersion

-

GET /v1/{project_id}/templates/{template_name}/versions/{version_id}

rf:privateTemplate:showVersionContent

-

DELETE /v1/{project_id}/templates/{template_name}/versions/{version_id}

rf:privateTemplate:deleteVersion

-

GET /v1/{project_id}/templates/{template_name}/versions/{version_id}/metadata

rf:privateTemplate:showVersionMetadata

-

POST /v1/{project_id}/stacks

rf:stack:create
  • kms:cmk:decryptDataKey
  • iam:agencies:pass

POST /v1/{project_id}/stacks/{stack_name}/deployments

rf:stack:deploy

kms:cmk:decryptDataKey

GET /v1/{project_id}/stacks

rf:stack:list

-

GET /v1/{project_id}/stacks/{stack_name}/metadata

rf:stack:getMetadata

-

DELETE /v1/{project_id}/stacks/{stack_name}

rf:stack:delete

-

GET /v1/{project_id}/stacks/{stack_name}/templates

rf:stack:getTemplate

-

GET /v1/{project_id}/stacks/{stack_name}/events

rf:stack:listEvents

-

GET /v1/{project_id}/stacks/{stack_name}/resources

rf:stack:listResources

-

GET /v1/{project_id}/stacks/{stack_name}/outputs

rf:stack:listOutputs

-

POST /v1/{project_id}/stacks/{stack_name}/execution-plans

rf:stack:createExecutionPlan

kms:cmk:decryptDataKey

GET /v1/{project_id}/stacks/{stack_name}/execution-plans/{execution_plan_name}/metadata

rf:stack:getExecutionPlanMetadata

-

GET /v1/{project_id}/stacks/{stack_name}/execution-plans/{execution_plan_name}

rf:stack:getExecutionPlan

-

POST /v1/{project_id}/stacks/{stack_name}/execution-plans/{execution_plan_name}

rf:stack:applyExecutionPlan

-

GET /v1/{project_id}/stacks/{stack_name}/execution-plans

rf:stack:listExecutionPlans

-

DELETE /v1/{project_id}/stacks/{stack_name}/execution-plans/{execution_plan_name}

rf:stack:deleteExecutionPlan

-

POST /v1/{project_id}/stacks/{stack_name}/rollbacks

rf:stack:continueRollback

-

POST /v1/{project_id}/stacks/{stack_name}/continuations

rf:stack:continueDeploy

-

GET /v1/{project_id}/stacks/{stack_name}/execution-plans/{execution_plan_name}/prices

rf:stack:estimateExecutionPlanPrice

bss:discount:view

PATCH /v1/{project_id}/stacks/{stack_name}

rf:stack:update

iam:agencies:pass

POST /v1/stack-sets

rf:stackSet:create

iam:agencies:pass

GET /v1/stack-sets

rf:stackSet:list

-

GET /v1/stack-sets/{stack_set_name}/templates

rf:stackSet:showTemplate

-

GET /v1/stack-sets/{stack_set_name}/metadata

rf:stackSet:showMetadata

-

POST /v1/stack-sets/{stack_set_name}/deployments

rf:stackSet:deploy

-

DELETE /v1/stack-sets/{stack_set_name}

rf:stackSet:delete

-

PATCH /v1/stack-sets/{stack_set_name}

rf:stackSet:update

iam:agencies:pass

GET /v1/stack-sets/{stack_set_name}/stack-instances

rf:stackSet:listStackInstances

-

GET /v1/stack-sets/{stack_set_name}/operations/{stack_set_operation_id}/metadata

rf:stackSet:showOperationMetadata

-

GET /v1/stack-sets/{stack_set_name}/operations

rf:stackSet:listOperations

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for IAC.

Table 3 Resource types supported by IAC

Resource Type

URN

privateTemplate

rf:<region>:<account-id>:privateTemplate:<template-name>

stackSet

rf:<region>:<account-id>:stackSet:<stack-set-name>/<stack-set-id>

stack

rf:<region>:<account-id>:stack:<stack-name>

Conditions

IAC does not support service-specific condition keys in identity policies.It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Management & Governance