Log on to the AWS marketplace site and select

Cloud Formation

Stacks

Create Stack

to begin the process of deploying the solution.

Populate the properties on the

Create Stack

page. The following sections describe the properties to populate.

In this section, specify a stack name for the solution on the AWS platform.

In this section, specify network parameters for the solution.

Several fields ask you to supply CIDR values. The CIDR (Classless Inter-Domain Routing) value represents a block of IP addresses. For example, to specify the range of 10.20.30.0 to 10.20.30.255, enter the following string:

10.20.30.40/24

Configuration of the private and public subnets depends on whether you want the automated deployment to create a remote Windows server with Informatica clients.

If you do not want the remote windows server, specify CIDR values for two private subnets and leave the value for the Public Subnet CIDR property blank.
If you want the remote Windows server, specify CIDR values for two private subnets and one public subnet.
For more information about the remote Windows server, see Informatica clients.

The following table describes values for parameters in the

Network Configuration

section:

Availability Zones	List of Availability Zones to use for the subnets in the VPC. List at least two zones. The solution prioritizes the zones in the order in which you list them.
VPC CIDR	CIDR block for the VPC to use for the deployment. To use existing resources, identify a VPC where existing resources reside. Verify that VPC peering is enabled.
Public Subnet CIDR	CIDR block for the optional public subnet.
Private Subnet 1 CIDR	CIDR block for one of two private subnets.
Private Subnet 2 CIDR	CIDR block for the second of two private subnets.
IP address range	CIDR IP address range that is permitted to access the Informatica domain.
Deploy a Remote Windows Server?	Choose from the following: No (default). Yes. The solution deploys a remote Windows server that can access other resources in the VPC. If you choose Yes, then choose service subnets which are not attached to an Internet gateway.

The following table describes values for parameters in the

Amazon EC2 Configuration

section:

Parameter	Description
Key pair name	Select an existing EC2 KeyPair name to enable SSH access for Informatica services to the EC2 instance.

In this section, specify parameters for the Amazon RDS relational database to host the Informatica domain. The following table describes values for parameters in this section:

Parameter	Description
Database password	Type a password for the domain repository database user. Retype this password in the next field.
Select MultiAZ deployment	Choose Yes to enable the database to be available in more than one availability zones, or No (default).

In this section, specify parameters for the Big Data Management domain. The following table describes values for parameters in this section:

Parameter	Description
Informatica administrator user name	Type a name for the Informatica domain administrator. In this field and the following field, you can specify any user name and password. Make a note of the user name and password, and use it later to log in to the Administrator tool to configure the Informatica domain.
Informatica administrator password	Type a password for the Informatica domain administrator. Retype this password in the next field.
Big Data Management License Key Location	Name of the Amazon S3 bucket in your account that contains the Informatica Enterprise Information Catalog Key. Use a bucket of the same region in which the stack is being launched.
Big Data Management License Key Name	Enter the subdirectory path, if any, and filename of the Big Data Management license key file located in the S3 bucket named in the property Big Data Management License Key Location . For example, where the entire path including the bucket name is S3BucketName/SubDir1/SubDir2/BDMLicense.key , type the following: SubDir1/SubDir2/BDMLicense.key

In this section, specify parameters for the Amazon EMR cluster. The following table describes values for parameters in this section:

Parameter	Description
EMR AutoDeploy	Choose Yes to enable autodeploy connections for the solution, or No (default) to create a new EMR cluster and connections.
EMR ID of EMR Cluster	ID of the existing EMR cluster to use in the solution. Choose <NONE> if you want to: Create a new EMR cluster for the solution Use cluster workflows (auto-deployment) to create ephemeral clusters for the solution Default: <NONE>

In this section, optionally specify parameters for a cluster for the Amazon Redshift data warehouse.

To create a new Redshift data warehouse, configure the parameters as follows:

Redshift Deploy Type = Required
Redshift Host =
<NONE>

To use an existing Redshift data warehouse, configure the parameters as follows:

Redshift Deploy Type = Required
Redshift Host =
<IP address of the existing Redshift cluster master node>

If you do not want to use a Redshift data warehouse with the deployed solution, choose:

Redshift Deploy Type = Skip

Then click

Next

to go to the next deployment step.

The following table describes values for parameters in this section:

Parameter	Description
Redshift Deploy Type	Choose from the following options: Required. Choose Required to create a Redshift data warehouse cluster. Skip. Choose Skip if you do not want to use an Amazon Redshift data warehouse.
Redshift Host	Choose from the following options: To use an existing Redshift cluster, type the DNS name or IP address of the master node of the existing Redshift cluster. To create a Redshift cluster, choose <NONE> . Default: <NONE>
Redshift user name	Type the username that is associated with the master user account for the Redshift cluster.
Redshift database name	Type a name for the Redshift data warehouse.
Redshift cluster password	Type a password for the Redshift cluster master user account.

After you finish entering values for the parameters, click

Next

.

AWS begins provisioning resources according to the values you entered.