For advanced users, Amazon Web Services supports the Boto Python scripting interface for finer-grained control of instances in your Amazon virtual private clouds. You use the Boto Python interface on a separate computer as an AWS API client. Knowledge of Python and Bash scripting and use of Boto are required for effective use of API clients with the AWS API Proxy.

...

Setting Up an API Client

...

You begin the Amazon API client configuration by defining the DNS CNAME aliases for the Infoblox vNIOS for AWS instance that will act as the AWS API Proxy. (For this section, we assume use of a vNIOS instance in the VPC as the AWS API Proxy, and a Linux system as the API client.) You define the aliases against the IP address of the vNIOS instance for every region in which the Infoblox vNIOS for AWS instance is intended to operate.
Example:

...

In the JSON file, API requests refer to the standard Amazon service endpoint values in each record (“us-east-1”). You also enter these standard values as part of assignments to the AWS API Proxy configuration (for information, see Assigning the AWS Service Endpoints to the AWS API Proxy). These definitions assign the AWS API Proxy, with each of its DNS host names, to the endpoints. (These host names are defined on the appliance, as described in Setting the DNS Name Server for the Amazon VPC .)

The following example illustrates how to connect to the AWS EC2 endpoint using the aforementioned Boto setup:

vpc_conn = boto.vpc.connect_to_region("us-west-1", port=8787)

Continue your setup in the following section, Assigning the AWS Service Endpoints to the AWS API Proxy.

...

...

Assigning the AWS Service Endpoints to the AWS API Proxy

You use the values in the endpoints.json file to assign the EC2 service endpoint mappings to the vNIOS host, changing the values from the standard Amazon ones. You add these values to your vNIOS API Proxy configuration. For example, consider the JSON entry:

"us-west-1": "us-west-blox-gw1.corp100.com",

Instead of using the standard ec2.us-west-1.amazonaws.com value as the endpoint, you can use a DNS alias you configured for the NIOS appliance or Infoblox vNIOS for AWS instance (us-west-blox-gw1.corp100.com), as a substitute for the service endpoint of the particular Amazon region. You change these values for all EC2 service endpoints that you plan to use for Infoblox vNIOS for AWS. This enforces use of the AWS API Proxy in place of the service endpoints.
To perform the setup for the NIOS or vNIOS Cloud Platform Appliance that will operate as the AWS API Proxy, do the following:

1. From the Grid tab, select the

   GridManager

   GridManager tab, and then click the Cloud-API service.

2. Select the appliance that will run the API Proxy (the member must have the Cloud Network Appliance license) by selecting the Services tab -> cloud_member check box, and then click Edit.

3. In the General tab ->

   AdministratorsallowedtomakeWAPIrequestsontheGridMaster

   AdministratorsallowedtomakeWAPIrequestsontheGridMaster section, select

   Setofadministrators

   Setofadministrators and then click Add -> Local. You will see the complete list of configured Cloud user accounts. You choose the accounts from which API requests are allowed. In a default configuration, only the cloud/local account appears.

4. Click the

   APIProxy

   APIProxy tab ->

   AmazonWebServices

   AmazonWebServices tab, and then click the

   EnableService

   EnableService check box. Ensure that it is enabled.

5. For the Port, enter the value for the TCP port (typically 8787).

6. For the

   APIEndpointMapping

   APIEndpointMapping, click Add.

   • APIProxyFQDN

     APIProxyFQDN: For the Infoblox API Proxy this value consists of the DNS host name for the Infoblox vNIOS for AWS appliance. Along with the JSON configuration described above, these values enforce the placement of the Cloud Platform appliance as the AWS API Proxy, which receives all AWS API calls issued by API clients.

   • AWSEndpointFQDN

     AWSEndpointFQDN: Enter the Amazon regional endpoint to which the API Proxy will send its processed API requests. Example: ec2.us-west-1.amazonaws.com.

7. Save the configuration.

...