Deploy the Informatica® Data Engineering Integration Solution on the AWS Cloud Marketplace (10.4.1)

Deploy the Informatica® Data Engineering Integration Solution on the AWS Cloud Marketplace (10.4.1)

Architecture

Architecture

When you deploy the
Data Engineering Integration
solution on a new Virtual Private Cloud (VPC) with the default parameters, the deployment builds the following
Data Engineering Integration
environment on the AWS Marketplace:
  • Informatica domain on an EC2 instance, with additional instances to contain nodes in the Data Integration Service grid
  • Informatica clients on a remote Windows bastion server, on a public subnet
  • Amazon S3 storage resources and connections for source and target data in existing S3 buckets
  • Amazon RDS relational databases for Informatica domain repositories
  • AWS security and account management services
  • Lambda functions
The following image shows the architecture of
Data Engineering Integration
on AWS Marketplace:
The numbers in the architecture diagram correspond to items in the following list:
  1. A virtual public cloud (VPC) configured across two Availability Zones to contain the
    Data Engineering Integration
    deployment.
  2. Availability zones. For each Availability Zone, this deployment provisions one private and one public subnet.
  3. Subnets to contain specific elements of the deployment. Creates two private subnets, plus one public subnet if you want to use a Windows bastion server for Informatica clients. Creates each of the subnets in a different availability zone.
  4. The Informatica domain, including the Model Repository Service and the Data Integration Service.
  5. Oracle database to contain the following Informatica repositories:
    • Domain configuration repository
    • Model repository, 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.
  6. S3 storage, to act as a location for the license key.
  7. AWS Lambda functions.
  8. IAM roles.
  9. Amazon CloudWatch.
  10. Informatica clients in a separate EC2 bastion server in a public subnet.

0 COMMENTS

We’d like to hear from you!