Troubleshooting
How to check if a bucket fails to mount on a VDI
If a bucket fails to mount on a VDI, there are a few locations where you can check for errors. Follow the steps below.
-
Check the VDI Logs:
-
Log into the AWS Management Console.
-
Open the EC2 Console and navigate to Instances.
-
Select the VDI instance you launched.
-
Connect to the VDI via the Session Manager.
-
Run the following commands:
sudo su cd ~/bootstrap/logs
Here, you'll find the bootstrap logs. The details of any failure will be located in the
configure.log.{time}
file.Additionally, check the
/etc/message
log for more details.
-
-
Check Custom Credential Broker Lambda CloudWatch Logs:
-
Log into the AWS Management Console.
-
Open the CloudWatch Console and navigate to Log groups.
-
Search for the log group
/aws/lambda/
.<stack-name>
-vdc-custom-credential-broker-lambda -
Examine the first available log group and locate any errors within the logs. These logs will contain details regarding potential issues providing temporary custom credentials for mounting S3 buckets.
-
-
Check Custom Credential Broker API Gateway CloudWatch Logs:
-
Log into the AWS Management Console.
-
Open the CloudWatch Console and navigate to Log groups.
-
Search for the log group
.<stack-name>
-vdc-custom-credential-broker-lambdavdccustomcredentialbrokerapigatewayaccesslogs<nonce> -
Examine the first available log group and locate any errors within the logs. These logs will contain details regarding any requests and responses to the API Gateway for custom credentials needed to mount the S3 buckets.
-
How to edit a bucket's IAM role configuration after onboarding
-
Sign in to the AWS DynamoDB Console
. -
Select the Table:
-
In the left navigation pane, choose Tables.
-
Find and select
.<stack-name>
.cluster-settings
-
-
Scan the Table:
-
Choose Explore table items.
-
Ensure Scan is selected.
-
-
Add a Filter:
-
Choose Filters to open the filter entry section.
-
Set the filter to match your key-
-
Attribute: Enter the key.
-
Condition: Select Begins with.
-
Value: Enter
shared-storage.
replacing<filesystem_id>
.s3_bucket.iam_role_arn<filesystem_id>
with the value of the filesystem that needs to be modified.
-
-
-
Execute the Scan:
Choose Run to run the scan with the filter.
-
Check the value:
If the entry exists, ensure the value is correctly set with the right IAM role ARN.
If the entry does not exist:
-
Choose Create item.
-
Enter the item details:
-
For the key attribute, enter
shared-storage.
.<filesystem_id>
.s3_bucket.iam_role_arn -
Add the correct IAM role ARN.
-
-
Choose Save to add the item.
-
-
Restart the VDI instances:
Reboot the instance to ensure the VDIs that are affected by the incorrect IAM role ARN are mounted again.