appflow:UseConnectorProfile

Literal appearances in AWS managed IAM policies. Statements that use wildcards (for example s3:*) are not counted here. This is not an IAM authorization simulation.

Policies (any)

2

Allow (Action)

2

Deny (Action)

0

NotAction

0

571 policies include at least one wildcard action string (any service). Index regenerated on every deploy.

First seen

From archive history

This action

2022-09-30 in AppIntegrationsServiceLinkedRolePolicy

Service prefix appflow

2020-06-03 in AmazonAppFlowReadOnlyAccess

Earliest appearance in any AWS managed policy tracked here, not an official AWS launch date. Matched case-insensitively, as IAM does.

Action reference

SAR-style (unofficial)

Service: Amazon AppFlow

Access level

Write

Description

Grants permission to use a connector profile while creating a flow in Amazon AppFlow

Resource types

  • connectorprofile*

Allow (Action)

Deny (Action)

None

NotAction

None

Thanks to Ian McKay for iam-dataset (MIT), structured data derived from the AWS Service Authorization Reference. Not maintained by AWS and not guaranteed current. IAMTrail's managed policy archive is separate.

Definitions bundle regenerated on every deploy