Você está na página 1de 35

Cloud Analytics Modernization

on the AWS Cloud


with Informatica, Tableau Server,
and AWS Services
Quick Start Reference Deployment

November 2018

Ryann Lannan – Informatica Cloud Data Integration Team


Vaidy Krishnan – Tableau Product Management
Vinod Shukla – AWS Quick Start Reference Team

AWS can provide you with AWS credits for this deployment. Please
fill out our form and we will reach out to you.

Contents
Quick Links ............................................................................................................................ 3
Overview ................................................................................................................................. 3
Solution Components ......................................................................................................... 4
Costs and Licenses .............................................................................................................. 5
Prerequisites ..........................................................................................................................6
Specialized Knowledge .......................................................................................................6
Technical Requirements.....................................................................................................6
Architecture............................................................................................................................ 7
Infrastructure ..................................................................................................................... 7
AWS Services ......................................................................................................................8
Tableau Services .................................................................................................................8

Page 1 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Informatica EDC Services ..................................................................................................9


Informatica Intelligent Cloud Services ............................................................................ 10
Quick Start Dataset........................................................................................................... 10
Deployment Options .............................................................................................................11
Deployment Steps ................................................................................................................ 12
Step 1. Prepare Your AWS Account .................................................................................. 12
Step 2. Register at Informatica Marketplace ................................................................... 13
Step 3. Launch the Quick Start ........................................................................................ 13
Step 4. Monitor the Deployment ......................................................................................23
Step 5: Test the Deployment ............................................................................................ 25
Optional: Using Your Own Dataset ................................................................................. 28
Optional: Adding VPC Definitions .................................................................................. 28
Best Practices .......................................................................................................................29
Using Cloud Analytics Modernization on AWS ...............................................................29
Manual Cleanup ...............................................................................................................29
Troubleshooting ...................................................................................................................32
Additional Resources ...........................................................................................................34
GitHub Repository ...............................................................................................................34
Document Revisions ............................................................................................................ 35

This Quick Start deployment guide was created by Informatica and Tableau Software in
collaboration with Amazon Web Services (AWS).

Quick Starts are automated reference deployments that use AWS CloudFormation
templates to deploy key technologies on AWS, following AWS best practices.

Page 2 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Quick Links
The links in this section are for your convenience. Before you launch the Quick Start, please
review the architecture, security, and other considerations discussed in this guide.

 If you have an AWS account, and you’re already familiar with AWS services, Informatica
products, and Tableau Server, you can launch the Quick Start to build the architecture
shown in Figure 1 in a new or existing virtual private cloud (VPC). The deployment takes
approximately two hours. If you’re new to AWS, Informatica, or Tableau, please review
the implementation details and follow the step-by-step instructions provided later in
this guide.

Launch Launch
(for new VPC) (for existing VPC)

 If you want to take a look under the covers, you can view the AWS CloudFormation
templates that automate the deployment.

View template View template


(for new VPC) (for existing VPC)

Overview
This Quick Start reference deployment guide provides step-by-step instructions for
deploying a cloud analytics modernization solution on the AWS Cloud with Informatica and
Tableau software.

Cloud analytics modernization is a powerful approach to fuel data-driven digital


transformations and migrations to the cloud. This integrated solution from Informatica,
Tableau Software, and AWS speeds the time to evaluate and deploy an end-to-end solution
for self-service cloud analytics. It enables you to connect to cloud and on-premises data
sources, and to catalog and profile your data assets for analysis and visualization. The Quick
Start includes the following services:
 Informatica Intelligent Cloud Services, for secure data pipelines to cloud and on-
premises data.
 Informatica Enterprise Data Catalog (EDC), for data source cataloging that provides
provenance, lineage, and relationships for data assets. A plug-in enables users to
access business and technical context from within Tableau.
 Tableau Server, for secure, governed visual analytics.

Page 3 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

 Amazon Redshift, for fast, cost-effective data warehousing.


 Amazon Relational Database Service (Amazon RDS) with Oracle Database, for
storing aggregate data for the Tableau dashboards.

This Quick Start supports the following key design principles:


 Data is easily accessible to analysts and other business users through self-service.
 You can analyze all your data across your software as a service (SaaS) and on-premises
applications.
 You can enable your users with self-service analytics so they can easily discover and
understand trusted and relevant enterprise-wide data for analytics.
 You can use high-productivity, GUI-driven tools that abstract complexity and reduce
costs.
 Data, which is a valuable corporate asset, is managed collaboratively, and supports your
data governance, data quality, and data security initiatives.

This Quick Start is for users who want to deploy and develop a cloud analytics
modernization solution, managed by their IT team, to enable their business.

Solution Components
This cloud analytics modernization solution uses the following products:

Informatica Intelligent Cloud Services is a next-generation integration platform as a


service (iPaaS) that provides enterprise data management through a suite of intelligent
cloud services. Informatica Intelligent Cloud Services enables you to build high-performant
cloud data warehouses, create and manage data integration projects, and orchestrate and
automate business processes. You can create processes that are event-driven or exposed as
APIs, and integrate, test, and monitor the API endpoints you consume. Informatica
Intelligent Cloud Services analyzes the state of orchestration and deployment activities
across all cloud services and provides in-depth, actionable insights. Informatica Intelligent
Cloud Services also provides analysis of enterprise health, domain-level analytics, job and
workflow statistics, and node-level resource consumption.

Informatica Enterprise Data Catalog (EDC) brings together all data assets in an
enterprise and presents a comprehensive view of the data assets and data asset
relationships. Enterprise Data Catalog captures the technical, business, and operational
metadata for a large number of data assets that you use to determine the effectiveness of
enterprise data. From across the enterprise, Enterprise Data Catalog gathers information

Page 4 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

related to metadata, including column data statistics, data domains, data object
relationships, and data lineage information. A comprehensive view of enterprise metadata
can help you make critical decisions about data integration, data quality, and data
governance in the enterprise.

Tableau Server is a scalable, enterprise-class analytics platform that enables you to


securely scale data and analytics across your organization. Users can filter and drill down
into data or author new content without being limited to predefined questions, wizards, or
chart types. They can share and collaborate with Tableau workbooks and data sources.
Distributed mobile and browser-based users can interact with workbooks published to the
server from Tableau Desktop or embedded into company portals. Tableau Desktop users
can leverage prepared data sources published from Tableau Prep.

The Quick Start also includes Amazon Redshift and Amazon RDS, which serve as data
sources for Tableau Server. For additional details on Quick Start components, see the
Architecture section.

Costs and Licenses


You are responsible for the cost of the AWS services used while running this Quick Start
reference deployment. There is no additional cost for using the Quick Start.

The AWS CloudFormation templates for this Quick Start include configuration parameters
that you can customize. Some of these settings, such as instance type, will affect the cost of
deployment. See the pricing pages for each AWS service you will be using for cost estimates.

Tip After you deploy the Quick Start, we recommend that you enable the AWS Cost
and Usage Report to track costs associated with the Quick Start. This report delivers
billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your
account. It provides cost estimates based on usage throughout each month, and
finalizes the data at the end of the month. For more information about the report,
see the AWS documentation.

This Quick Start requires a license or trial subscription to deploy the following services:
 Informatica Intelligent Cloud Services
 Informatica Enterprise Data Catalog
 Tableau Server

Page 5 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Register at Informatica Marketplace to obtain a trial license for Informatica Intelligent


Cloud Services and to create a trial organization. Deploying the Quick Start will
automatically activate Enterprise Data Catalog and Tableau Server software and trial
license keys.

Prerequisites
Specialized Knowledge
Before you deploy this Quick Start, we recommend that you become familiar with the
following AWS services. (If you are new to AWS, see the Getting Started Resource Center.)
 Amazon Virtual Private Cloud (Amazon VPC)
 Amazon Elastic Compute Cloud (Amazon EC2)
 Amazon Redshift
 Amazon S3
 Amazon RDS

In addition, we recommend that you review the following:


 Informatica Intelligent Cloud Services
 Enterprise Data Catalog
 Tableau Server on AWS Quick Start

Technical Requirements
Before you deploy this Quick Start, verify the following:
 You have an account with AWS, and you know the account login information. The user
should be granted administrative privileges, which allows full access to AWS services
and resources.
 You have a license or trial subscription for Informatica Intelligent Cloud Services. To
sign up for a free trial, go to Informatica Marketplace.
 This Quick Start will automatically deploy Enterprise Data Catalog with a 30-day trial
license.
 This Quick Start will automatically deploy Tableau Server with a 14-day trial license. If
you have a Tableau Server license key and would like to use it, enter it in the Tableau
Server license key field during deployment (see step 3). To obtain a product key,
contact sales@tableau.com.

Page 6 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Architecture
Deploying this Quick Start for a new virtual private cloud (VPC) with the default parameters
builds the following cloud analytics modernization environment in the AWS Cloud.

Figure 1: Cloud analytics modernization solution deployed on AWS

Infrastructure
The Quick Start sets up a highly available architecture that spans two Availability Zones,
and a VPC configured with two public and two private subnets according to AWS best
practices.
The Quick Start installs and configures the following infrastructure components:
 Amazon VPC. This service lets you provision a logically isolated section of the AWS
Cloud where you can launch resources in a virtual network that you define. The VPC
provides a network architecture with multiple public and private subnets that span
multiple Availability Zones, so that AWS resources can be deployed in highly available
configurations.

Page 7 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

 Remote Desktop Gateway. The Quick Start deploys a Remote Desktop Gateway
instance in an Auto Scaling group in the public subnets and configures it with an Elastic
IP address for outbound internet connectivity. This gateway provides secure access to
Microsoft Windows instances located in the private and public subnets. The Remote
Desktop Gateway instance uses the Remote Desktop Protocol (RDP) over HTTPS to
establish a secure, encrypted connection between remote users on the internet and
Windows-based EC2 instances, without needing to configure a virtual private network
(VPN) connection. This helps reduce the attack surface on your Windows-based
instances and provides a remote administration solution for administrators.
 NAT Gateway. The NAT gateway instance in the public subnet enables instances in the
private subnets to connect to the internet or to other AWS services, but prevents the
internet from initiating a connection with those instances.
 IAM roles. The Quick Start configures AWS Identity and Access Management (IAM)
roles to provide the required access for AWS resources created through the Quick Start.
These IAM roles enable access to data in Amazon S3, enable Amazon Redshift to copy
data from the sample dataset’s S3 bucket and key prefix into its tables, and enable
association with the Amazon Redshift cluster.

AWS Services
 Amazon S3. Amazon S3 is an object store that provides artifacts necessary for the
Quick Start, including datasets, dashboards, and SQL required to configure AWS
database services and to compute aggregates for the sample dataset.
 Amazon Redshift. Amazon Redshift is a fast, fully managed, petabyte-scale data
warehouse. The Quick Start uses Amazon Redshift to provide full fact tables, ad-hoc
exploration and aggregation, and filtered drill-downs. Amazon Redshift is optimized for
computationally intensive workloads such as computation of aggregates and complex
joins, and supports analysis on both Microsoft Windows and macOS.
 Amazon RDS with Oracle Database. This service makes it easy to set up, operate,
and scale a relational database in the cloud. It provides the Quick Start with high-query-
volume aggregate tables that feed scale-out dashboards. It is deployed in multiple
Availability Zones for high availability.

Tableau Services
 Tableau Server on Amazon EC2. The Quick Start provides a single-node
deployment of Tableau Server on Windows with the ability to host and serve analytics
dashboards and workbooks, which is supported by the trial license. If you have a
Tableau Server license, you can enter it upon deployment. For a Tableau Server

Page 8 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

standalone or cluster (multi-node) environment on AWS, see the Quick Start for
Tableau Server.
 Sample Tableau Server dashboard. Dashboards, consistent with the sample
dataset, demonstrate how to connect to multiple data sources in AWS to optimize
performance.

Informatica EDC Services


The following services are set up on Amazon RDS:
 Informatica domain. The Informatica domain is the fundamental administrative unit
of the Informatica platform. The Informatica platform has a service-oriented
architecture that provides the ability to scale services and share resources across
multiple machines.
 Model Repository Service. The model repository is a relational database that stores
all the metadata for projects created using Informatica client tools. The model
repository also stores run-time and configuration information for applications that are
deployed to a Data Integration Service.

The following services are set up on the Informatica EC2 node:


 Analyst Service. The Analyst Service runs the Analyst tool in the Informatica domain.
The Analyst Service manages the connections between the service components and the
users who log in to the Analyst tool. You can perform column and rule profiling, manage
scorecards, and manage bad records and duplicate records in the Analyst tool.
 Business Glossary. The Business Glossary consists of online glossaries of business
terms and policies that define important concepts within an organization. Data stewards
create and publish terms that include information such as descriptions, relationships to
other terms, and associated categories. Glossaries are stored in a central location for
easy lookup by consumers. Glossary assets include business terms, policies, and
categories that contain information that consumers might search for. A glossary is a
high-level container that stores Glossary assets. A business term defines relevant
concepts within the organization, and a policy defines the business purpose that governs
practices related to the term. Business terms and policies can be associated with
categories, which are descriptive classifications.
 Catalog Service. This service runs Enterprise Data Catalog and manages connections
between service components and external applications.
 Hadoop. An embedded Hadoop cluster uses Hortonworks, running the Hadoop
Distributed File System (HDFS), Apache HBase, YARN, and Solr.

Page 9 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

 Informatica Cluster Service. The Informatica Cluster Service runs and manages all
Hadoop services, Apache Ambari server, and Apache Ambari agents on the embedded
Hadoop cluster.
 Metadata and Catalog. The Metadata Catalog includes the metadata persistence
store, search index, and graph database in the embedded Hadoop cluster. The catalog
represents an indexed inventory of all the data assets in the enterprise that you
configure in Enterprise Data Catalog. Enterprise Data Catalog organizes all the
enterprise metadata in the catalog and enables the users of external applications to
discover and understand the data.

Informatica Intelligent Cloud Services


 Informatica Cloud Secure Agent. An Informatica Cloud Secure Agent is a
lightweight program that runs tasks and enables secure communication across the
firewall between your organization and Informatica Intelligent Cloud Services. It allows
you to connect to access and manage data in cloud and on-premise applications,
platforms, databases, and flat files. The Informatica Cloud Secure Agent is also deployed
on the Informatica EC2 node.

Quick Start Dataset


The Quick Start includes a sample dataset that demonstrates the cloud analytics workflow.
The Quick Start is designed so that you can replace this dataset as needed for your use case,
as explained later in this guide. The dataset is stored in Amazon S3 and includes the
following data components and artifacts:
 Quick Start seed data in CSV format.
 Informatica Intelligent Cloud Services mapping that transforms CSV seed data and
stores it in an Amazon Redshift target: S3 to Redshift_ITQS
 Informatica Intelligent Cloud Services mapping that aggregates Amazon Redshift
records and stores it in an Oracle target: Aggregate Store Sales_ITQS

Tableau Server uses Amazon Redshift and Oracle as data sources for visualization.

Figure 2 shows the data flow in the cloud analytics modernization solution.

Page 10 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Figure 2: Cloud analytics modernization data flow

Deployment Options
This Quick Start provides two deployment options:
 Deployment of the cloud analytics modernization solution into a new VPC
(end-to-end deployment). This option builds a new VPC with public and private
subnets, and then deploys the cloud analytics modernization solution into that
infrastructure.
 Deployment of the cloud analytics modernization solution into an existing
VPC. This option provisions cloud analytics components into your existing AWS
infrastructure.
The Quick Start provides separate templates for these options. It also lets you configure
Amazon Redshift, Amazon RDS, Informatica, and Tableau settings, as discussed later in
this guide.

Page 11 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Deployment Steps
Step 1. Prepare Your AWS Account
1. If you don’t already have an AWS account, create one at https://aws.amazon.com by
following the on-screen instructions.
2. Use the region selector in the navigation bar to choose the AWS Region where you want
to deploy the cloud analytics modernization solution on AWS.
3. Create a key pair in your preferred region.
When you log in to any Amazon EC2 system, you use a password file for authentication.
The file is called a private key file and has a file name extension of .pem. If you do not
have an existing .pem key to use, follow the instructions in the AWS documentation to
create a key pair.

Note Your administrator might ask you to use a particular existing key pair.

When you create a key pair, you save the .pem file to your desktop system.
Simultaneously, AWS saves the key pair to your account. Make a note of the key pair
that you want to use for the cloud analytics modernization instance, so that you can
provide the key pair name during the deployment in step 3.
4. If necessary, request a service limit increase for the following instance types. You might
need to do this if you already have existing deployments that use these instance types,
and you think you might exceed the default limits with this reference deployment.

Component Instance type

Informatica domain, EDC c4.4xlarge


services, Secure Agent

Embedded metadata cluster c4.8xlarge

Tableau Server m5.4xlarge

Remote Desktop for Tableau t2.large

Oracle RDS db.m4.2xlarge

Amazon Redshift cluster dc1.large-1 node

Page 12 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Step 2. Register at Informatica Marketplace


1. If you haven’t already subscribed to Informatica Intelligent Cloud Services, Informatica
Enterprise Data Catalog, and Tableau Server, register at Informatica Marketplace.
2. Confirm your account through the verification email and input your password when
prompted.

Step 3. Launch the Quick Start


Note You are responsible for the cost of the AWS services used while running this
Quick Start reference deployment. There is no additional cost for using this Quick
Start. For full details, see the pricing pages for each AWS service you will be using in
this Quick Start. Prices are subject to change.

1. Choose one of the following options to launch the AWS CloudFormation template into
your AWS account. For help choosing an option, see deployment options earlier in this
guide.

Option 1 Option 2
Deploy cloud analytics Deploy cloud analytics
modernization into a new VPC modernization into an existing
on AWS VPC on AWS

Launch Launch

Important If you’re deploying the cloud analytics modernization solution into an


existing VPC, make sure that your VPC has two private subnets and one public
subnet in different Availability Zones. These subnets require NAT gateways or NAT
instances in their route tables, to allow the instances to download packages and
software without exposing them to the Internet. You’ll also need the domain name
option configured in the DHCP options as explained in the Amazon VPC
documentation. You’ll be prompted for your VPC settings when you launch the Quick
Start.

Each deployment takes about two hours to complete.


2. Check the region that’s displayed in the upper-right corner of the navigation bar and
change it if necessary. This is where the network infrastructure for the cloud analytics

Page 13 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

modernization solution will be built. The template is launched in the US East (Ohio)
Region by default.
3. On the Select Template page, keep the default setting for the template URL, and then
choose Next.
4. On the Specify Details page, change the stack name if needed. Review the parameters
for the template. Provide values for the parameters that require input. For all other
parameters, review the default settings and customize them as necessary. When you
finish reviewing and customizing the parameters, choose Next.
In the following tables, parameters are listed by category and described separately for
the two deployment options:
– Parameters for deploying components into a new VPC
– Parameters for deploying components into an existing VPC

Note The templates for the two scenarios share most, but not all, of the same
parameters. For example, the template for an existing VPC prompts you for the VPC
and subnet IDs in your existing VPC environment. You can also download the
templates and edit them to create your own parameters based on your specific
deployment scenario.

 Option 1: Parameters for deploying into a new VPC


View template
Informatica Intelligent Cloud Services Credentials:
Parameter label Default Description
(name)

Work email Requires input The email address used for Informatica Intelligent Cloud
(EmailID) Services registration and the Tableau trial account.

IICS username Requires input The user name for accessing Informatica Intelligent Cloud
(IICSUsername) Services.

IICS password Requires input The password associated with the Informatica Intelligent
(IICSPassword) Cloud Services user name. The password used for Quick Start
deployment cannot contain special characters.

Page 14 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Network Configuration:
Parameter label Default Description
(name)

Availability Zones Requires input The list of Availability Zones to use for the subnets in the VPC.
(AvailabilityZones) The Quick Start uses two Availability Zones from your list and
preserves the logical order you specify.

VPC definition QuickstartDefault The VPC definition name from the map (Mappings section)
(VPCDefinition) maintained in this Quick Start’s master template. Each
definition specifies a VPC configuration, including the number
of Availability Zones to be used for the deployment and the
CIDR blocks for the VPC, public subnets, and private subnets.
You can support multiple VPC definitions by extending this
map and choosing the appropriate name. If you do not need to
change the VPC configuration, keep the default setting.
For more information, see the section Optional: Adding VPC
Definitions later in this guide.

Remote Access CIDR Requires input The CIDR IP range that is permitted to access the VPC. We
(RemoteAccessCIDR) recommend that you use a constrained CIDR range to reduce
the potential of inbound attacks from unknown IP addresses.
For example, the IPv4 block 192.168.100.0/22 represents the
1024 IPv4 addresses from 192.168.100.0 to 192.168.103.255.
There are many tools available to help you calculate subnet
CIDR blocks; for example, see http://www.subnet-
calculator.com/cidr.php.
Note For ease of deployment, we have simplified the
requirements to just one CIDR range. However, in production
scenarios, we highly recommend using one or separate CIDR
group ranges for Tableau Server, Tableau Services Manager,
and remote desktop protocol (RDP).

Hosted Zone name Optional The name of the hosted zone within which the Quick Start will
(HostedZoneName) create convenient DNS entries for AWS resources. If you don’t
want to create DNS entries or you aren’t using AWS Route 53
for DNS, leave this parameter blank; otherwise, enter the
hosted zone name, including the trailing period (for example,
dev.example.com.).

Amazon Redshift Configuration:


Parameter label Default Description
(name)

Redshift database quickstart The name of the database for storing visualization data, to be
name created in the Amazon Redshift cluster. This string must
(RedshiftDatabaseName) contain lowercase letters (a-z) and numbers (0-9) only. If you
are using an existing cluster for visualization data, provide a
valid database name.

Page 15 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter label Default Description


(name)

Redshift username redshift The user name that is associated with the master user account
(RedshiftUsername) for the Amazon Redshift cluster that is being created. This
string must start with a lowercase letter (a-z) and must contain
lowercase letters (a-z) and numbers (0-9) only.

Redshift password Requires input The password that is associated with the master user account
(RedshiftPassword) for the Amazon Redshift cluster that is being created. The
password must be an 8-64 character string that consists of at
least one uppercase letter, one lowercase letter, and one
number.

Confirm Redshift Requires input The password that is associated with the master user account
password for the cluster that is being created. This must match the
(ConfirmRedshift password you entered for the Redshift password
Password) parameter.

Amazon Environment and Machine Configuration


Parameter label Default Description
(name)

Key pair name Requires input A public/private key pair, which allows you to connect securely
(KeyPairName) to your instance after it launches. When you created an AWS
account, this is the key pair you created in your preferred
region.

Amazon RDS Configuration:


Parameter label Default Description
(name)

RDS instance Requires input The password for the database instance associated with
password Informatica services and Tableau Server tasks. This must be
(RDSInstancePassword) an 8-30 character string of printable ASCII characters,
excluding slash marks (/), quotation marks ("), and at signs
(@).

Confirm RDS instance Requires input The password for the database instance associated with
password Informatica services and Tableau Server tasks. This must
(ConfirmRDSInstance match the password you entered for the RDS instance
Password) password parameter.

Enterprise Data Catalog Configuration:


Parameter label Default Description
(name)

Informatica Requires input The user name to access Informatica Administrator. This must
Administrator be a 4-15 character string that starts with an uppercase or
lowercase letter and includes only alphanumeric characters
username

Page 16 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter label Default Description


(name)
(InformaticaAdmin and underscores (_). The user name must not be
Username) “administrator.”

Informatica Requires input The password to access Informatica Administrator. This must
Administrator be a 5-64 character string that starts with an uppercase or
password lowercase letter and includes only alphanumeric characters
(InformaticaAdmin and underscores (_).
Password)

Confirm Informatica Requires input The password to access Informatica Administrator. This must
Administrator match the password you entered for the Informatica
password administrator password parameter.
(ConfirmInformatica
AdminPassword)

Tableau Remote Desktop Gateway Configuration:


Parameter label Default Description
(name)

Remote Desktop admin The user name for the new local administrator account for the
Gateway admin Remote Desktop Gateway. This is a 5-25 character,
username alphanumeric string.
(RemoteDesktopGateway
AdminUser)

Remote Desktop Requires input The password for the administrative account for the Remote
Gateway admin Desktop Gateway. This must be an 8-32 character string that
password contains letters, numbers, and symbols, excluding ampersands
(RemoteDesktopGateway (&). The password shouldn’t include the user name.
AdminPassword)

Domain DNS name example.com The fully qualified domain name (FQDN) of the Remote
(DomainDNSName) Desktop Gateway. This must be a 3-63 character string that
contains alphanumeric characters, periods (.), and hyphens
(-). It must not end in a number, period, or hyphen.

Tableau Server Configuration:


Parameter label Default Description
(name)

Tableau Services admin The user name for the Tableau Services Manager (TSM)
Manager (TSM) administrator. This is a 3-30 character string that consists of
administrator alphanumeric characters and underscores (_). It must begin
username with an uppercase or lowercase letter. Do not use
(TableauManager Administrator or administrator as the user name.
Username)

Tableau Services Requires input The password for the Tableau Services Manager (TSM)
Manager (TSM) administrator. This is an 8-120 character string. It should

Page 17 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter label Default Description


(name)
administrator contain at least one special character, one number, one
password uppercase letter, and one lowercase letter. Double quotes (")
(TableauManager and dollar signs ($) are not allowed.
Password)

Tableau Server admin The user name of the initial administrator for Tableau Server.
administrator This is a 5-20 character string that begins with an uppercase
username or lowercase letter and contains only alphanumeric characters
(TableauServerAdmin and underscores (_).
User)

Tableau Server Requires input The password of the initial administrator for Tableau Server.
administrator This is an 8-120 character string. It should contain at least one
password special character, one number, one uppercase letter, and one
(TableauServerAdmin lowercase letter. Double quotes (") and dollar signs ($) are not
Password) allowed.

Tableau Server license Optional The license key for Tableau Server. For more information, see
key the Prerequisites section. Leave this parameter blank if you’re
(TableauServerLicense using a trial license.
Key)

AWS Quick Start Configuration:

Note Informatica recommends that you do not change the default values for the
parameters in this category.

Parameter label Default Description


(name)

Quick Start S3 Bucket aws-quickstart- The S3 bucket name for the Quick Start assets. The bucket
Name informatica-tableau name can include numbers, lowercase letters, uppercase
(QSS3BucketName) letters, and hyphens (-), but should not start or end with a
hyphen. You can specify your own bucket if you copy all the
Quick Start assets and submodules into it. You might do this if
you want to customize the templates and override the Quick
Start behavior for your specific implementation.

Quick Start S3 Key quickstart- The S3 key prefix for your copy of Quick Start assets, if you
Prefix informatica- decide to customize or extend the Quick Start for your own
(QSS3KeyPrefix) tableau-analytics/ use. The key prefix can include numbers, lowercase letters,
uppercase letters, hyphens (-), and slash marks (/).

Page 18 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

 Option 2: Parameters for deploying into an existing VPC


View template

Informatica Intelligent Cloud Services Credentials:


Parameter label Default Description
(name)

Work email Requires input The email address used for Informatica Intelligent Cloud
(EmailID) Services registration and the Tableau trial account.

Username for IICS Requires input The user name for accessing Informatica Intelligent Cloud
(IICSUsername) Services.

Password for IICS Requires input The password associated with the Informatica Intelligent
(IICSPassword) Cloud Services user name. The password used for Quick Start
deployment cannot contain special characters.

Network Configuration:
Parameter label Default Description
(name)

Existing VPC ID Requires input The ID of your existing VPC (e.g., vpc-0343606e). Your VPC
(VPCID) should have one public subnet and two private subnets across
different Availability Zones.

Existing VPC CIDR 10.0.0.0/16 The CIDR block for your existing VPC.
(VPCCIDR)

Existing VPC private Requires input The ID of the private subnet in Availability Zone 1 in your
subnet 1 ID existing VPC (e.g., subnet-a0246dcd).
(PrivateSubnet1ID)

Existing VPC private Requires input The ID of the private subnet in Availability Zone 2 in your
subnet 2 ID existing VPC (e.g., subnet-b58c3d67).
(PrivateSubnet2ID)

Existing VPC public Requires input The ID of the public subnet in Availability Zone 1 in your
subnet 1 ID existing VPC (e.g., subnet-a0124abc).
(PublicSubnet1ID)

Hosted Zone name Optional The name of the hosted zone within which the Quick Start will
(HostedZoneName) create convenient DNS entries for AWS resources. If you don’t
want to create DNS entries or you aren’t using AWS Route 53
for DNS, leave this parameter blank; otherwise, enter the
hosted zone name, including the trailing period (for example,
dev.example.com.).

Remote Access CIDR Requires input The CIDR IP range that is permitted to access the VPC. We
(RemoteAccessCIDR) recommend that you use a constrained CIDR range to reduce
the potential of inbound attacks from unknown IP addresses.
For example, the IPv4 block 192.168.100.0/22 represents the
1024 IPv4 addresses from 192.168.100.0 to 192.168.103.255.
There are many tools available to help you calculate subnet

Page 19 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter label Default Description


(name)
CIDR blocks; for example, see http://www.subnet-
calculator.com/cidr.php.
Note For ease of deployment, we have simplified the
requirements to just one CIDR range. However, in production
scenarios, we highly recommend using one or separate CIDR
group ranges for Tableau Server, Tableau Services Manager,
and remote desktop protocol (RDP).

Amazon Redshift Configuration:


Parameter label Default Description
(name)

Amazon Redshift host Optional The DNS name or IP address of the master node of an existing
(RedshiftHost) Amazon Redshift cluster that you intend to use for the
Informatica sample jobs. Leave this blank to create a new
Amazon Redshift cluster in the VPC you specified with the
Existing VPC ID parameter.

Redshift database quickstart The name of the database for storing visualization data, to be
name created in the Amazon Redshift cluster. This string must
(RedshiftDatabaseName) contain lowercase letters (a-z) and numbers (0-9) only. If you
are using an existing cluster for visualization data, provide a
valid database name.

Redshift username redshift The user name that is associated with the master user account
(RedshiftUsername) for the Amazon Redshift cluster that is being created. This
string must start with a lowercase letter (a-z) and must contain
lowercase letters (a-z) and numbers (0-9) only.

Redshift password Requires input The password that is associated with the master user account
(RedshiftPassword) for the Amazon Redshift cluster that is being created. The
password must be an 8-64 character string that consists of at
least one uppercase letter, one lowercase letter, and one
number.

Confirm Redshift Requires input The password that is associated with the master user account
password for the cluster that is being created. This must match the
(ConfirmRedshift password you entered for the Redshift password
Password) parameter.

Amazon Environment and Machine Configuration


Parameter label Default Description
(name)

Key Pair name Requires input A public/private key pair, which allows you to connect securely
(KeyPairName) to your instance after it launches. When you created an AWS
account, this is the key pair you created in your preferred
region.

Page 20 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Amazon RDS Configuration:


Parameter label Default Description
(name)

RDS instance Requires input The password for the database instance associated with
password Informatica services and Tableau Server tasks. This must be
(RDSInstancePassword) an 8-30 character string of printable ASCII characters,
excluding slash marks (/), quotation marks ("), and at signs
(@).

Confirm RDS instance Requires input The password for the database instance associated with
password Informatica services and Tableau Server tasks. This must
(ConfirmRDSInstance match the password you entered for the RDS instance
Password) password parameter.

Enterprise Data Catalog Configuration:


Parameter label Default Description
(name)

Informatica Requires input The user name to access Informatica Administrator. This must
administrator be a 4-15 character string that starts with an uppercase or
lowercase letter and includes only alphanumeric characters
username
and underscores (_). The user name must not be
(InformaticaAdmin “administrator.”
Username)

Informatica Requires input The password to access Informatica Administrator. This must
administrator be a 5-64 character string that starts with an uppercase or
password lowercase letter and includes only alphanumeric characters
(InformaticaAdmin and underscores (_).
Password)

Confirm Informatica Requires input Password to access Informatica Administrator. This must
administrator match the password you entered for the Informatica
password administrator password parameter.
(ConfirmInformatica
AdminPassword)

Tableau Server Configuration:


Parameter label Default Description
(name)

Tableau Services admin The user name for the Tableau Services Manager (TSM)
Manager (TSM) administrator. This is a 3-30 character string that consists of
administrator alphanumeric characters and underscores (_). It must begin
username with an uppercase or lowercase letter. Do not use
(TableauManager Administrator or administrator as the user name.
Username)

Tableau Services Requires input The password for the Tableau Services Manager (TSM)
Manager (TSM) administrator. This is an 8-120 character string. It should
administrator contain at least one special character, one number, one

Page 21 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter label Default Description


(name)
password uppercase letter, and one lowercase letter. Double quotes (")
(TableauManager and dollar signs ($) are not allowed.
Password)

Tableau Server admin The user name of the initial administrator for Tableau Server.
administrator This is a 5-20 character string that begins with an uppercase
username or lowercase letter and contains only alphanumeric characters
(TableauServerAdmin and underscores (_).
User)

Tableau Server Requires input The password of the initial administrator for Tableau Server.
administrator This is an 8-120 character string. It should contain at least one
password special character, one number, one uppercase letter, and one
(TableauServerAdmin lowercase letter. Double quotes (") and dollar signs ($) are not
Password) allowed.

Tableau Server license Optional The license key for Tableau Server. For more information, see
key the Prerequisites section. Leave this parameter blank if you’re
(TableauServerLicense using a trial license.
Key)

AWS Quick Start Configuration:

Note Informatica recommends that you do not change the default values for the
parameters in this category.

Parameter label Default Description


(name)

Stack name <NONE> The name of the top-level (parent) stack. Keep the default
(RootStackName) setting if you’re launching the Quick Start in an existing VPC.

Quick Start S3 Bucket aws-quickstart- The S3 bucket name for the Quick Start assets. The bucket
Name informatica-tableau name can include numbers, lowercase letters, uppercase
(QSS3BucketName) letters, and hyphens (-), but should not start or end with a
hyphen. You can specify your own bucket if you copy all the
Quick Start assets and submodules into it. You might do this if
you want to customize the templates and override the Quick
Start behavior for your specific implementation.

Quick Start S3 Key quickstart- The S3 key prefix for your copy of Quick Start assets, if you
Prefix informatica- decide to customize or extend the Quick Start for your own
(QSS3KeyPrefix) tableau-analytics/ use. The key prefix can include numbers, lowercase letters,
uppercase letters, hyphens (-), and slash marks (/).

When you finish reviewing and customizing the parameters, choose Next.

Page 22 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

5. On the Options page, you can specify tags (key-value pairs) for resources in your stack
and set advanced options. When you’re done, choose Next.
6. On the Review page, review and confirm the template settings. Under Capabilities,
select the check box to acknowledge that the template will create IAM resources.
7. Choose Create to deploy the stack.

Step 4. Monitor the Deployment


During deployment, you can monitor the creation of the cluster instance and the
Informatica domain, and get more information about system resources.
1. Choose the stack that you are creating, and then choose the Events tab to monitor the
creation of the stack.
Figure 3 shows part of the Events tab.

Figure 3: Monitoring the deployment in the Events tab

When stack creation is complete, the Status field shows CREATE_COMPLETE, and
the console displays a list of stacks that have been created, as shown in
Figure 4.

Page 23 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Figure 4: Stacks created

2. Choose the Outputs tab.


When the Informatica domain setup is complete, the Outputs tab displays the
following information:
Key Description

EDCCatalogURL URL for the Informatica EDC user console

InstanceID Informatica domain host name

InformaticaAdminConsoleURL URL for the Informatica administrator console

EtcHostFileEntry Etc host file entry to be added to the /etc/hosts file to


enable access to the domain, using the host name of the
Administrative Server

EDCAdminURL URL for the EDC Administrator

CloudFormationLogs Location of the AWS CloudFormation installation log

S3DatalakeBucketName Name of the S3 bucket used for the data lake

InstanceSetupLogs Location of the setup log for the Informatica domain EC2
instance

InformaticaHadoopInstallLogs Location of the master node Hadoop installation log

InformaticaDomainPrivateDNSName Private DNS name of the Informatica domain EC2


instances

InformaticaPublicDNSName Public DNS name of the Informatica domain EC2


instances

InformaticaDomainDatabaseEndPoint Informatica domain database endpoint

InformaticaAdminConsoleServerLogs Location of the Informatica domain installation log

Page 24 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Note If the Outputs tab is not populated with this information, wait for domain
setup to be complete.

3. Use the links in the Outputs tab for the main stack to access management tools, as
described in the next section.

Figure 5: Outputs tab for main stack

Step 5: Test the Deployment


To test the deployment, access each resource created by the Quick Start by using the URLs
provided in the Outputs tab. To log in to each service, use the user name and password you
entered during deployment.

Use To

InformaticaAdminConsoleURL Open the Instance Administration screen. You can


use this screen to manage Informatica services and
resources. You can also get additional information about
the instance, such as the public DNS and public IP
address.

EDCAdminURL Administer the Informatica EDC environment.

EDCCatalogURL Access Information EDC. See the Enterprise Data Catalog


User Guide on the Informatica website for information
about logging in to Enterprise Data Catalog.

TableauServerURL Access Tableau Server.

Page 25 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Note All Informatica service endpoint URLs are SSL-enabled using self-signed
certificates. Depending on your browser choice, you may get a warning. Ignore the
warning and proceed. For example, in Chrome, choose Advanced, and then choose
Proceed to <URL> (Unsafe).

1. Use the URL to access the EDC catalog and log in by using your user name and
password. You should see 13660 assets scanned from 11 resources, as shown in Figure 6.

Figure 6: EDC home page

Choose the resources link to view information about the transformations created
during deployment.
2. Use the URL to access Tableau Server. Choose the Default project, and then choose
Informatica, Demographics – RDS & Redshift. Figure 7 shows the Content page
on Tableau Server.

Page 26 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Figure 7: Demographics information on Tableau Server

3. Use the URL to access Informatica Intelligent Cloud Services. Choose Data
Integration to launch the Data Integration service, and then choose Explore,
Default. The Default project contains the mappings and mapping tasks created during
deployment.

Figure 8: Default project folder in Data Integration

Page 27 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

4. Choose My Jobs. The My Jobs page shows the jobs that were run during
deployment.

Optional: Using Your Own Dataset


The Quick Start uses a sample dataset that you can replace with your own data. The sample
dataset is stored in a new S3 bucket that is created as part of the deployment. To use your
own dataset, prepare your on-premises or cloud data and use Informatica Intelligent Cloud
Services to upload your data to Amazon Redshift or to the S3 bucket. You can find the name
of the S3 bucket in the Outputs tab with the key S3DatalakeBucketName.

There are no specific data format requirements; for more information, see the Informatica
Cloud Data Integration documentation.

Optional: Adding VPC Definitions


When you launch the Quick Start in the mode where a new VPC is created, the Quick Start
uses VPC parameters that are defined in a mapping within the Quick Start templates. If you
choose to download the templates from the GitHub repository, you can add new named
VPC definitions to the mapping, and choose one of the named VPC definitions that you
have defined when you launch the Quick Start.

The following table shows the parameters defined within the default VPC definition
(QuickstartDefault). You can define as many VPC definitions as you need within your
environments. When you deploy the Quick Start, use the VPC definition parameter to
specify the configuration you want to use.

Parameter Default Description

CreateAdditional false Set to true to create a network ACL-protected subnet in each


PrivateSubnets Availability Zone. If false, the CIDR parameters for those
subnets will be ignored.

NATInstanceType t2.small The EC2 instance type for the NAT instances. This parameter is
used only if the AWS Region doesn’t support NAT gateways.

NumberOfAZs 2 The number of Availability Zones to use in the VPC.

PrivateSubnet1A 10.0.0.0/19 The CIDR block for private subnet 1A located in Availability
CIDR Zone 1.

PrivateSubnet1B 10.0.192.0/21 The CIDR block for private subnet 1B with dedicated network
CIDR ACL located in Availability Zone 1.

PrivateSubnet2A 10.0.32.0/19 The CIDR block for private subnet 2A located in Availability
CIDR Zone 2.

Page 28 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Parameter Default Description

PrivateSubnet2B 10.0.200.0/21 The CIDR block for private subnet 2B with dedicated network
CIDR ACL located in Availability Zone 2.

PrivateSubnet3A 10.0.64.0/19 The CIDR block for private subnet 3A located in Availability
CIDR Zone 3.

PrivateSubnet3B 10.0.208.0/21 The CIDR block for private subnet 3B with dedicated network
CIDR ACL located in Availability Zone 3.

PrivateSubnet4A 10.0.96.0/19 The CIDR block for private subnet 4A located in Availability
CIDR Zone 4.

PrivateSubnet4B 10.0.216.0/21 The CIDR block for private subnet 4B with dedicated network
CIDR ACL located in Availability Zone 4.

PublicSubnet1 10.0.128.0/20 The CIDR block for the public (DMZ) subnet 1 located in
CIDR Availability Zone 1.

PublicSubnet2 10.0.144.0/20 The CIDR block for the public (DMZ) subnet 2 located in
CIDR Availability Zone 2.

PublicSubnet3 10.0.160.0/20 The CIDR block for the public (DMZ) subnet 3 located in
CIDR Availability Zone 3.

PublicSubnet4 10.0.176.0/20 The CIDR block for the public (DMZ) subnet 4 located in
CIDR Availability Zone 4.

VPCCIDR 10.0.0.0/16 The CIDR block for the VPC.

Best Practices
Using Cloud Analytics Modernization on AWS
Now that you have tested the deployment, you can use the following links to get detailed
information about using the services deployed in this Quick Start.
 Data integration user guide (Informatica website)
 Administrator user guide (Informatica website)
 Enterprise Data Catalog user guide (Informatica website)
 Tableau Services Manager Overview (Tableau website)

Add a custom TCP rule for port 8044 on the Hadoop node. Enterprise Data Catalog uses
port 8044 for the log location URL.

For information about using this Quick Start after deployment, see:
 Cloud Analytics Modernization on the AWS Cloud User Guide (Informatica website)

Page 29 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Manual Cleanup
When you have finished using the AWS environment built by this Quick Start, delete the
resources to stop incurring AWS charges. To delete the resources, follow these steps:
1. Delete the AWS CloudFormation stack. In the AWS CloudFormation console, choose the
main stack name, and then choose Actions, Delete Stack.

Figure 9: Stack deletion process

2. In the Amazon S3 console, choose the S3 bucket located at stack-name-s3bucketstack-


auto-generated-unique-string, and delete the EDC installation, Hadoop cluster,
Tableau cluster, Oracle table and database, and Amazon Redshift files in the bucket.
3. If you used an existing Informatica Intelligent Cloud Services organization, delete the S3
to Redshift_ITQS and Aggregate Store Sales_ITQS mappings and mapping tasks from
the Default project folder in Data Integration:

a. Select the checkbox to the left of the mapping tasks. From the dropdown menu,
choose Delete.

Page 30 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Figure 10: Mapping task deletion

b. Delete the mappings.


4. Navigate to the Informatica Administrator console. Choose Connections in the
navigation pane to delete the following connections:
- AWS Oracle Quick Start_ITQS
- AWS Redshift Quick Start_ITQS
- AWS S3 Quick Start_ITQS
- AWS Tableau Quick Start_ITQS
To delete the connections, choose the trash bin icon to the left of each connection.

Figure 11: Connections page in Administrator

Page 31 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Troubleshooting
Q. I encountered a CREATE_FAILED error when I launched the Quick Start.
A. If you encounter this error in the AWS CloudFormation console, we recommend that you
relaunch the template with Rollback on failure set to No. (This setting is under
Advanced in the AWS CloudFormation console, Options page.) With this setting, the
stack’s state will be retained and the instance will be left running, so you can troubleshoot
the issue. (You'll want to look at the log files in %ProgramFiles%\Amazon\EC2ConfigService
and C:\cfn\log.)

Important When you set Rollback on failure to No, you’ll continue to


incur AWS charges for this stack. Please make sure to delete the stack when
you’ve finished troubleshooting.

For additional information, see Troubleshooting AWS CloudFormation on the AWS


website.

Q. I encountered an error while installing Informatica domain and services.


A. We recommend that you view the /installation.log log file to get more information
about the errors you encountered.

Q. I encountered a size limitation error when I deployed the AWS Cloudformation


templates.
A. We recommend that you launch the Quick Start templates from the location we have
provided or from another S3 bucket. If you deploy the templates from a local copy on your
computer or from a non-S3 location, you might encounter template size limitations when
you create the stack. For more information about AWS CloudFormation limits, see the AWS
documentation.

Q. I encountered an address limit error when I launched Amazon EC2.


A. Make sure that you are registered and the required licenses are assigned to your
Informatica Intelligent Cloud Services account before launching the Quick Start.

Q. I encountered an AWS CloudFormation script rollback within minutes of launch.


A. Your user account might not have the required connector licenses, or your Informatica
account might already have mappings and connections with an _ITQS suffix. We
recommend that you add the required connector licenses if you are using your existing
Informatica account. Remove all mappings and connections that have the _ITQS suffix if
you are reusing the same Informatica account in AWS CloudFormation.

Page 32 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Q. The Tableau artifacts created by the Quick Start don’t appear.


A. You have exceeded your daily limit of 1,000,000 job rows. This error will be visible in
the Informatica Intelligent Cloud Services console as the Mapping Configuration Tasks
(MCTs) fail. We recommend that you use a valid Informatica account that has no upper
limit on transaction rows.

Q. I am in São Paulo and NAT Gateway is not available in my Availability Zone.


A. Supported Availability Zones for creating NAT gateways are sa-east-1a and sa-east-
1c. For the Availability Zones parameter, choose sa-east-1a and sa-east-1c, not sa-
east-1b, from the list.

Q. The stack creation completed successfully but Tableau visualization is empty.


A. If you have subscribed to multiple services and connectors from Informatica Intelligent
Cloud Services, mapping tasks might fail to load required sample data into Amazon
Redshift and the Oracle database used for Tableau visualization. Follow the instructions in
the Informatica Knowledge Base to increase the Java heap space, and rerun the mappings.

Q. I encountered an “Internal Failures” error during launch.


A. Internal failures might occur when the AWS CloudFormation service experiences
increased error rates across all stacks. Try launching the Quick Start in another region or at
another time. If the issue persists, contact AWS Support.

Q. The Tableau Server stack fails with Tableau license expiration.


A. The 14-day trial license for Tableau Server associated with your email address has
expired. Use a unique email address or contact Tableau Support.

Q. The Lambda stack fails although Informatica connections, mappings, and license are
present.
A. The Lambda stack will fail if Informatica connections are already present. We
recommend that you delete any duplicate connections in your Informatica Intelligent Cloud
Services environment and try again.

Q. Can I provision the instances for high availability and disaster recovery?
A. Yes, you can configure alarms by using Amazon CloudWatch, and recovery actions could
be triggered in case of a system crash. For details and how-to steps, see the AWS
documentation.

Page 33 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Additional Resources
AWS services
 AWS CloudFormation
http://aws.amazon.com/documentation/cloudformation/
 Amazon EC2
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/
 Amazon Redshift
https://aws.amazon.com/documentation/redshift/
 Amazon S3
https://aws.amazon.com/documentation/s3/
 Amazon VPC
http://aws.amazon.com/documentation/vpc/

Informatica
 Informatica for AWS Network Community (a source for product documentation,
Knowledge Base articles, and other information)
https://network.informatica.com/community/informatica-network/products/cloud-
integration/cloud-for-amazon-aws/overview/

Tableau
 Tableau Desktop
http://www.tableau.com/products/desktop

 Tableau Server
http://www.tableau.com/products/server

 Designing Efficient Workbooks whitepaper


https://www.tableau.com/learn/whitepapers/designing-efficient-workbooks

Quick Start reference deployments


 AWS Quick Start home page
https://aws.amazon.com/quickstart/

GitHub Repository
You can visit our GitHub repository to download the templates and scripts for this Quick
Start, to post your comments, and to share your customizations with others.

Page 34 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018

Document Revisions
Date Change In sections

November 2018 Initial publication —

© 2018, Amazon Web Services, Inc. or its affiliates, Informatica LLC, and Tableau
Software. All rights reserved.

Notices

This document is provided for informational purposes only. It represents AWS’s current product offerings
and practices as of the date of issue of this document, which are subject to change without notice. Customers
are responsible for making their own independent assessment of the information in this document and any
use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether
express or implied. This document does not create any warranties, representations, contractual
commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities
and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of,
nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, Version 2.0 (the "License"). You
may not use this file except in compliance with the License. A copy of the License is located at
http://aws.amazon.com/apache2.0/ or in the "license" file accompanying this file. This code is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.

Page 35 of 35

Você também pode gostar