--- title: "Cloud API resolvers" slug: "cloud-api-resolvers-v7-0" description: "Learn how to configure cloud API resolvers for AWS, Azure, and GCP to automate entitlement actions and manage network resources effectively." tags: ["Cloud Resolvers", "Cloud API Resolver"] updated: 2026-06-05T12:36:00Z published: 2026-06-05T19:17:41Z canonical: "support.appgate.com/cloud-api-resolvers-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Cloud API resolvers Setting up a name resolver requires more configuration than setting up a DNS resolver. You must configure the AppGate ZTNA system to use the relevant cloud APIs. This configuration may include a hostname, access keys, or regions. Once you specify a name resolver, you can use resource names when defining entitlement actions. --- ## Purpose of cloud API resolvers When you use resource names, you can automate the configuration within entitlements. External systems populate network resources automatically. The AppGate ZTNA system makes API calls that return the instances currently active in a specific cloud environment. AppGate ZTNA populates firewall rules in near real time, eliminating the need to manually update entitlements each time a server instance is created or removed. --- ## Functionality of cloud API resolvers AppGate ZTNA supports AWS, Azure, GCP, Illumio, and vSphere. Once configured correctly, the Gateway will automatically adjust the allowed access rules in response to changing assets and IP addresses within any virtualized environment. The name resolver checks the results every 60 seconds to see if they have changed. If results have changed, AppGate ZTNA reruns the entitlement and access criteria scripts and updates the firewall rules. If a hostname is returned, the name resolver uses DNS to resolve it. AppGate ZTNA rate-limits and caches API calls to prevent host platforms from blocking queries under high loads. --- ## Configuring cloud API resolvers When you use resource names instead of IP addresses or hostnames, you often have to set up the AppGate ZTNA system in conjunction with the virtualization or cloud environment you are using to handle API calls from the AppGate ZTNA system. Name resolvers update every 60 seconds, so account for any API call rate limits that your cloud provider enforces. - Within the hosting environment, use tags and security groups to identify instances, network interfaces, or load balancers. - Set permissions in, or obtain credentials from, the hosting environment that grants the rights to use REST API calls to the user. - Set up the different types of cloud resolvers in [Sites > Cloud Resolvers](/v1/docs/configuring-sites-v7-0#cloud-resolvers) so they are ready to be used by the Gateways. - Define the *Host(s)* in [Entitlements > Access Rights > Actions](/v1/docs/configuring-entitlements-v7-0#access-rights) using the special resource name syntax - You can test your name resolver syntax in the Sites page. There is a **Test Name Resolver** action button for each Site. The test syntax for is identical to the syntax that you configure in your actions. > [!NOTE] > **NOTE** > > To minimize the number of cloud API calls made by the Gateways, cloud API calls now return all resources and filter them in the Gateway as required. It is important to set the right permissions for the resolver even if you are not using a specific type—for example, `"ec2:DescribeNetworkInterfaces"` for AWS and `"Microsoft.Network/networkInterfaces/read"` for Azure. Expand each section below to learn more about each type of resolver. To configure a resolver, see [Cloud Resolvers](/v1/docs/configuring-sites-v7-0#cloud-resolvers). ### Amazon Web Services (AWS) You can access the required APIs in AWS using an IAM user with the appropriate Secret Access Key, or you can configure the option to use IAM roles linked to the instances. By default, the IAM user must be within the same AWS account as the environment. You can work around this restriction by using the AWS assumed roles concept. Assumed roles allow the root IAM user to switch to a different user or role in different accounts or regions. For all IAM roles specified, you will need a new access policy for AppGate ZTNA or you can use an existing Amazon EC2 policy; a read-only policy for AppGate ZTNA works well. AppGate ZTNA reads tags or other entities from the entitlements and then accesses instance metadata to retrieve IP addresses. `'Describe*'` gives read-only access to any EC2 objects. Attach the AppGate ZTNA policy to the user or role. If using roles, this is included automatically in the profile when launching an AppGate ZTNA instance from the Marketplace. The following is the appropriate policy to set up: ```json {    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Action": [                "ec2:DescribeSecurityGroups",                "ec2:DescribeInstances",                "ec2:DescribeNetworkInterfaces",                "ec2:DescribeVpcs",                "elasticloadbalancing:DescribeLoadBalancers",                "elasticloadbalancing:DescribeTags"            ],            "Resource": "*"        }    ] } ``` If you are enabling RDS, EKS, or an API Gateway, use the following policy: ```json {    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Action": [                "ec2:DescribeSecurityGroups",                "ec2:DescribeInstances",                "ec2:DescribeNetworkInterfaces",                "ec2:DescribeVpcs",                "elasticloadbalancing:DescribeLoadBalancers",                "elasticloadbalancing:DescribeTags",                "apigateway:GET",                "eks:DescribeCluster",                "eks:ListClusters",                "rds:DescribeDBInstances"            ],            "Resource": "*"        }    ] } ``` For more information about this example, see [Example policies to control access the Amazon EC2 API](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ExamplePolicies_EC2.html#iam-example-read-only). You can now use the [special name resolver syntax](/v1/docs/resource-names-v7-0) to define hosts in your entitlements. ### AWS assume role configuration Consider a scenario where VMs in VPC A have network access to VMs in VPC B through VPC peer connectivity, and two different accounts—account A and account B—manage these VPCs. If you want the Gateway in account A to resolve VMs with a certain tag that reside in account B, this will not work by default. The IAM credentials for the Gateways in account A are not valid in account B. Assumed roles resolve this limitation: #### **In AWS account B** Create an IAM role and attach the appropriate policy to it, such as the example above. The existing `AmazonEC2ReadOnlyAccess` policy is also an option. See [Example policies to control access the Amazon EC2 API](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ExamplePolicies_EC2.html#iam-example-read-only) for more information. Edit the trust relationship of the created IAM role, adding the trusted entities that can assume this role and any associated conditions such as in the example below: ```json { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": {"AWS": "arn:aws:iam::ACCOUNT_A_ID:role/name_of_role"},//Role ARN in account A that will assume this role "Action": "sts:AssumeRole" "Condition": {"StringEquals": {"sts:ExternalId": "12345"}} //Read Note below }] } ``` > [!NOTE] > **NOTE** > > When a role policy includes an external ID, anyone who wants to assume the role must include the correct external ID in the AssumeRole API call. The external ID can be any secret identifier that is known by the two accounts. For more information, see: [IAM tutorial: Delegate access across AWS accounts using IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html). #### **In AWS account A** You may already have an IAM role with the `AmazonEC2ReadOnlyAccess` policy or similar attached to it. If not, create a new IAM role associated to your instance. Then create a new policy selecting *Service > STS, Action > Write (AssumeRole), Resources > Specific*. Under Role, specify the ARN from Account B. This will allow it to assume the role already defined in Account B and attach it to the role. The policy should look like the following: ```json { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": "sts:AssumeRole", "Resource": "arn:aws:iam::ACCOUNT_B_ID:role/name_of_role" //Role ARN in account B that will be assumed } ] } ``` Under *Permissions*, attach the new policy to your role. After you attach the policy, your Gateways have the permissions from the assumed role, allowing them to list and describe instances in account B. You can now configure it in the resolver. ### Azure In Azure, AppGate ZTNA supports two alternative methods to allow the resolver to make API calls: ### Managed identities With managed identities, Azure assigns an identity to the appliance and grants the required access rights based on that identity. You do not need to configure any IDs or secrets in the Site settings. See [What is managed identities for Azure resources?](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview) for more information about how to configure managed identities. When you create the appliance in Azure, select the *System assigned managed identity* checkbox in the Management tab: ![Checkbox for enabling system assigned managed identity in Azure's identity settings.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag55-azure_managed_identity.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A48Z&se=2026-11-21T22%3A39%3A48Z&sr=b&sp=r&sig=gn3YqpuJSx0yDux3OU0Y8bYG7QzgxTgpRLjXsgpv6HM%3D) For an existing appliance, the Identity panel also allows you to enable the system assigned managed identity: ![Azure managed identity settings with status toggle and object ID displayed for configuration.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag55-azure-identity.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A48Z&se=2026-11-21T22%3A39%3A48Z&sr=b&sp=r&sig=QSBqz6bm07zIzSF5%2BKROwSPUuTB%2B9a6R1GIkynoMu9U%3D) From here you can navigate to Azure role assignments where you select what role (along with any permissions) that the appliance will be granted. The generic read permission is sufficient, but you can reduce permissions further if required. The following list shows the absolute minimum permissions: `"Microsoft.Resources/subscriptions/read",` `"Microsoft.Network/networkSecurityGroups/read",` `"Microsoft.Network/virtualNetworks/read",` `"Microsoft.Network/networkInterfaces/read",` `"Microsoft.Network/loadBalancers/read",` `"Microsoft.Compute/virtualMachines/read",` `"Microsoft.Network/publicIPAddresses/read"` ### App registrations To allow AppGate ZTNA to use any web app or API, you must first register the app and then collect the required information for the Site settings: - In App registrations, click on *Certificates and secrets*, create a secret, and save the value for use later. - Note the Application ID and Tenant ID for use later. - In Resource Groups, in the Access control (IAM) blade where the AppGate ZTNA instances reside, you must add *permissions: Role – choose Reader* and select the app created earlier. See [Appgate SDP Name Resolving in Azure](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/Appgate-SDP%20for%20Azure-marketplace%20step-by-step(1).pdf?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A48Z&se=2026-11-21T22%3A39%3A48Z&sr=b&sp=r&sig=oL9YNNFbxvhEKfvA4WVi0L9zojdwMUFFDWUabHwxynE%3D). Now you can use the [special name resolver](/v1/docs/resource-names-v7-0) syntax to define hosts in your entitlements. ### Google Cloud Platform (GCP) Multiple GCP resolvers can be specified to resolve instances from projects with proper IAM role configuration. For GCP name resolvers to work, the project needs `compute.googleapis.com` enabled. Gateways need *Read Only* **Cloud Platform Cloud API access scopes** enabled. ![Cloud Platform access is enabled among various API access scopes listed.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag63-google_api.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A39%3A48Z&se=2026-11-21T22%3A39%3A48Z&sr=b&sp=r&sig=Ei5v%2BOrqP4YSqFBL3HlPy1fB3PXZt99TI2Eg6%2BpuFf4%3D) ## Configuring IAM roles Create a service account for the project (Project A) where the Gateway is going to be deployed, and copy the email-id of the service account. Now go to other project (Project B). - Go to the roles page. - Create a new role with Permissions > `compute.instances.list`, `compute.forwardingRules.list`, and `resourcemanager.projects.get` - Give it an appropriate name, such as `ComputeInstancesReadRole` - Go to the IAM & admin > IAM page. - Select the **Add** button. - In the ***New members*** field, paste the email-id of the service account. It should look like a strange email address. - Assign the custom role (`ComputeInstancesReadRole`) that you just created. Now you can use the [special name resolver](/v1/docs/resource-names-v7-0) syntax to define hosts in your entitlements.