Work In Progress​

• Today the team troubleshooted the ingress and verified the jar file versions.
• The team checked and noted the service account and statefulset configurations.
• Altered the pod with the AWS CLI and attempted to run S3 commands but uncounted a timeout error.

Tracking​

• The team followed up with the Customer on opening a support ticket with AWS.

• Our team will continue to troubleshoot the issue and look into debugging the AWS CLI errors.

• Cases open: 1

  • Case TS013430052

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "07/06/2023 Documentation".

Work In Progress​

• Today there was a presentation and discussion on IBM Sterling Secure Proxy (SSP).

Tracking​

• Our team is taking the information we got from the Customer's team yesterday and incorporating it into our troubleshooting with the Dev team.

• Cases open: 1

  • Case TS013430052

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "07/06/2023 Documentation".

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

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/28/2023 Documentation".

Work In Progress​

• The team continued to troubleshoot the AWS Signature error. The team first examined the configuration for the Business Process execution.
• The team then checked AWS S3 configuration and SSL and then reattempted to upload the file, but encountered the same error.
• The team then went through the logs to verify the details associated with the error.

Tracking​

• We noted the configurations currently being used in the Customer's environment, along with logs from the error. We will take this back to our Dev team and continue to troubleshoot this issue.

• Cases open: 1

  • Case TS013430052

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/27/2023 Documentation".

Work In Progress​

• Last Friday (6/23/23) the customer's team encountered an error while testing file transfer in Sterling.
• The error indicated a 400-status code, which typically means an invalid request from the client (Sterling) to the server (S3).
• The error message specifically mentions that requests specifying server-side encryption with AWS KMS managed keys require AWS Signature Version 4 and the S3 PUT service failed.

Tracking​

• Our team has opened a ticket (TS013430052) and are working 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

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/27/2023 Documentation".

Work In Progress​

• The team discussed the need to attach the KMS key to the access policy for S3.
• The customer's team noted that having “Bucket Key” enabled will generate a key, instead of fetching one.
• When setting the S3 bucket, we encountered issues with updating the policy document and encountered unsupported property policy documents error.
• We attempted to troubleshoot the issue by creating a new role and policy, but the problem persisted.
• It was suggested to remove the KMS actions and see if the policy update is successful without them.

Tracking​

• The customer's team said they would continue to debug and troubleshoot the error and we would reconvene next week.

• Cases open: 0

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/27/2023 Documentation".

Work In Progress​

• Pushing Towards Using an Accelerator: there was discussion on using an accelerator called Pragma Community Manager (PCM) to help prove out business use cases. It acts as an extra layer on top of B2B Integration (B2BI) and provides a single pane for managing operations. PCM acts as a one-stop-shop for setting up configurations and operations in File Gateway and the B2BI dashboard.
• There was a discussion on how the customer primarily uses S3 for file transfers. S3 buckets are encrypted with KMS keys for security.

Tracking​

• The the customer team requested documentation related to S3 and the currently supported features.

• Our team requested a bucket that had a policy that didn’t force KMS to be passed in the header.

• The customer requested a follow up working session to further discuss and test S3 buckets with KMS encryption and policies.

• Cases open: 0

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/20/2023 Documentation".

Work In Progress​

• The team troubleshoot the SFTP server by creating a new template and channel and modifying them.
• The team made adjustments to the network policies and tested SSH connectivity.
• They made adjustments to the remote profile and resolved the issue by adjusting the directory.
• They tested the file delivery and confirmed that the file was successfully delivered to the server.

Next Steps​

• Doing file pulls or GETS via SFTP from the SFTP server.

Tracking​

• We will continue to make documentation on these processes.

• Cases open: 0

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/20/2023 Documentation".

Work In Progress​

• The team did a walkthrough on how configure SFTP client in Sterling B2B Integrator.
• The team then showed how to create a channel in Sterling File Gateway.
• The team set up consumer and producer Partners within Sterling File Gateway.
• Troubleshoot server receiving the file.

Tracking​

• Waiting on their pipeline to finish provisioning access to their SFTP server.

• We are currently preparing documentation for this process, and have sent out today’s recorded session.

• Cases open: 0

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/20/2023 Documentation".

Work In Progress​

• The KMS encryption with S3 is not currently supported and should be available by the end of the year or early next year. In the meantime, the team can focus on testing SFTP.

Tracking​

• The Customer needs to set up an SFTP server and create an SFTP user with private keys for testing.

• The Customer will speak to his team about getting an exception for S3 bucket storage to use standard AWS SSE instead of KMS.

• Cases open: 0

• Cases closed: 5

  • case TS012906539
  • case TS013042929
  • case TS012831699
  • case TS012704616
  • case TS012702956

• ibm-client-engineering/solution-sfg-aws#17

• This flight log is being submitted via PR "06/14/2023 Documentation".