rekognition

rekognitionAka

aws-rekognition

A read-only policy generated by Turbot that lists the APIs that
should be added to the turbot-managed (hard) boundary policy,
thereby enabling them to be assigned to users and roles.
This value will change depending on the value of the value of the
`AWS &gt; Rekognition &gt; Permissions &gt; Lockdown &gt; API Boundary` policy


AWS > Turbot > Permissions > Compiled > API Boundary

AWS > Account

AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-rekognition

A calculated policy that Turbot uses to create a compiled list of ALL permissions for AWS Rekognition
that is used as input to the control that manages the IAM stack.


AWS > Turbot > Permissions > Compiled > Service Permissions

AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-rekognition

A calculated policy that Turbot uses to create a compiled list of ALL permissions for AWS Rekognition
that is used as input to the stack that manages the Turbot IAM permissions objects.


AWS > Turbot > Permissions > Compiled > Levels

AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-rekognition

Configure whether the AWS Rekognition API is enabled.

**Note:** Disabling the service disables the API for ALL users and roles, and Turbot will have no access to the API.


AWS > Rekognition

AWS > Rekognition > API Enabled

A list of AWS regions in which AWS Rekognition resources are approved for use.

The expected format is an array of regions names. You may use the &#39;*&#39; and
&#39;?&#39; wildcard characters.

This policy is the default value for all AWS Rekognition resources&#39; Approved &gt; Regions policies.


AWS > Rekognition > Approved Regions [Default]

Configure whether the AWS Rekognition service is enabled.
This will only affect Turbot managed User Roles and will allow the Turbot managed user to access AWS Rekognition service.
  - `Enabled` policy allows Turbot managed users to perform all the actions for the service
  - `Enabled: Metadata Only` policy allows Turbot managed users to perform only the metadata level actions for the service (like `describe*`, `list*`)

**Note:**
  - `Disabled` policy disables the service but does NOT disable the API for Turbot or SuperUsers
  - All the resource data stored in the Turbot CMDB is considered to be metadata
  - For more information related to permissions and grant levels, please check the [documentation](https://turbot.com/v5/docs/concepts/iam/permissions)


AWS > Rekognition > Enabled

AWS > Rekognition > Permissions > Levels

AWS > Rekognition > Permissions > Lockdown

Configure whether permissions policies are in effect for AWS Rekognition.

This setting does not affect account level permissions (AWS/Admin, AWS/Owner, etc)

**Note:** The behavior of this policy depends on the value of AWS &gt; Permissions.


AWS > Rekognition > Permissions

AWS > Rekognition > Permissions > Levels > Modifiers

Define the permissions levels that can be used to grant access to an AWS account.
Permissions levels defined will appear in the UI to assign access to Turbot users.
This policy provides a default for Permissions &gt; Levels in each service,
however you can explicitly override the setting for each service if desired


A map of AWS API to Turbot Permission Level used to customize Turbot&#39;s standard permissions.
You can add, remove or redefine the mapping of AWS API operations to Turbot permissions levels here.

**Note:** Modifiers are cumulative - if you add a permission to the Metadata level, it is also added to ReadOnly, Operator and Admin.
Modifier policies set here apply ONLY to the AWS level

```
example:
  - &quot;glacier:createvault&quot;: admin
  - &quot;glacier:ListVaults&quot;: metadata
  - &quot;s3:DeleteBucket&quot;: none
```


AWS > Rekognition > Permissions > Lockdown > API Boundary

Configure whether the AWS rekognition API is enabled for all users and roles in turbot-managed boundary policies.

**Note:** Disabling the service disables the API for ALL users and roles, and Turbot will have no access to the API.


A list of AWS regions in which AWS Rekognition resources are supported for use.

The expected format is an array of regions names. You may use the &#39;*&#39; and
&#39;?&#39; wildcard characters.

This policy is the default value for all AWS Rekognition resources&#39; Regions policies.


AWS > Rekognition > Regions

AWS > Region

AWS/Rekognition/Metadata

AWS/Rekognition/Operator

aws-acm

aws-amplify

aws-apigateway

aws-appconfig

aws-appfabric

aws-appflow

aws-appmesh

aws-appstream

aws-appsync

aws-artifact

aws-athena

aws-auditmanager

aws-backup

aws-batch

aws-bedrock

aws-billing

aws-braket

aws-chatbot

aws-chime

aws-cisv1

aws-cisv1-4

aws-cisv2-0

aws-cisv3-0

aws-cleanrooms

aws-cloud9

aws-clouddirectory

aws-cloudformation

aws-cloudfront

aws-cloudhsm

aws-cloudmap

aws-cloudsearch

aws-cloudshell

aws-cloudtrail

aws-cloudwatch

aws-codebuild

aws-codecommit

aws-codedeploy

aws-codepipeline

aws-codestar

aws-codewhisperer

aws-cognito

aws-comprehend

aws-computeoptimizer

aws-config

aws-connect

aws-datapipeline

aws-datasync

aws-dax

aws-devicefarm

aws-directconnect

aws-directoryservice

aws-dms

aws-docdb

aws-dynamodb

aws-ec2

aws-ec2imagebuilder

aws-ecr

aws-ecs

aws-efs

aws-eks

aws-elasticache

aws-elasticbeanstalk

aws-elasticinference

aws-elasticsearch

aws-elastictranscoder

aws-emr

aws-eventbridgepipes

aws-eventbridgescheduler

aws-events

aws-fms

aws-fsx

aws-gamelift

aws-glacier

aws-globalaccelerator

aws-glue

aws-gluedatabrew

aws-greengrass

aws-guardduty

aws-health

aws-hipaa

aws-iam

aws-inspector

aws-iot

aws-iot1click

aws-iotanalytics

aws-iotevents

aws-iotsitewise

aws-iotthingsgraph

aws-kendra

aws-kinesis

aws-kms

aws-lakeformation

aws-lambda

aws-lex

aws-lightsail

aws-location

aws-logs

aws-machinelearning

aws-macie

Mod: aws-rekognition

Recommended Version

Resource Types

IAM Roles

Policies