Skip to main content

How to Generate and Use AWS Secret Keys

This section will guide you through the process required for creating a AWS SecretAccessKey and SecretKey and assigning the correct permissions to it.

Creating an AWS Secret Key with Credentials​

Many features in Nocodo rely on secure integration with AWS services. To facilitate this, you'll need an AWS Secret Key with credentials. This allows Nocodo to interact securely with your AWS resources.

Follow these steps to create an AWS Secret Key with credentials:

  1. Sign in to the AWS Management Console
    Go to AWS Management Console and sign in with your AWS account credentials. If you do not have an AWS account, you'll need to create one.

  2. Navigate to the IAM (Identity and Access Management) Service
    In the AWS Management Console, search for and select "IAM" from the services menu. This will take you to the IAM dashboard.

  3. Create a New IAM User

    • On the IAM dashboard, click on "Users" in the sidebar, then select "Create user" Screenshot of the 'Create user' page in AWS IAM. 'Step 1: Specify user details' is highlighted. The 'User name' field is filled with 'nocodo-test-user'. A checkbox for 'Provide user access to the AWS Management Console' is available. A blue information box provides additional details. 'Cancel' and 'Next' buttons are at the bottom right.
    • Enter a user name (e.g., "nocodo-test-user").

  4. Set Permissions for the User

    • Click "Next" aws-

      The image shows the 'Set permissions' step in the 'Create user' process within the AWS IAM console. Options include 'Add user to group', 'Copy permissions', and 'Attach policies directly'. 'Permissions policies' section shows 'AmazonS3FullAccess' selected. 'Next' and 'Previous' buttons are at the bottom.

    • You can attach existing policies directly, add the user to a group with appropriate permissions, or create a custom policy. For a basic setup, you might choose "Attach existing policies directly" and select "AmazonS3FullAccess" (or any other specific permissions Nocodo might require).

    • Click "Next" to add any optional tags.

  5. Review and Create User

    • Review the user details and permissions.
    • Click "Create user."

  6. Download the Credentials

    • Once the user is created, you'll see an option to 'Create access key' in the Summary section of the user. Screenshot of the 'Create access key' page in AWS IAM. It shows options for access key use cases: Command Line Interface (CLI), Local code, Application running on an AWS compute service, Third-party service (selected), Application running outside AWS, and Other. A warning suggests using IAM roles instead of long-term access keys. There is a confirmation checkbox and 'Next' and 'Cancel' buttons.
    • Select the Use Case for the Access Key. Select 'Third-party service' and confirm that you understood the recommendations.
    • In the next step add some tags or directly create the access key. A screenshot of the 'Retrieve access keys' page in AWS IAM. It shows an Access key with the ID 'AKIA4VJKECKJKI4IBHVK' and a masked Secret access key. Below, access key best practices are listed: never store keys in plain text, disable or delete when not needed, enable least-privilege permissions, and rotate keys regularly. Buttons for downloading a .csv file and marking the process as done are at the bottom.
    • In the following screen you are able to download the .csv file containing the Access Key ID and Secret Access Key. Download and securely store this file. This is the only time you will be able to view the Secret Access Key.

  7. Configure AWS Credentials in Nocodo

    • With the credentials downloaded, you can now configure them in Nocodo. Follow the specific instructions in the Nocodo documentation to input these credentials into the system.
danger

Important Security Note:
Keep your AWS Access Key ID and Secret Access Key secure. Only share them with trusted Persons or Applications. Rotate your keys regularly and delete any keys that are no longer needed. Nocodo AI stores your Credentials securely. The only way they can be accessed is when you execute your projects.