Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Not Found
English

Page Not Found

The page or file you are looking for has been moved or no longer exists.

The following links might help you find the content you need:


You can also search the Documentation Portal or visit the home page.

English
  • Data Ingestion and Replication
  • All Products

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Back Next

Credential Profile File Authentication

Credential Profile File Authentication

You can provide the credentials required to establish the connection with Amazon S3 through the credential profile file that contains an access key and secret key. The credential profile file contains an access key, a secret key, and a session token when you use temporary security credentials.
You can use permanent IAM credentials or temporary security credentials with a session token when you use credential profile file authentication.
If you do not specify the credential profile file path, the default credential file path is used. If you do not specify the profile name, the credentials are used from the default profile in the credential file.
Consider the following rules for a credential profile file:
  • The credential file must be on the same machine where you installed the Secure Agent.
  • The credential profile file name must end with
    .credentials
    .
  • If you do not specify the credential profile path, the Secure Agent uses the credential profile file present in the following default location in your home directory:
    ~/.aws/credentials
    On Windows, you can refer to your home directory by using the environment variable
    %UserProfile%
    . On Unix-like systems, you can use the environment variable
    $HOME
    .
A sample credential profile file: 
[default]

aws_access_key_id = 1233333

aws_secret_access_key = abcabcabc


[test-profile]

aws_access_key_id = 1233333

aws_secret_access_key = abcabcabc

aws_session_token = jahaheieomdrtflmlioerp
The
aws_access_key_id
 and
aws_secret_access_key
 specify the AWS access key and secret key used as part of credentials to authenticate the user.
The
aws_session_token
 specifies an AWS session token used as part of the credentials to authenticate the user. A session token is required only if you specify temporary security credentials.
0 COMMENTS
We’d like to hear from you!