Escolar Documentos
Profissional Documentos
Cultura Documentos
November 2018
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
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.
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.
Page 3 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018
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 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.
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.
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
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
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.
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.
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.
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
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.
Page 12 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018
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
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.
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.).
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
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.
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.
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.
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
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)
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 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
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)
Note Informatica recommends that you do not change the default values for the
parameters in this category.
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
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
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.
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
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.
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 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
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)
Note Informatica recommends that you do not change the default values for the
parameters in this category.
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.
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
InstanceSetupLogs Location of the setup log for the Informatica domain EC2
instance
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.
Use To
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.
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
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.
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.
There are no specific data format requirements; for more information, see the Informatica
Cloud Data Integration documentation.
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.
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.
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
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.
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.
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
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.)
Page 32 of 35
Amazon Web Services – Cloud Analytics Modernization with Informatica and Tableau November 2018
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
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
© 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