Work In Progress
- The discussion highlights the possibility that the issue could be related to the version of IBM Sterling B2Bi being used. The customer is on version 6.1.2.1, while the lab environment is using version 6.1.2.2. However, we have downgraded our version to match the customer's and we are still not encountering the issue.
- There was a discussion on how the AWS SDK is utilized in IBM Sterling B2Bi for interacting with S3. The error mentions an issue with the signature version being used. It is noted that AWS deprecated older signature versions, and the SDK should default to using version 4 signatures. The discussion speculates if the SDK version might be a factor in the error.
The following troubleshooting steps were taken in our IBM reference environment:
- We examined the IAM policy and configurations.
- We logged into to B2Bi and checked which version of the AWS SDK was being used.
- Logged into the cluster and checked to be sure a token was being obtained.
- Downgraded environment to 6.1.2.1 and we are still not encountering the issue.
Tracking
Our team is continuing to work closely with the Dev team to troubleshoot this issue.
Cases open: 1
- Case TS013430052
Cases closed: 5
- case TS012906539
- case TS013042929
- case TS012831699
- case TS012704616
- case TS012702956
This flight log is being submitted via PR "06/28/2023 Documentation".