Work Instruction | How to Create AWS Credentials on a Glide Instance - Product Knowledge

Work Instruction | How to Create AWS Credentials on a Glide Instance Overview This article provides clear, step-by-step instructions for creating AWS credentials on a Glide instance. Use these credentials to connect your Glide instance securely to AWS services. Each step is illustrated with a screenshot to make the process easy to follow.

Dependencies An active AWS account with permissions to create IAM users, groups, and policies. Access to your Glide instance with administrator privileges. Instructions Follow the steps to create your AWS access, secret key, and set up AWS credentials on the glide instance.

Step 1: Log In to the AWS Management Console Go to the AWS Management Console and sign in with your AWS credentials.

Login to the aws console for e.g. https://us-east-1.console.aws.amazon.com/ Enter your AWS credentials and password. Step 2: Navigate to IAM (Identity and Access Management) From the AWS Console home page, search for “IAM” in the search bar and select IAM from the results.

Step 3: Create a New IAM User In the IAM dashboard, click on Users in the left sidebar. Click the Create user button. Enter a username (e.g., glide-aws-user). Step 4: Set Permissions & Policies On the Permission screen, click Create Group. Enter a new group name, e.g. "MID_Trace_Collector_Group". Create a customer-managed policy scoped to the CloudWatch Logs actions the MID trace collector uses, then attach that policy to the group: Policy name: MIDTraceCollectorLogsAccess

{ "Version": "2012-10-17", "Statement": [ { "Sid": "DiscoverLogGroups", "Effect": "Allow", "Action": "logs:DescribeLogGroups", "Resource": "*" }, { "Sid": "ReadAndQueryLogGroups", "Effect": "Allow", "Action": [ "logs:FilterLogEvents", "logs:StartQuery", "logs:GetQueryResults", "logs:StopQuery" ], "Resource": "arn:aws:logs:*: :log-group:*" } ] }

Replace with your AWS account ID. The region is wildcarded so this covers every region in your account without listing each one. logs:DescribeLogGroups can't be scoped to specific log groups — CloudWatch Logs has no name filter for it, and it's how the collector discovers log groups dynamically, so it stays Resource: "*". The other four actions are restricted to log groups in your account only. This group grants read/query access only — no write, delete, or Bedrock permissions.

Click Next. Go ahead and create the group. Step 5: Review and Create User Review the user details and permissions, then click Create user to finish.

Once the user is created, you’ll see a success banner. Step 6: Create Access Key Navigate back to the IAM -> Users and select the user just created in previous step. Click on the security credentials tab. Under security credentials -> create access key

Under access key best practices select third party service

Provide option description tag. Proceed to create the access key.

Download the .csv file containing the Access key ID and Secret access key Store these credentials securely! (You will not be able to view the secret access key again.) Step 7: Add AWS Credentials to Your Glide Instance Log in to your Glide instance as an administrator. Make sure you change the application scope to “AI Trace Collector”.

Navigate to the Connection & Credential Aliases page (sys_alias) and create a new record. https://{instance_name}.service-now.com/sys_alias_list.do . Set the Type field to credentials.

Provide the credentials alias name. Make sure the application scope is set to "AI Trace Collector. The ID will be generated on saving the form. Step 8. Create AWS Credentials with Access & Security Key Navigate to https://{instance_name}.service-now.com/discovery_credentials_list.do Select AWS Credentials from the list.

In the subsequent aws credentials form fill out the details.

Name: (Any name) Access key ID:(Access ID you downloaded in step 6.) Secret Access Key:(Secret access key you downloaded in step 6.) Step 9. Link AWS Credentials to Access & Security Key Select the credentials alias linking icon (lock button). Search for the credentials alias to link using the search icon. From the connection & credentials aliases screen select the alias you created in step 7.

Save your changes. Conclusion You have successfully created AWS credentials and added them to your Glide instance. Your Glide application can now securely connect to AWS services using these credentials. For enhanced security, consider using IAM roles and limiting permissions to only what is necessary for your application.

Troubleshooting & Tips If you lose the secret access key, you will need to create a new access key in AWS IAM. Rotate access keys regularly and remove unused credentials. Ensure your IAM user has only the permissions it needs to reduce security risks.