Policy types for @turbot/aws-organizations
- AWS > Organizations > API Enabled
- AWS > Organizations > Enabled
- AWS > Organizations > Organization > CMDB
- AWS > Organizations > Organization Root > Active
- AWS > Organizations > Organization Root > Active > Age
- AWS > Organizations > Organization Root > Active > Last Modified
- AWS > Organizations > Organization Root > Approved
- AWS > Organizations > Organization Root > Approved > Custom
- AWS > Organizations > Organization Root > Approved > Usage
- AWS > Organizations > Organization Root > CMDB
- AWS > Organizations > Organizational Account > Active
- AWS > Organizations > Organizational Account > Active > Age
- AWS > Organizations > Organizational Account > Active > Last Modified
- AWS > Organizations > Organizational Account > Approved
- AWS > Organizations > Organizational Account > Approved > Custom
- AWS > Organizations > Organizational Account > Approved > Usage
- AWS > Organizations > Organizational Account > CMDB
- AWS > Organizations > Organizational Unit > CMDB
- AWS > Organizations > Permissions
- AWS > Organizations > Permissions > Levels
- AWS > Organizations > Permissions > Levels > Modifiers
- AWS > Organizations > Permissions > Lockdown
- AWS > Organizations > Permissions > Lockdown > API Boundary
- AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-organizations
- AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-organizations
- AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-organizations
- AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-organizations
AWS > Organizations > API Enabled
Configure whether the AWS Organizations 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-organizations#/policy/types/organizationsApiEnabled
[ "Enabled", "Disabled", "Enabled if AWS > Organizations > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Organizations > Enabled" ], "default": "Enabled"}
AWS > Organizations > Enabled
Configure whether the AWS Organizations service is enabled.
This will only affect Guardrails managed User Roles and will allow the Guardrails managed user to access AWS Organizations 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-organizations#/policy/types/organizationsEnabled
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
AWS > Organizations > Organization > CMDB
Configure whether to record and synchronize details for the AWS Organizations organization 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".
tmod:@turbot/aws-organizations#/policy/types/organizationCmdb
"{\n account {\n Id: get(path:\"Id\")\n MasterAccountId: get(path: \"Organization.MasterAccountId\")\n }\n}\n"
"{% if ($.account.Id is not null) and ($.account.Id === $.account.MasterAccountId) %} 'Enforce: Enabled' {%- else %} 'Skip' {% endif %}"
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ]}
AWS > Organizations > Organization Root > Active
Determine the action to take when an AWS Organizations organization root, based on the AWS > Organizations > Organization Root > 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 > Organizations > Organization Root > 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-organizations#/policy/types/organizationRootActive
[ "Skip", "Check: Active"]
{ "type": "string", "enum": [ "Skip", "Check: Active" ], "example": [ "Check: Active" ], "default": "Skip"}
AWS > Organizations > Organization Root > Active > Age
The age after which the AWS Organizations organization root
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 > Organizations > Organization Root > 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-organizations#/policy/types/organizationRootActiveAge
[ "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 > Organizations > Organization Root > Active > Last Modified
The number of days since the AWS Organizations organization root
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 > Organizations > Organization Root > 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-organizations#/policy/types/organizationRootActiveLastModified
[ "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 > Organizations > Organization Root > Approved
Determine the action to take when an AWS Organizations organization root is not approved based on AWS > Organizations > Organization Root > 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.
See Approved for more information.
tmod:@turbot/aws-organizations#/policy/types/organizationRootApproved
[ "Skip", "Check: Approved"]
{ "type": "string", "enum": [ "Skip", "Check: Approved" ], "example": [ "Check: Approved" ], "default": "Skip"}
AWS > Organizations > Organization Root > Approved > Custom
Determine whether the AWS Organizations organization root is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Organizations organization root is not approved, it will be subject to the action specified in the AWS > Organizations > Organization Root > 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-organizations#/policy/types/organizationRootApprovedCustom
{ "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 > Organizations > Organization Root > Approved > Usage
Determine whether the AWS Organizations organization root is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Organizations organization root is not approved, it will be subject to the action specified in the AWS > Organizations > Organization Root > Approved
policy.
See Approved for more information.
tmod:@turbot/aws-organizations#/policy/types/organizationRootApprovedUsage
[ "Not approved", "Approved", "Approved if AWS > Organizations > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if AWS > Organizations > Enabled" ], "example": [ "Not approved" ], "default": "Approved if AWS > Organizations > Enabled"}
AWS > Organizations > Organization Root > CMDB
Configure whether to record and synchronize details for the AWS Organizations organization root 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".
tmod:@turbot/aws-organizations#/policy/types/organizationRootCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Organizations > Organizational Account > Active
Determine the action to take when an AWS Organizations organizational account, based on the AWS > Organizations > Organizational Account > 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 > Organizations > Organizational Account > 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-organizations#/policy/types/organizationalAccountActive
[ "Skip", "Check: Active"]
{ "type": "string", "enum": [ "Skip", "Check: Active" ], "example": [ "Check: Active" ], "default": "Skip"}
AWS > Organizations > Organizational Account > Active > Age
The age after which the AWS Organizations organizational account
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 > Organizations > Organizational Account > 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-organizations#/policy/types/organizationalAccountActiveAge
[ "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 > Organizations > Organizational Account > Active > Last Modified
The number of days since the AWS Organizations organizational account
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 > Organizations > Organizational Account > 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-organizations#/policy/types/organizationalAccountActiveLastModified
[ "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 > Organizations > Organizational Account > Approved
Determine the action to take when an AWS Organizations organizational account is not approved based on AWS > Organizations > Organizational Account > 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.
See Approved for more information.
tmod:@turbot/aws-organizations#/policy/types/organizationalAccountApproved
[ "Skip", "Check: Approved"]
{ "type": "string", "enum": [ "Skip", "Check: Approved" ], "example": [ "Check: Approved" ], "default": "Skip"}
AWS > Organizations > Organizational Account > Approved > Custom
Determine whether the AWS Organizations organizational account is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Organizations organizational account is not approved, it will be subject to the action specified in the AWS > Organizations > Organizational Account > 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-organizations#/policy/types/organizationalAccountApprovedCustom
{ "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 > Organizations > Organizational Account > Approved > Usage
Determine whether the AWS Organizations organizational account is allowed to exist.
This policy will be evaluated by the Approved control. If an AWS Organizations organizational account is not approved, it will be subject to the action specified in the AWS > Organizations > Organizational Account > Approved
policy.
See Approved for more information.
tmod:@turbot/aws-organizations#/policy/types/organizationalAccountApprovedUsage
[ "Not approved", "Approved", "Approved if AWS > Organizations > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if AWS > Organizations > Enabled" ], "example": [ "Not approved" ], "default": "Approved if AWS > Organizations > Enabled"}
AWS > Organizations > Organizational Account > CMDB
Configure whether to record and synchronize details for the AWS Organizations organizational account 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".
tmod:@turbot/aws-organizations#/policy/types/organizationalAccountCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Organizations > Organizational Unit > CMDB
Configure whether to record and synchronize details for the AWS Organizations organizational unit 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".
tmod:@turbot/aws-organizations#/policy/types/organizationalUnitCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
AWS > Organizations > Permissions
Configure whether permissions policies are in effect for AWS Organizations.
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-organizations#/policy/types/organizationsPermissions
[ "Enabled", "Disabled", "Enabled if AWS > Organizations > Enabled & AWS > Organizations > API Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if AWS > Organizations > Enabled & AWS > Organizations > API Enabled" ], "example": [ "Enabled" ], "default": "Enabled if AWS > Organizations > Enabled & AWS > Organizations > API Enabled"}
AWS > Organizations > 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-organizations#/policy/types/organizationsPermissionsLevels
[ "{\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 > Organizations > 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-organizations#/policy/types/organizationsPermissionsLevelsModifiers
AWS > Organizations > Permissions > Lockdown
tmod:@turbot/aws-organizations#/policy/types/organizationsPermissionsLockdown
AWS > Organizations > Permissions > Lockdown > API Boundary
Configure whether the AWS organizations 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-organizations#/policy/types/organizationsPermissionsLockdownApiBoundary
[ "Enabled if AWS > Organizations > API Enabled"]
{ "type": "string", "enum": [ "Enabled if AWS > Organizations > API Enabled" ], "example": [ "Enabled if AWS > Organizations > API Enabled" ], "default": "Enabled if AWS > Organizations > API Enabled"}
AWS > Turbot > Event Handlers > Events > Rules > Event Sources > @turbot/aws-organizations
AWS Organizations CloudWatch Events event sources for the Guardrails Event Handlers.
tmod:@turbot/aws-organizations#/policy/types/organizationsEventSources
"{\n account {\n Id: get(path: \"Id\")\n MasterAccountId: get(path: \"Organization.MasterAccountId\")\n }\n region {\n Name: get(path: \"Name\")\n }\n}\n"
"{% if ($.account.Id === $.account.MasterAccountId) and ($.region.Name === "us-east-1") %}"aws.organizations"{% else %}[]{% endif %}"
{ "type": "array", "items": { "type": "string" }}
AWS > Turbot > Permissions > Compiled > API Boundary > @turbot/aws-organizations
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 > Organizations > Permissions > Lockdown > API Boundary
policy
tmod:@turbot/aws-organizations#/policy/types/awsCompiledApiBoundary
{ "type": "array"}
AWS > Turbot > Permissions > Compiled > Levels > @turbot/aws-organizations
A calculated policy that Guardrails uses to create a compiled list of ALL permissions for AWS Organizations
that is used as input to the stack that manages the Guardrails IAM permissions objects.
tmod:@turbot/aws-organizations#/policy/types/awsLevelsCompiled
AWS > Turbot > Permissions > Compiled > Service Permissions > @turbot/aws-organizations
A calculated policy that Guardrails uses to create a compiled list of ALL permissions for AWS Organizations
that is used as input to the control that manages the IAM stack.
tmod:@turbot/aws-organizations#/policy/types/awsCompiledServicePermissions