KB478353: MicroStrategy on AWS - Top FAQs

Product Manager, Director •

Description

This knowledge base article reviews FAQs regarding implementation, business value, and licensing around Strategy on AWS.

FAQs

Q: What is Strategy on AWS?
Strategy on AWS allows organizations to get up and running quickly with a fully configured Strategy system and gives users the power to monitor, change, and maintain platform features themselves. Any organization now has the ability to invest in business intelligence and begin building transformational apps and dashboards in as little as 30 minutes.
Q: What is the main difference between the new Strategy on AWS and the Strategy Cloud you already have?
Strategy on AWS environments are deployed within the customers AWS account where it is the customer’s responsibility for maintaining the environment.
Strategy Cloud is a fully managed Platform as a service offering. This service includes a complete environment with features like intrusion detection, firewalls, load balancers and networking pre-configured for the Strategy environment by Strategy staff. The service also includes expert management for the Strategy application (Seamless upgrades).

Q: Why should I use Strategy on AWS?

Self-service provisioning options through an AWS-powered portal that offers full control to Strategy administrators looking to deploy cloud instances of any size on dedicated AWS infrastructure – plus the ability to manage and schedule tasks and operations in real-time.
The full breadth of Strategy capabilities, from enterprise data discovery to enterprise reporting and dashboards, optimized connectors to hundreds of databases, personalized distribution capabilities, powerful predictive analytics, and more. Make sure to check out the Learning Center to learn about all capabilities.
Mobile productivity apps customized with transaction-enabled workflows, and tailored to any business function or role.
RESTful APIs that provide users with the flexibility to self-create custom workflows and build personalized admin interfaces that automate Strategy on AWS operations.

Q: What can I do with Strategy on AWS?

Deploy the entire Strategy platform which is fully functional and configured in a matter of minutes in any of the 17 available AWS regions.
Deploy any of the 3 available offerings (Team, Department, and Enterprise) based on the need.
Ability to fully administer and manage deployment on the Amazon Web Services (AWS) cloud with a self-service Cloud Environment Manager.
Start, Stop, or Reboot Strategy environments from the Cloud Environment Manager on-demand as well as on-schedule
All actions are supported with RESTful APIs which allows users to automate and build customer workflows

Q: On what AWS Regions is Strategy on AWS available?
Currently, there are 17 supported regions for Strategy on AWS:

Northern Virginia (US-EAST-1)
Ohio (US-EAST-2)
California (US-WEST-1)
Oregon (US-WEST-2)
Canada (CA-CENTRAL-1)
Ireland (EU-WEST-1)
London (EU-WEST-2)
Paris (EU-WEST-3)
Frankfurt (EU-CENTRAL-1)
Stockholm (EU-NORTH-1)
Singapore (AP-SOUTHEAST-1)
Sydney (AP-SOUTHEAST-2)
Tokyo (AP-NORTHEAST-1)
Seoul (AP-NORTHEAST-2)
Mumbai (AP-SOUTH-1)
Sao Paulo (SA-EAST-1)
Bahrain (ME-SOUTH-1)

Q: How much does Strategy on AWS cost?
Strategy on AWS has two components that will have an impact on the cost:
1) Infrastructure
Since all the components of the Strategy Enterprise platform will be deployed in the customer's own Amazon AWS account, the infrastructure cost is billed directly to the customers through their Amazon Account. This bill is the AWS account holders responsibility and not managed or controlled by Strategy. Estimates of the AWS infrastructure costs can be found in the environment creation page, in the Strategy Cloud Platform console. Please keep in mind that these are only estimated as the cost can change based on stopping the environment, storage and In/Out transfer of data.

2) Strategy Software license
Strategy on AWS is designed to be a Bring Your Own License product. This means customers must purchase Strategy Software licenses through the regular sales channels and plug it directly in their newly deployed Strategy environment in AWS. Hint: Make sure to mention that you need a license for Strategy on AWS when talking to the Account Executive.

Q: How do I get started with Strategy on AWS?
The only pre-requisites are that you need to have a Strategy Resource Center account and an AWS account to get started. Step-by-step instructions on how to configure your AWS account can be found here. The Strategy Software license will free for 30 days. Customers are still responsible for the cost of the infrastructure.
Q: What are the different types of environments that I can deploy with Strategy on AWS?
Currently, there are 3 different Strategy on AWS Editions:

Team: Team Edition is an all-in-one machine which includes the Intelligence Server, Web Server and PostgreSQL database, installed on a single EC2 instance. Team Edition is oriented to serve small teams (around 25 users) to collaborate together.
Department: The Strategy on AWS Department Edition is designed to cover the main requirements of small businesses or departments within large corporations. It provides the full power of the Strategy Enterprise platform on a single machine while keeping the heart of the system (the metadata repository) on its own dedicated resources. Metadata uses AWS Relational Database Service(RDS) which provide more reliability and scalability.
Enterprise: The Strategy on AWS Enterprise Edition is designed for customers looking for increased performance, scalability and availability of their Strategy Enterprise applications by leveraging clustering and failover capabilities. During deployments of Enterprise, there are 2 EC2 instances each running the full platform but are deployed in different availability zones. The services (Intelligence Server, Web Server and Usher Security) are clustered for high availability and the metadata, based in RDS is deployed using Multi-Availability Zones for failover purposes.

Q: What instance types can I deploy on?
Teams edition environments utilize R4 and X1 instance types:

StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952

Department and Enterprise edition environments utilize R5 and X1 instance types:

StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952
StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952	StepAction1Strategy Web or Web Universal users log in to a project and request reports from their Web browsers2A third party IP distribution tool such as Cisco Local Router, Microsoft Network Load Balancing, or Microsoft Windows Load Balancing Service distributes the user connections from the Web clients among Web Servers.3The Strategy Web product load balancers on each Web Server collect load information from each cluster node, and then connect the users to the nodes that carry the lightest loads and run the project that the user logged into. All report requests are then processed by the nodes to which the users are connected4The Strategy Intelligence Server nodes receive the requests and process them. In addition, the nodes communicate with each other to maintain metadata synchronization and cache accessibility across nodes.5The nodes send the requests to the warehouse as queries as usual.ModelvCPUMemory(GiB)R4 family r4.large215.25r4.xlarge430.5r4.2xlarge861r4.4xlarge16122r4.8xlarge32244r4.16xlarge64488X1 family x1.16xlarge64976x1.32xlarge1281952ModelvCPUMemory(GiB)R5 family r5.large216r5.xlarge432r5.2xlarge864r5.4xlarge16128r5.8xlarge32256r5.12xlarge48384r5.16xlarge64512r5.24xlarge96768X1 family x1.16xlarge64976x1.32xlarge1281952

Q: Can I change instance sizes after the initial selection?
Yes, you have the flexibility to choose the current instance type for your application today, and then choose a different instance size as your business and application needs change. Strategy on AWS customers have the ability to scale their environment up or down with several instance size options from AWS.
Environments can scale on-demand or schedule based on usage patterns, application usage patterns, and data size. Customers can add new users at any time and deploy multiple environments and projects as they see fit.
Customers pay for what they use on the infrastructure according to the length of time.
Q: Which Strategy versions are supported with Strategy on AWS?
Strategy on AWS supports the most recent platform release and most recent feature release.

Q: Why do I need to go through the Configuration of the AWS Account?
Strategy on AWS deploys the Strategy components into your own AWS account. The first step is to grant the Strategy on AWS provisioning tool access to your AWS account. During the configuration, we configure access and deploy the infrastructure which is required to support Strategy platform using a Cloud Formation script. The Cloud Formation script triggered during configuration will do the following:

Create VPC/Subnets and all of its supporting network architecture
Create a 'step functions state' machine
Download Lambda script required to support the Strategy infrastructure deployment
Allow access to Strategy owned S3 buckets containing supporting files
Creates an IAM role named "ProvisionStrategy"

This also allows the correct user to deploy environments into the correct AWS account.
Q: Why do I need to go through the Validation of the AWS Account?
During the validation step, we verify that the Infrastructure stack has been deployed successfully, we add a trial certificate to your account and make sure that the Cloud environment manager has access to your account via Roles.
Q: How much access does Strategy have into the Customer's AWS account?
During the creation of Infrastructure stack, Cloud Formation creates a IAM role called as "ProvisionStrategy". Permissions provided to that role are limited and only the permissions necessary to configure and manage the environment is created. These permissions are required to manage deployed environments from the Strategy on AWS provisioning tool. If you no longer want Strategy to have access to your account, you can at any point 'Deploy and Forget' as well as delete the "ProvisionStrategy" role. If the role is deleted, you will not be able to manage the Strategy environment from the Strategy on AWS provisioning tool anymore.
Q: What happens when I deploy an environment and it fails?
There are some instances when the deployment of the environment fails. If any of the configuration steps fail, an automated email is sent out informing the user that the environment has failed. Hover over the tooltip to check the error messages.

If any of the "Configuration" steps have failed, please re-deploy the environment.
During the cases when the Infrastructure stack fails during configuration, please delete the stack and try again.
Q: How to delete the Infrastructure stack in case it fails?
There are some cases where it may be useful to delete the base Infrastructure stack. The following steps will guide you through the process of safely deleting the Infrastructure stack. Please note that once this stack has been deleted, you will not be able to deploy any more Strategy environments into your account as the required IAM roles and underlying infrastructure will be deleted. Use the following steps below for deletion:

In the CloudFormation console, select the checkbox for the Infrastructure stack.
After that, make sure to select Delete Stack from the Actions menu.

Monitor the progress of the stack deletion. Do not be alarmed if you receive an error indicating that one or more of the resources failed to delete; the following steps will walk you through the process of cleaning these resources.
If the Infrastructure stack no longer appears in the CloudFormation console, no further action is required at this time. If the Infrastructure stack Status is “DELETE_FAILED” continue on to the next step.
Select the Resources tab of the Infrastructure Stack and take note of the resources which failed to delete and their error messages. Most commonly these resources are the IAM Roles “MSTRInstanceProfileRole” and “ProvisionStrategy” with error messages: “Cannot delete entity, must delete policies first”.

Navigate to the console corresponding to the resource type which failed to delete. Locate and delete the resource.

For example, if the IAM .Role failed to delete, navigate to the IAM console, locate the MSTRInstanceProfileRole resource, and delete the resource.
Repeat Step 4 for all resources which failed to delete.
Return to the CloudFormation console, select the checkbox for the Infrastructure stack.

Then, “Delete Stack” from the “Actions” menu.
Select the checkboxes for the resources which failed to delete during Step 1, then select “Yes, Delete."

Monitor the progress of the stack deletion. All resources should now successfully delete.

Q: What operating systems are supported within Strategy on AWS?
Strategy is Installed on Redhat Linux or Amazon Linux.
Strategy Developer tools are installed on Microsoft Windows Server 2016.
Q: Where is Strategy on AWS Installed?

On Linux Strategy Platform is installed on : /opt/mstr

Q: Where ports are being used for Strategy on AWS?
Currently, the ports being used are:

Web Server : 443
Gateway : 3443
Collaboration Server : 3000
JSON-Data API : 10443

Q: How do I access the Strategy on AWS environment?
As soon as an environment is created, users will receive an automated email with instructions on how to access Strategy. After logging in, you will be directed to the Strategy on AWS Landing Page where we have put together all the useful information any administrator will need, such as Web URL, Mobile Admin URL, Machine name and more.
See the next question (FAQ) for an example.
Q: How do I access the developer machine?

Create an environment using Strategy on AWS.
Wait to receive an email confirming that your environment has been created
Use your mstr credentials to access the Strategy Platform via the Landing page.

In the Strategy on AWS landing page, select Remote Desktop Gateway under Administration.

Once you access the Remote Desktop Gateway, select the Developer Instance RDP option.

Q: How to start and stop services for the Strategy platform?
The Strategy platform comes with the startup scripts which are configured to be used.
service mstr <options> : Strategy init script will allow you check the status of the Strategy Intelligence Server, Listener, and Tomcat service status.
The startup script also provides functionalities to start and stop the Strategy services.
Below are some sample scripts you can run.
To start and stop the Intelligence Server : service mstr iserverstart, service mstr iserverstop
To start and stop the Tomcat service : service mstr tomcatstart, service mstr tomcatstop
To start and stop the Listener service : service mstr listenerstart, service mstr listenerstop
To start and stop the Collaboration service : service collab-server start, service collab-server stop
To start and stop Kafka and Zookeeper : service kafka-zookeeper start, service kafka-zookeeper stop
Q: How to change your Strategy Web password?

Click the Strategy icon at the top of the page and select Preferences. The User Preferences page opens.
On the left, click Change password.
Provide the necessary information in the following order:
Old password: Enter the old password (the password you are changing).
New password: Enter the new password.
New password verification: Enter the new password again (to ensure you have entered the new password correctly).
Click Change Password to apply your changes.
The new password will be active the next time you log into Strategy Web.
To change another users password, please follow the steps here .

Learning Resources

Or feel free to visit the Documentation pages for more product information.

Comment

0 comments

Details

Knowledge Article

Published:

August 7, 2017

Last Updated:

October 31, 2022

FAQs

Self-service provisioning options through an AWS-powered portal that offers full control to Strategy administrators looking to deploy cloud instances of any size on dedicated AWS infrastructure – plus the ability to manage and schedule tasks and operations in real-time.

The full breadth of Strategy capabilities, from enterprise data discovery to enterprise reporting and dashboards, optimized connectors to hundreds of databases, personalized distribution capabilities, powerful predictive analytics, and more. Make sure to check out the Learning Center to learn about all capabilities.

Mobile productivity apps customized with transaction-enabled workflows, and tailored to any business function or role.

RESTful APIs that provide users with the flexibility to self-create custom workflows and build personalized admin interfaces that automate Strategy on AWS operations.

Q: What can I do with Strategy on AWS?

Deploy the entire Strategy platform which is fully functional and configured in a matter of minutes in any of the 17 available AWS regions.

Deploy any of the 3 available offerings (Team, Department, and Enterprise) based on the need.

Ability to fully administer and manage deployment on the Amazon Web Services (AWS) cloud with a self-service Cloud Environment Manager.

Start, Stop, or Reboot Strategy environments from the Cloud Environment Manager on-demand as well as on-schedule

All actions are supported with RESTful APIs which allows users to automate and build customer workflows

Q: On what AWS Regions is Strategy on AWS available?
Currently, there are 17 supported regions for Strategy on AWS:

Northern Virginia (US-EAST-1)

Ohio (US-EAST-2)

California (US-WEST-1)

Oregon (US-WEST-2)

Canada (CA-CENTRAL-1)

Ireland (EU-WEST-1)

London (EU-WEST-2)

Paris (EU-WEST-3)

Frankfurt (EU-CENTRAL-1)

Stockholm (EU-NORTH-1)

Singapore (AP-SOUTHEAST-1)

Sydney (AP-SOUTHEAST-2)

Tokyo (AP-NORTHEAST-1)

Seoul (AP-NORTHEAST-2)

Mumbai (AP-SOUTH-1)

Sao Paulo (SA-EAST-1)

Bahrain (ME-SOUTH-1)