yahwang opened a new issue, #2307:
URL: https://github.com/apache/iceberg-python/issues/2307

   ### Apache Iceberg version
   
   0.9.1 (latest release)
   
   ### Please describe the bug 🐞
   
   ### ~/.aws/credentials
   
   The default credentials are different from the developer's credentials.
   
   ```
   [default]
   aws_access_key_id=ABC
   aws_secret_access_key=ABC
   
   [dev]
   aws_access_key_id=DEF
   aws_secret_access_key=DEF
   ```
   
   ### ~/.aws/config
   ```
   [profile default]
   region=ap-northeast-2
   
   [profile dev]
   region=ap-northeast-2
   
   [profile prod]
   region=ap-northeast-2
   role_arn=arn:aws:iam::[ACCOUNT]:role/[Admin ROLE]
   source_profile=dev
   ```
   
   ### code
   
   ```
   from pyiceberg.catalog import load_catalog
   
   glue_catalog = load_catalog(
       'AwsDataCatalog',
       **{
           'glue.profile-name': 'prod',
           'glue.region': 'ap-northeast-2',
       },
       type='glue'
   )
   
   glue_catalog.list_namespaces() # work
   glue_catalog.list_tables(namespace='default') # work
   
   table = glue_catalog.load_table("default.iceberg_test")
   ```
   
   ```
   OSError: When reading information for key ... AWS Error ACCESS_DENIED during 
HeadObject operation: No response body.
   ```
   
   After changing the default credentials to dev's credentials, it worked. Is 
there any problem using source_profile?
   
   ### Willingness to contribute
   
   - [ ] I can contribute a fix for this bug independently
   - [ ] I would be willing to contribute a fix for this bug with guidance from 
the Iceberg community
   - [ ] I cannot contribute a fix for this bug at this time


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to