Cross-Account S3 Tables Access Issue: AssumeRole Cannot Find s3tablescatalog

When accessing S3 Tables across AWS accounts using AssumeRole, there are specific steps you need to follow beyond just having the right IAM permissions. The issue you're encountering with "CATALOG_NOT_FOUND" suggests that while you have the necessary IAM policies attached to your role, you're missing the required resource links and cross-account permissions setup.

Here's what you need to do:

1. Create a resource link in Account A (544459981429) to the shared database in Account B (862998707484). This is a crucial step that connects your account to the shared resources.

You can create this resource link using AWS Glue with a command similar to:

aws glue create-database 
--region us-west-2 
--catalog-id "544459981429" 
--database-input '{
"Name": "b_dingyi_resourcelink",
"TargetDatabase": {
"CatalogId": "862998707484:s3tablescatalog/aws-s3",
"DatabaseName": "b_dingyi-integ-862998707484"
},
"CreateTableDefaultPermissions": []
}'

2. Ensure cross-account permissions are granted on the table in Account B. The owner of Account B needs to grant permissions to your role in Account A:

aws lakeformation grant-permissions 
--region us-west-2 
--principal DataLakePrincipalIdentifier=arn:aws:iam::544459981429:role/YourAssumeRoleName
--resource Table='{
"CatalogId": "862998707484:s3tablescatalog/aws-s3",
"DatabaseName": "b_dingyi-integ-862998707484",
"Name": "inventory"
}'
--permissions ALL

3. Grant DESCRIBE permission on the resource link in Account A:

aws lakeformation grant-permissions 
--region us-west-2
--principal DataLakePrincipalIdentifier=arn:aws:iam::544459981429:role/YourAssumeRoleName
--resource Database='{CatalogId=544459981429, Name=b_dingyi_resourcelink}'
--permissions DESCRIBE

4. Check S3 bucket policies to ensure Account A has access to any underlying S3 data. The bucket policy should include a statement allowing access from Account A's role.

5. Verify Object Ownership settings in the S3 bucket. If objects were uploaded by different accounts, ensure the Object Ownership setting is "Bucket owner enforced" to avoid access issues.

After completing these steps, you should be able to query the S3 Tables using your AssumeRole from Account A. Instead of directly referencing the catalog in Account B, you would query using the resource link you created in Account A.
Sources
Accessing shared Amazon S3 tables - AWS Lake Formation
Configure cross-account access in Athena to Amazon S3 buckets - Amazon Athena
Why can't my S3 File Gateway access objects uploaded by cross-account users? | AWS re:Post