Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Configuring Google Ads connections

Focus mode
Configuring Google Ads connections - AWS Glue

Google Ads supports AUTHORIZATION_CODE grant type for OAuth2.

This grant type is considered “three-legged” OAuth as it relies on redirecting users to the third party authorization server to authenticate the user. It is used when creating connections via the AWS Glue Console. The AWS Glue Console will redirect the user to Google Ads where the user must login and allow AWS Glue the requested permissions to access their Google Ads instance.

Users may opt to create their own connected app in Google Ads and provide their own client ID and client secret when creating connections through the AWS Glue Console. In this scenario, they will still be redirected to Google Ads to login and authorize AWS Glue to access their resources.

This grant type results in a refresh token and access token. The access token is short lived, and may be refreshed automatically without user interaction using the refresh token.

For more information, see public Google Ads documentation on creating a connected app for Authorization Code OAuth flow .

To configure a Google Ads connection:

  1. In AWS Secrets Manager, create a secret with the following details. It is required to create a secret for each connection in AWS Glue.

    1. For AuthorizationCode grant type:

      • For customer managed connected app – Secret should contain the connected app Consumer Secret with USER_MANAGED_CLIENT_APPLICATION_CLIENT_SECRET as key.

  2. In AWS Glue Glue Studio, create a connection under Data Connections by following the steps below:

    1. When selecting a Connection type, select Google Ads.

    2. Provide the developer token of the Google Ads you want to connect to.

    3. Provide the MANAGER ID of the Google Ads if you want to log in as manager.

    4. Select the IAM role which AWS Glue can assume and has permissions for following actions:

      { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "secretsmanager:DescribeSecret", "secretsmanager:GetSecretValue", "secretsmanager:PutSecretValue", "ec2:CreateNetworkInterface", "ec2:DescribeNetworkInterface", "ec2:DeleteNetworkInterface", ], "Resource": "*" } ] }
    5. Select the secretName which you want to use for this connection in AWS Glue to put the tokens.

    6. Select the network options if you want to use your network.

  3. Grant the IAM role associated with your AWS Glue job permission to read secretName.

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.