Configuring Oracle NetSuite connections
Oracle NetSuite supports the AUTHORIZATION_CODE grant type for OAuth2. The grant type determines how Amazon Glue communicates with Oracle NetSuite to request access to your data.
This grant type is considered "three-legged" OAuth as it relies on redirecting users to a third-party authorization server to authenticate the user. It is used when creating connections via the Amazon Glue console. The user creating a connection may by default rely on an Amazon Glue-owned connected app (Amazon Glue managed client application) where they do not need to provide any OAuth-related information except for their Oracle NetSuite instance URL. The Amazon Glue console will redirect the user to Oracle NetSuite where the user must login and allow Amazon Glue the requested permissions to access their Oracle NetSuite instance.
Users may still opt to create their own connected app in Oracle NetSuite and provide their own client id and client secret when creating connections through the Amazon Glue console. In this scenario, they will still be redirected to Oracle NetSuite to login and authorize Amazon 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 public Oracle NetSuite documentation on creating a connected app for Authorization Code OAuth flow, see Public apps
.
To configure a Oracle NetSuite connection:
In Amazon Secrets Manager, create a secret with the following details:
For the customer managed connected app, the Secret should contain the connected app Consumer Secret with
USER_MANAGED_CLIENT_APPLICATION_CLIENT_SECRET
as key.Note: You must create a secret for your connection in Amazon Glue.
In the Amazon Glue Data Catalog, create a connection by following the steps below:
When selecting a Connection type, select Oracle NetSuite.
Provide the Oracle NetSuite environment.
Select the Amazon IAM role which Amazon 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": "*" } ] }
Select the
secretName
which you want to use for this connection in Amazon Glue to put the tokens.Select the network options if you want to use your network.
Grant the IAM role associated with your Amazon Glue job permission to read
secretName
.In your Amazon Glue job configuration, provide
connectionName
as an Additional network connection.