Skip to content

Setting up Neptune credentials in AWS Secrets#

This guide shows how to store your Neptune credentials in AWS Secrets. This lets you smoothly use the Neptune client library with Amazon SageMaker.

About AWS secrets

AWS Secrets Manager is a secure way to share sensitive information across AWS services. The secrets are encrypted and access to them is controlled by access policies. It's like using a password manager that stores your password in an encrypted form and pastes it to website forms when needed.

Before you start#

  • Set up your Neptune project, where the runs and metadata will go: Creating a Neptune project
  • (optional) Instead of using a Neptune user account, you can create a service account for use in automated pipelines.

Creating the AWS secret#

To store your Neptune information in an AWS secret:

  1. In AWS Secrets Manager, navigate to Secrets.
  2. Click Store new secret.
  3. Under Secret type, select Other type of secret.
  4. Under Key/value pairs, add the following entries:

    Key Value
    api-token The Neptune API token of your account
    project The name of your Neptune project
    How do I find my API token?

    In the top-right corner of the Neptune app, click your avatar and select Get your API token.

    You can copy your token from the dialog that opens. It's very long – make sure to copy and paste it in full!

    How do I find my project name?

    Your full project name has the form workspace-name/project-name.

    For example, if your workspace name (shown in the top-left corner) is "ml-team" and your project is named "classification", your project string is: "ml-team/classification".

    To copy the name in Neptune, navigate to your projectSettingsProperties.

  5. Click Next to continue.

  6. In the Configure secret step, under Secret name and description, enter a secret name starting with AmazonSageMaker-.
  7. Optionally enter more information about the secret, then click Next and leave the default settings.

Accessing the AWS secret#

The SageMaker resource that needs access to the secret must have the following permissions:

  • secretsmanager:ListSecrets
  • secretsmanager:GetSecretValue

The default AmazonSageMakerFullAccess policy used in SageMaker services does have these permissions. The relevant part of the policy looks like this:

{
    "Effect": "Allow",
    "Action": [
        ...
        "secretsmanager:ListSecrets",
        ...
    ],
    "Resource": "*"
},
{
    "Effect": "Allow",
    "Action": [
        "secretsmanager:DescribeSecret",
        "secretsmanager:GetSecretValue",
        "secretsmanager:CreateSecret"
    ],
    "Resource": [
        "arn:aws:secretsmanager:*:*:secret:AmazonSageMaker-*"
    ]
},

With the Neptune–AWS integration#

To access the secrets from your code (such as a notebook or training script):

  1. Install the neptune-aws integration package.
  2. Initialize Neptune with the following:

    from neptune.new.integrations.aws import init_run 
    
    run = init_run(
        secret="neptune-secret",  # Use your secret name here
        region="us-west-1",  # Use the appropriate region here
    )
    

Without the integration#

To access the secrets from your code without the Neptune–AWS integration, you can also use the following code:

import boto3
from botocore.exceptions import ClientError
import json

secret_name = "AmazonSageMaker-name-of-your-secret"
region_name = "eu-west-1"

# Create a Secrets Manager client
session = boto3.session.Session()
client = session.client(
    service_name="secretsmanager",
    region_name=region_name
)

get_secret_value_response = client.get_secret_value(
    SecretId=secret_name
)

json.loads(get_secret_value_response["SecretString"])  #(1)!
  1. Dictionary containing the saved secrets.