disallowed_regions

AWS Disallowed Regions

What It Does

This policy finds all AWS EC2 instances within a user-specified list of disallowed regions or outside of a user-specified list of allowed regions. An incident is raised and a report emailed containing all of the non-compliant instances, with the option to stop or terminate offending instances.

Input Parameters

• Email Addresses - Email addresses of the recipients you wish to notify when new incidents are created.
• Account Number - The Account number for use with the AWS STS Cross Account Role. Leave blank when using AWS IAM Access key and secret. It only needs to be passed when the desired AWS account is different than the one associated with the Flexera One credential. more
• Exclusion Tags (Key:Value) - Cloud native tags to ignore resources that you don't want to produce recommendations for. Use Key:Value format for specific tag key/value pairs, and Key:* format to match any resource with a particular key, regardless of value. Examples: env:production, DO_NOT_DELETE:*
• Disallow/Allow Regions - Whether to allow or disallow the regions specified in the Disallow/Allow Regions List parameter. If set to "Allow", all EC2 instances outside of the listed regions will be considered out of compliance. If set to "Disallow", all EC2 instances within the listed regions will be considered out of compliance.
• Disallow/Allow Regions List - A list of regions to disallow or allow. Example: us-east-1
• Automatic Actions - When this value is set, this policy will automatically take the selected action(s).

Please note that the "Automatic Actions" parameter contains a list of action(s) that can be performed on the resources. When it is selected, the policy will automatically execute the corresponding action on the data that failed the checks, post incident generation. Please leave it blank for manual action. For example, if a user selects the "Terminate Instances" action while applying the policy, all the EC2 instances that didn't satisfy the policy condition will be deleted.

Policy Actions

• Sends an email notification.
• Stop reported instances after approval.
• Terminate reported instances after approval.

Prerequisites

This Policy Template uses Credentials for authenticating to datasources -- in order to apply this policy you must have a Credential registered in the system that is compatible with this policy. If there are no Credentials listed when you apply the policy, please contact your Flexera Org Admin and ask them to register a Credential that is compatible with this policy. The information below should be consulted when creating the credential(s).

• AWS Credential (provider=aws) which has the following permissions:

  • sts:GetCallerIdentity
  • ec2:DescribeRegions
  • ec2:DescribeInstances
  • ec2:StopInstances*
  • ec2:TerminateInstances*

  * Only required for taking action; the policy will still function in a read-only capacity without these permissions.

  Example IAM Permission Policy:

  {
      "Version": "2012-10-17",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "sts:GetCallerIdentity",
                  "ec2:DescribeRegions",
                  "ec2:DescribeInstances",
                  "ec2:StopInstances",
                  "ec2:TerminateInstances"
              ],
              "Resource": "*"
          }
      ]
  }

• Flexera Credential (provider=flexera) which has the following roles:

  • billing_center_viewer

The Provider-Specific Credentials page in the docs has detailed instructions for setting up Credentials for the most common providers.

Supported Clouds

• AWS

Cost

This policy template does not incur any cloud costs.