Deploy PowerCenter on the AWS Cloud Marketplace (10.5.1)

Deploy PowerCenter on the AWS Cloud Marketplace (10.5.1)

Option 1. Deploy into a new VPC

Option 1. Deploy into a new VPC

Specify the identifiers for the VPC, for the subnet containing the Amazon EC2 instances where the deployment process deploys the application components, and for the subnets used by the Informatica services. The deployment process provisions the application components and creates the required repository databases based on the values you specify.
  1. Enter the name of the stack to create. The stack name can include letters (A-Z and a-z), numbers (0-9), and dashes (-).
  2. Enter the parameters required to deploy the application.
    The following table lists the parameters in the
    Network Configuration
    section:
    Parameter
    Default
    Description
    Availability Zones
    Requires input
    The list of Availability Zones to use for the subnets in the VPC. Make sure that you select two zones.
    VPC CIDR
    10.0.0.0/16
    Classless Inter-Domain Routing IP address range associated with the Amazon VPC.
    The CIDR range must have permissions to access the public subnet where the application runs.
    Format the string as
    <IP address>/<IP network prefix>
    . For example, to specify a range from
    10.20.30.40
    to
    10.20.30.47
    , enter
    10.20.30.40/29
    .
    Public Subnet CIDR
    Requires input
    CIDR block for the public subnet. Ensure that you include the subnet in the VPC CIDR.
    Private Subnet 1 CIDR
    10.0.0.0/19
    CIDR block for the private subnet 1. Ensure that you include the subnet in the VPC CIDR.
    Private Subnet 2 CIDR
    10.0.32.0/19
    CIDR block for the private subnet 2. Ensure that you include the subnet in the VPC CIDR.
    CIDR IP Range
    Requires input
    The CIDR IP range that is permitted to access
    PowerCenter
    .
    To reduce the potential of inbound attacks from unknown IP addresses, you can use a constrained CIDR range to reduce. For example, to specify the range of 10.20.30.40 to 10.20.30.47, enter 10.20.30.40/29.
    The following table lists the parameters in the
    Bastion Server for Informatica
    section:
    Parameter
    Default
    Description
    Deploy Bastion Server
    Requires input
    Select
    Yes
    to deploy a bastion server to access other resources in the VPC.
    The following table lists the parameters in the
    Amazon EC2 Configuration
    section:
    Parameter label (name)
    Default
    Description
    Key Pair Name
    Requires input
    Name of an existing Amazon EC2 key pair to enable SSH and Remote Desktop Protocol (RDP) access to
    PowerCenter
    .
    Keypair S3 URI
    Requires input
    S3 Bucket URI for the keypair selected. Use the following format:
    s3://bucket-name/Keypair.pem
    or
    s3://bucket-name/sub-folder/Keypair.pem
    The option is available only for Linux deployments.
    The following table lists the parameters in the Amazon Elastic File System (EFS) Configuration (applicable only on Linux deployments):
    Parameter
    Default
    Description
    EFS Creation
    No
    Select Yes to create an Amazon Elastic File System.
    The following table lists the parameters in the
    Informatica PowerCenter
    section:
    Parameter label (name)
    Default
    Description
    License Key S3 Bucket URI
    Requires input
    The S3 bucket URI for the
    PowerCenter
    license key in the following format:
    s3://<bucket-name>/<directory>/<license key>
    Database Type
    Oracle
    Select the database type for the Informatica repository and services. Choose Oracle or Microsoft SQL Server.
    High Availability Deployment
    Requires input
    Enable or disable high availability for the deployment.
    For information about high availability for the Informatica domain, see the Informatica documentation.
    Number of PowerCenter Nodes
    Requires input
    Select the number of nodes that you need to run PowerCenter.
    Use S3 files
    No
    Use configuration files stored on an Informatica-owned S3 bucket. Selecting Yes downloads configuration files and then configures. May contain latest fixes if any, else the deployment uses local configuration files stored in the EC2 instance.
  3. Click
    Next
    .
  4. On the Options page, expand the
    Advanced
    tab.
  5. Set the
    Rollback on Failure
    property to
    No
    .
  6. Click
    Next
    .
  7. Click
    Create
    .
  8. When the status for the stack reads CREATE_COMPLETE, click the stack name.

0 COMMENTS

We’d like to hear from you!