How to Identify AWS Elements Provisioned by Agora¶

The identifiers of the AWS elements provisioned by Agora in your AWS account can be obtained using the Agora Solution Manager, which can be opened by selecting the Manage environments button in the Environments section of your Agora subscription.

From the Agora Solution Manager, selecting the Overview option from the Environments menu displays an Overview of your environment. Clicking the button located next to the name of a cluster displays a summary of the main AWS elements provisioned by Agora for the cluster.

From the Overview, the Actions drop-down for each cluster includes an option to View all events. Selecting this option opens the Cluster events page displaying all the events for the cluster. A detailed list of the steps executed can be viewed by selecting the button for each event. Selecting the Execution output option under the Output drop-down for a step, lists details of the AWS elements provisioned in the step.

For example, to identify a particular AWS element created during a Cloud cluster creation event, expand the event and search the displayed details for the step with the desired AWS element in its name. The Execution output for the step will list the AWS identifier for the created element.

In the following image we can see an example of how to find the AWS identifier of a Virtual DataPort target group created during an event step.

List of AWS Elements Created by Agora in the User’s Account¶

This section lists all the dependent AWS elements created and used by Agora for a deployment. Agora does not create any IAM service elements, these must be created by the user for subsequent use by Agora.

The list is divided into two sections, one listing AWS elements which imply costs and one that lists elements that do not. A brief description for each element provided summarizing their role in the Agora deployment. Each element’s name is a hyperlink to more detailed information about their AWS pricing.

AWS elements that do not imply costs:

• IAM::Role: The role to be assumed by Agora, with sufficient permissions to enable Agora to create the rest of the AWS elements. Removes the need for the management and use of access keys.

• IAM::InstanceProfile: Instance profile of the role, to be assumed by the Solution Manager instance.

• IAM::Policy: Policy of the role.

• EC2::VPC: VPC used by the Execution Plane. Optionally, this can be created by Agora or an existing VPC can be used.

• EC2::Subnet: Subnets used by the Execution Plane. Optionally, Agora can create the subnets or existing ones can be used. A public and a private subnet is required.

• EC2::RouteTable: Defines where network traffic from the subnet is directed. Used for operations such as deployments, recreations etc…

• EC2::NetworkInterface: Enables the load balancers of the services and EC2 instances deployed to connect to the VPC virtual network.

• EC2::SecurityGroup: Security groups for the ports of each service, for example ports 9443 or 9090 for Denodo Virtual DataPort.

• EC2::KeyPair: Used to access the EC2 instances. Optionally, Agora can create this or an existing one can be used.

• EC2::LaunchTemplate: Templates to facilitate instance launching. Only used when auto scaling is enabled.

• AutoScaling::AutoScalingGroup: Also created when auto scaling is enabled, grouping EC2 instances for use during auto scaling.

• ElasticLoadBalancingV2::TargetGroup: Created to group the ports of the Denodo services together, acting as the target to which requests received by the load balancer are routed.

• ElasticLoadBalancingV2::Listener: Created to check incoming requests and route them to the targets groups.

AWS elements that imply costs:

• EC2::InternetGateway: Allows VPC connections from and to the internet. Costs are dependant on the amount of traffic. Please see the section Data Transfer by following the link for more information.

• EC2::NatGateway: Needed to allow connections to the public internet from the private subnet.

• EC2::Elastic IP: For public communications between the internet and the instances.

• EC2::Instance: Instances to host the Denodo services.

• EC2::Volume: EBS (Elastic Block Storage) volumes of the instances.

• EC2::Ami: AMIs are created for the configuration of TLS and some processes such as updating the Execution Plane. AMIs do not imply direct costs, however, they need EBS snapshots that do have a cost implication.

• ElasticLoadBalancingV2::LoadBalancer: To distribute traffic among the instances. If internet facing is chosen, an IPv4 Public Address is assigned and charges will be incurred. Internet facing is enabled by default for Data Catalog.

AWS Elements Created Deploying With Agora Production Template¶

Using a deployment with an Agora production template as an example. This template deploys 3 environments. One environment for development, with 1 Virtual DataPort and 1 Data Catalog; and another two environments, staging and production, both with 1 Virtual DataPort, 1 Data Catalog and 1 Scheduler. In this example we are choosing to create new VPCs, subnets and keypairs.