Nimble Studio File Transfer: Permissions Error

If you are receiving any of the below errors it is due to having invalid permissions with their credentials to the S3 Bucket:

AssumeRoleTokenProviderNotSetError: assume role with MFA enabled. but AssumeRoleTokenProvider session option not set.
  Failed Establishing a session to AWS:NoCredentialProviders: no valid providers in chain. Deprecated
  Failed establishing a session to AWS:ExpiredToken: The provided token has expired.

Failed establishing a session to AWS:NoSuchBucket: The specified bucket does not exist
    status code: 404, request id: T9AFHCF4W899K4CD, host id: U3OpDmSQfGY48bW0YpFfuOHM16f1KqUikh0o2edru5lklOz8kiOKSELNgnXxYRUdgvKnFePnXL8=

Failed establishing a session to AWS:BucketRegionError: incorrect region, the bucket is not in 'us-west-2' region at endpoint ''
    status code: 301, request id: , host id:

Failed establishing a session to AWS:AccessDenied: Access Denied
    status code: 403, request id: FEEH9HJDN3J897V0, host id: bazXZ2FIvPToCI7VBxsFQ9T7Dn1QntPTXq8yfbjhaIbhyh58rmKHo8u+k0t+/eFVlliNXst5kSA=

The cause for this behavior is due to credentials either being expired or not having the correct access to the corresponding S3 Bucket

This can be fixed by either generating new credentials or by updating the permissions of the existing credentials to give the correct access. It would also be worth checking if the user had properly setup their profile and they have the correct profile name set in their Nimble Studio File Transfer (NSFT) configuration. You can also check that the user inputted their bucket name into NSFT correctly. IAM Policy that will give the required access is linked here.