Create and configure AWS resources to connect to the serverless runtime
environment.
Create and configure the following AWS resources:
VPC
A VPC is a virtual network that contains other AWS resources. You can use an
existing VPC or create a VPC using the following guidelines:
Use IPv4 CIDR manual
input and enter the CIDR block for the VPC to use.
Make sure that
enableDnsSupport and enableDnsHostnames are set to true.
Subnet
A subnet in the VPC connects to the data sources. You can use an existing public
or private subnet, or you can create a subnet using the following guidelines:
Use any availability zone
in the region where you created the VPC.
To set the IPv4 VPC CIDR
block, use the same IPv4 CIDR block that you specified when you created
the VPC.
To set the IPv4 subnet
CIDR block, use a CIDR range that's within the VPC CIDR range. For
example, if you use 10.1.0.0/16 for the VPC, you might use 10.1.240.0/20
for the subnet.
Security group for the resource gateway
The resource gateway uses a security group to allow all inbound traffic from the
same security group. The following image shows the inbound rule in the security
group:
You use this security group
to create the serverless runtime environment in
Administrator
.
Resource gateway
A resource gateway in Amazon VPC Lattice is an entry point into the VPC that
allows access to data sources. It routes traffic to the data sources that you
want the serverless runtime environment to access.
To create the resource
gateway, use the following guidelines:
Use your existing VPC or
the VPC that you created.
Select an existing subnet
or the subnet that you created.
Use the same availability
zone that the subnet uses.
Use the security group
that you created for the resource gateway.
The following image shows an example of a resource gateway:
Resource configuration
A resource configuration in Amazon VPC Lattice is a logical representation of a
data source like an Amazon S3 bucket or Snowflake database. The serverless
runtime environment first connects to the resource configuration to connect to
the data source.
Create a resource configuration for each data source that you
want the serverless runtime environment to access. To create a resource
configuration, use the following guidelines:
Use the
Resource
configuration type and set it to
Single
to create the resource
configuration for a single resource.
Use the resource
gateway that you created.
For data sources that
aren't Amazon EFS, use
DNS resource
as the
resource definition and specify the public DNS name, such as
serverless-private.s3.us-west-2.amazonaws.com
or
serverless.snowflakecomputing.com
.
For an Amazon EFS
data source, use
IP resource
as the resource
definition and use
IPv4
as the IP address
type. Then, specify the private IP address.
The following image shows an example of a resource configuration:
Resource share
A resource share in AWS Resource Access Manager is a logical group that allows
you to share resource configurations with Informatica.
To create the resource
share, use the following guidelines:
To specify the resource
share details, complete the following tasks:
Use
VPC Lattice Resource Configurations
as the resource type.
Select all the
resource configurations that you want to add to the resource
share.
Make sure you add all of the resource configurations as
part of this step. After you create a serverless runtime
environment in
Administrator
, you can update the resource share
only by creating a new serverless runtime
environment.
To grant access to
Informatica as a principal, complete the following tasks:
Allow sharing
with anyone.
Use the
AWS account
principal type and add
Informatica's AWS account number as a principal.
To find
Informatica's AWS account number, create a serverless
runtime environment in
Administrator
and copy the number from the
Informatica Account Number
property.
The following image shows an example of a resource share:
After you create the resource share, AWS sends a resource share invite to
Informatica and the status of the resource share is
Associating
. When you create the serverless
runtime environment, the environment accepts the resource share and the
status changes to
Associated
.
If you don't create the serverless runtime environment within a certain
amount of time, the invite expires. You'll need to edit the resource share
and re-add Informatica as a principal so that AWS sends a new resource share
invite.
ASK INFAPreview
