Policy types for @turbot/aws-amplify
- AWS > Amplify > API Enabled
- AWS > Amplify > App > Active
- AWS > Amplify > App > Active > Age
- AWS > Amplify > App > Active > Last Modified
- AWS > Amplify > App > Approved
- AWS > Amplify > App > Approved > Custom
- AWS > Amplify > App > Approved > Regions
- AWS > Amplify > App > Approved > Usage
- AWS > Amplify > App > CMDB
- AWS > Amplify > App > Regions
- AWS > Amplify > App > Tags
- AWS > Amplify > App > Tags > Template
- AWS > Amplify > App > Usage
- AWS > Amplify > App > Usage > Limit
- AWS > Amplify > Approved Regions [Default]
- AWS > Amplify > Enabled
- AWS > Amplify > Permissions
- AWS > Amplify > Permissions > Levels
- AWS > Amplify > Permissions > Levels > Modifiers
- AWS > Amplify > Permissions > Lockdown
- AWS > Amplify > Permissions > Lockdown > API Boundary
- AWS > Amplify > Regions
- AWS > Amplify > Tags Template [Default]
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-amplify
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-amplify
AWS > Amplify > API Enabled
Configure whether the AWS Amplify API is enabled.
Note: Disabling the service disables the API for ALL users and roles, and Guardrails will have no access to the API.
tmod:@turbot/aws-amplify#/policy/types/amplifyApiEnabled
[ "Enabled", "Disabled", "Enabled if AWS > Amplify > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Amplify > Enabled" ], "default": "Enabled"}
AWS > Amplify > App > Active
Determine the action to take when an AWS Amplify app, based on the AWS > Amplify > App > Active > *
policies.
The control determines whether the resource is in active use, and if not,
has the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Amplify > App > Active > *
), raises an alarm, and takes the defined enforcement
action. Each Active sub-policy can calculate a status of active, inactive
or skipped. Generally, if the resource appears to be Active for any reason
it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved for any reason it will be considered
Unapproved.
See Active for more information.
tmod:@turbot/aws-amplify#/policy/types/appActive
[ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning"]
{ "type": "string", "enum": [ "Skip", "Check: Active", "Enforce: Delete inactive with 1 day warning", "Enforce: Delete inactive with 3 days warning", "Enforce: Delete inactive with 7 days warning", "Enforce: Delete inactive with 14 days warning", "Enforce: Delete inactive with 30 days warning", "Enforce: Delete inactive with 60 days warning", "Enforce: Delete inactive with 90 days warning", "Enforce: Delete inactive with 180 days warning", "Enforce: Delete inactive with 365 days warning" ], "example": [ "Check: Active" ], "default": "Skip"}
AWS > Amplify > App > Active > Age
The age after which the AWS Amplify app
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.
The Active
control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Amplify > App > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/aws-amplify#/policy/types/appActiveAge
[ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days"]
{ "type": "string", "enum": [ "Skip", "Force inactive if age > 1 day", "Force inactive if age > 3 days", "Force inactive if age > 7 days", "Force inactive if age > 14 days", "Force inactive if age > 30 days", "Force inactive if age > 60 days", "Force inactive if age > 90 days", "Force inactive if age > 180 days", "Force inactive if age > 365 days" ], "example": [ "Force inactive if age > 90 days" ], "default": "Skip"}
AWS > Amplify > App > Active > Last Modified
The number of days since the AWS Amplify app
was last modified before it is considered inactive.
The Active
control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.
The Active control checks the status of all defined Active policies for the
resource (AWS > Amplify > App > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/aws-amplify#/policy/types/appActiveLastModified
[ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days"]
{ "type": "string", "enum": [ "Skip", "Active if last modified <= 1 day", "Active if last modified <= 3 days", "Active if last modified <= 7 days", "Active if last modified <= 14 days", "Active if last modified <= 30 days", "Active if last modified <= 60 days", "Active if last modified <= 90 days", "Active if last modified <= 180 days", "Active if last modified <= 365 days", "Force active if last modified <= 1 day", "Force active if last modified <= 3 days", "Force active if last modified <= 7 days", "Force active if last modified <= 14 days", "Force active if last modified <= 30 days", "Force active if last modified <= 60 days", "Force active if last modified <= 90 days", "Force active if last modified <= 180 days", "Force active if last modified <= 365 days" ], "example": [ "Active if last modified <= 90 days" ], "default": "Skip"}
AWS > Amplify > App > Approved
Determine the action to take when an AWS Amplify app is not approved based on AWS > Amplify > App > Approved > *
policies.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/aws-amplify#/policy/types/appApproved
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
AWS > Amplify > App > Approved > Custom
Determine whether the AWS Amplify app is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Amplify app is not approved, it will be subject to the action specified in the AWS > Amplify > App > Approved
policy.
See Approved for more information.
Note: The policy value must be a string with a value of Approved
, Not approved
or Skip
, or in the form of YAML objects. The object(s) must contain the key result
with its value as Approved
or Not approved
. A custom title and message can also be added using the keys title
and message
respectively.
tmod:@turbot/aws-amplify#/policy/types/appApprovedCustom
{ "example": [ "Approved", "Not approved", "Skip", { "result": "Approved" }, { "title": "string", "result": "Not approved" }, { "title": "string", "result": "Approved", "message": "string" }, [ { "title": "string", "result": "Approved", "message": "string" }, { "title": "string", "result": "Not approved", "message": "string" } ] ], "anyOf": [ { "type": "array", "items": { "type": "object", "properties": { "title": { "type": "string", "pattern": "^[\\W\\w]{1,32}$" }, "message": { "type": "string", "pattern": "^[\\W\\w]{1,128}$" }, "result": { "type": "string", "pattern": "^(Approved|Not approved|Skip)$" } }, "required": [ "result" ], "additionalProperties": false } }, { "type": "object", "properties": { "title": { "type": "string", "pattern": "^[\\W\\w]{1,32}$" }, "message": { "type": "string", "pattern": "^[\\W\\w]{1,128}$" }, "result": { "type": "string", "pattern": "^(Approved|Not approved|Skip)$" } }, "required": [ "result" ], "additionalProperties": false }, { "type": "string", "pattern": "^(Approved|Not approved|Skip)$" } ], "default": "Skip"}
AWS > Amplify > App > Approved > Regions
A list of AWS regions in which AWS Amplify apps are approved for use.
The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.
This policy will be evaluated by the Approved control. If an AWS Amplify app is created in a region that is not in the approved list, it will be subject to the action specified in the AWS > Amplify > App > Approved
policy.
See Approved for more information.
tmod:@turbot/aws-amplify#/policy/types/appApprovedRegions
"{\n regions: policy(uri: \"tmod:@turbot/aws-amplify#/policy/types/amplifyApprovedRegionsDefault\")\n}\n"
"{% if $.regions | length == 0 %} [] {% endif %}{% for item in $.regions %}- '{{ item }}'\n{% endfor %}"
AWS > Amplify > App > Approved > Usage
Determine whether the AWS Amplify app is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Amplify app is not approved, it will be subject to the action specified in the AWS > Amplify > App > Approved
policy.
See Approved for more information.
tmod:@turbot/aws-amplify#/policy/types/appApprovedUsage
[ "Not approved", "Approved", "Approved if AWS > Amplify > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if AWS > Amplify > Enabled" ], "example": [ "Not approved" ], "default": "Approved if AWS > Amplify > Enabled"}
AWS > Amplify > App > CMDB
Configure whether to record and synchronize details for the AWS Amplify app into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".
If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.
To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".
CMDB controls also use the Regions policy associated with the resource. If region is not in AWS > Amplify > App > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/aws-amplify#/policy/types/appCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Amplify > App > Regions
A list of AWS regions in which AWS Amplify apps are supported for use.
Any apps in a region not listed here will not be recorded in CMDB.
The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.
tmod:@turbot/aws-amplify#/policy/types/appRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/aws-amplify#/policy/types/amplifyRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Amplify > App > Tags
Determine the action to take when an AWS Amplify app tags are not updated based on the AWS > Amplify > App > Tags > *
policies.
The control ensure AWS Amplify app tags include tags defined in AWS > Amplify > App > Tags > Template
.
Tags not defined in App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/aws-amplify#/policy/types/appTags
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
AWS > Amplify > App > Tags > Template
The template is used to generate the keys and values for AWS Amplify app.
Tags not defined in App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/aws-amplify#/policy/types/appTagsTemplate
[ "{\n account {\n turbot {\n id\n }\n }\n}\n", "{\n defaultTags: policyValue(uri:\"tmod:@turbot/aws-amplify#/policy/types/amplifyTagsTemplate\" resourceId: \"{{ $.account.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
AWS > Amplify > App > Usage
Configure the number of AWS Amplify apps that can be used for this region and the current consumption against the limit.
You can configure the behavior of the control with this AWS > Amplify > App > Usage
policy.
tmod:@turbot/aws-amplify#/policy/types/appUsage
[ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit"]
{ "type": "string", "enum": [ "Skip", "Check: Usage <= 85% of Limit", "Check: Usage <= 100% of Limit" ], "example": [ "Check: Usage <= 85% of Limit" ], "default": "Skip"}
AWS > Amplify > App > Usage > Limit
Maximum number of items that can be created for this region.
tmod:@turbot/aws-amplify#/policy/types/appUsageLimit
{ "type": "integer", "minimum": 0, "default": 100}
AWS > Amplify > Approved Regions [Default]
A list of AWS regions in which AWS Amplify resources are approved for use.
The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.
This policy is the default value for all AWS Amplify resources' Approved > Regions policies.
tmod:@turbot/aws-amplify#/policy/types/amplifyApprovedRegionsDefault
"{\n regions: policyValue(uri:\"tmod:@turbot/aws#/policy/types/approvedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
AWS > Amplify > Enabled
Configure whether the AWS Amplify service is enabled.
This will only affect Guardrails managed User Roles and will allow the Guardrails managed user to access AWS Amplify service.
- Enabled
policy allows Guardrails managed users to perform all the actions for the service
- Enabled: Metadata Only
policy allows Guardrails 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 Guardrails or SuperUsers
- All the resource data stored in the Guardrails CMDB is considered to be metadata
- For more information related to permissions and grant levels, please check the documentation
tmod:@turbot/aws-amplify#/policy/types/amplifyEnabled
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
AWS > Amplify > Permissions
Configure whether permissions policies are in effect for AWS Amplify.
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 > Permissions.
tmod:@turbot/aws-amplify#/policy/types/amplifyPermissions
[ "Enabled", "Disabled", "Enabled if AWS > Amplify > Enabled & AWS > Amplify > API Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Amplify > Enabled & AWS > Amplify > API Enabled" ], "example": [ "Enabled" ], "default": "Enabled if AWS > Amplify > Enabled & AWS > Amplify > API Enabled"}
AWS > Amplify > Permissions > Levels
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 Guardrails users.
This policy provides a default for Permissions > Levels in each service,
however you can explicitly override the setting for each service if desired
tmod:@turbot/aws-amplify#/policy/types/amplifyPermissionsLevels
[ "{\n item: account {\n turbot{\n id\n }\n }\n}\n", "{\n availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyTypeId:'tmod:@turbot/aws-iam#/policy/types/permissionsLevelsDefault'\") {\n items {\n value\n }\n }\n}\n"]
"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"
{ "type": "array", "items": { "type": "string", "enum": [ "Metadata", "ReadOnly", "Operator", "Admin", "Owner" ] }}
AWS > Amplify > Permissions > Levels > Modifiers
A map of AWS API to Guardrails Permission Level used to customize Guardrails' standard permissions.
You can add, remove or redefine the mapping of AWS API operations to Guardrails 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<br />example:<br /> - "glacier:createvault": admin<br /> - "glacier:ListVaults": metadata<br /> - "s3:DeleteBucket": none<br />
tmod:@turbot/aws-amplify#/policy/types/amplifyPermissionsLevelsModifiers
AWS > Amplify > Permissions > Lockdown
tmod:@turbot/aws-amplify#/policy/types/amplifyPermissionsLockdown
AWS > Amplify > Permissions > Lockdown > API Boundary
Configure whether the AWS amplify API is enabled for all users and roles in guardrails-managed boundary policies.
Note: Disabling the service disables the API for ALL users and roles, and Guardrails will have no access to the API.
tmod:@turbot/aws-amplify#/policy/types/amplifyPermissionsLockdownApiBoundary
[ "Enabled if AWS > Amplify > API Enabled"]
{ "type": "string", "enum": [ "Enabled if AWS > Amplify > API Enabled" ], "example": [ "Enabled if AWS > Amplify > API Enabled" ], "default": "Enabled if AWS > Amplify > API Enabled"}
AWS > Amplify > Regions
A list of AWS regions in which AWS Amplify resources are supported for use.
The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.
This policy is the default value for all AWS Amplify resources' Regions policies.
tmod:@turbot/aws-amplify#/policy/types/amplifyRegionsDefault
{ "allOf": [ { "$ref": "aws#/definitions/regionNameMatcherList" }, { "default": [ "ap-northeast-1", "ap-northeast-2", "ap-south-1", "ap-southeast-1", "ap-southeast-2", "eu-central-1", "eu-west-1", "eu-west-2", "us-east-1", "us-east-2", "us-west-2" ] } ]}
AWS > Amplify > Tags Template [Default]
A template used to generate the keys and values for AWS Amplify resources.
By default, all Amplify resource Tags > Template policies will use this value.
tmod:@turbot/aws-amplify#/policy/types/amplifyTagsTemplate
"{\n defaultTags: policyValue(uri:\"tmod:@turbot/aws#/policy/types/defaultTagsTemplate\") {\n value\n }\n}\n"
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-amplify
AWS Amplify CloudWatch Events event sources for the Guardrails Event Handlers.
tmod:@turbot/aws-amplify#/policy/types/amplifyEventSources
{ "type": "array", "items": { "type": "string" }, "default": [ "aws.amplify" ]}
AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-amplify
A read-only policy generated by Guardrails that lists the APIs that
should be added to the guardrails-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 theAWS > Amplify > Permissions > Lockdown > API Boundary
policy
tmod:@turbot/aws-amplify#/policy/types/awsCompiledApiBoundary
{ "type": "array"}
AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-amplify
A calculated policy that Guardrails uses to create a compiled list of ALL permissions for AWS Amplify
that is used as input to the stack that manages the Guardrails IAM permissions objects.
tmod:@turbot/aws-amplify#/policy/types/awsLevelsCompiled
AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-amplify
A calculated policy that Guardrails uses to create a compiled list of ALL permissions for AWS Amplify
that is used as input to the control that manages the IAM stack.
tmod:@turbot/aws-amplify#/policy/types/awsCompiledServicePermissions