1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
There are two types of connectors, well technically three:
- Built-in connectors
- Custom connectors (supplied by AppFlow Partners)
- Custom connectors (built and controlled by you)
These are also separated by Source and Destination, whether you're pushing or pulling information from the connector.
While Built-in connectors are currently supported as separate CloudFormation resources/properties with pre-defined fields, Custom connectors do not have this capability as any field may be available.
However, there are two CloudFormation resources you should be able to use for custom connectors CustomConnectorDestinationProperties
and CustomConnectorSourceProperties
. The configurations for these will vary for each connector and at this time I do not have the specific parameters for Google Ads, but through some tinkering you may be able to make this work.
Relevant content
- asked 7 months ago
- asked 4 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
Thank Chris. Ok, so this makes sense and can be created programmatically.
Is there a way to embed AppFlow for multiple users outside of aws account? Kinda like a SaaS app, where a user would grant access to their google account and AppFlow get authorization.
Kinda like described in dev guide https://github.com/awslabs/aws-appflow-custom-connector-python
Hi Roman, I am not sure unfortunately.