NathanCYee opened a new pull request, #17158:
URL: https://github.com/apache/iceberg/pull/17158

   Updated the assume role documentation to remove the exclusion on the 
settings being applied to the STS client. #16794 changed the behavior to 
explicitly add a region to the STS client following the AWS recommended best 
practices. #10289 flagged that the regional endpoint was now enabled by default 
in the AWS Java 2.0 SDK.
   
   There was a [documented update that the STS 
service](https://aws.amazon.com/blogs/security/announcing-upcoming-changes-to-the-aws-security-token-service-global-endpoint/)
 changed from only being served out of `us-east-1` to becoming regional by 
default for non opt-in regions. 
   > April 18, 2025: AWS has made changes to the AWS Security Token Service 
(AWS STS) global endpoint (sts.amazonaws.com) in Regions [enabled by 
default](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html)
 to enhance its resiliency and performance. AWS STS requests to the global 
endpoint are automatically served in the same AWS Region as your workloads. 
These changes will not be deployed to opt-in Regions. We recommend that you use 
the appropriate AWS STS regional endpoints. For more information, see [AWS STS 
global endpoint 
changes](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_region-endpoints.html#reference_sts_global_endpoint_changes)
 in the IAM User Guide.
   
   The old behavior to use the global endpoint is now considered 
[legacy](https://docs.aws.amazon.com/sdkref/latest/guide/feature-sts-regionalized-endpoints.html)
 in the SDK. 
   > All new SDK major versions releasing after July 2022 will default to 
regional. New SDK major versions might remove this setting and use regional 
behavior. To reduce future impact regarding this change, we recommend you start 
using regional in your application when possible.
   
   


-- 
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