Skip to content

License Service does not allow to set them in the AWS ECS Fargate usage logger for WebSphere Application Server

0

Hi AWS guys,

We are moving WebSphere on AWS Cloud ECS Fargate, this is an unsupported scenario actually. We are not able to implement license tracking because we have need:

SSE-KMS requires additional HTTP headers to be set in the request: https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOST.html#post-object-sse-specific-request-headers

License Service does not allow to set them in the LS Fargate usage logger: https://github.ibm.com/cloud-license-reporter/fargate-license-usage-logger/blob/6ce3[…]575e5cc09e11accbb651c/IBM-License-usage-logger-for-fargate.sh

Are there some solution that can be implemented? If, not I kindly ask to everyone who is facing this problem to vote our idea on IBM site: https://integration-development.ideas.ibm.com/ideas/ILMT-I-150.

BR, Andrea

  • Sorry im little confused of the issue here?

1 Answer
0

I apologize, but I cannot provide a specific solution to the issue you're describing with WebSphere on AWS ECS Fargate and license tracking. The scenario you've mentioned - running WebSphere on AWS ECS Fargate - is not a supported configuration according to the information provided.

However, I can offer some general insights about AWS Fargate and licensing:

AWS Fargate is a serverless compute engine for containers that works with Amazon ECS and EKS. It allows you to run containerized applications without managing the underlying infrastructure.

For managing software licenses in AWS environments, including those running on Fargate, AWS provides a service called AWS License Manager. This service helps you manage software licenses from various vendors across AWS and on-premises environments. It allows you to set rules based on your licensing agreements to prevent violations and can send notification alerts to help ensure you're meeting license requirements.

Regarding the specific issue with SSE-KMS and additional HTTP headers, this is indeed a requirement for server-side encryption with AWS Key Management Service. However, the ability to set these headers would depend on the specific implementation of the license tracking solution you're using.

As for the IBM License Service and its Fargate usage logger, since this appears to be an IBM-specific tool, the limitations you're encountering would need to be addressed by IBM. The suggestion to vote for the idea on the IBM site is a good one, as it can help bring attention to this issue and potentially lead to a solution from IBM.

In the meantime, you might want to explore alternative licensing solutions that are compatible with AWS Fargate, or consider discussing your specific use case with AWS support to see if they can offer any workarounds or alternative approaches for your WebSphere deployment on Fargate.
Sources
Implementation priorities - Management and Governance Cloud Environment Guide
Serverless Compute Engine – AWS Fargate Features – Amazon Web Services

answered 2 years ago

EXPERT

reviewed 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.