PlatformNotSupportedException

[Phanindra-labs]

How does Metering service determine RequestUsage API call was originated from supported platforms EKS and ECS when Request only contains ProductID, Public Key and Nounce? I am getting "PlatformNotSupportedException" despite making calls from EKS pod.

[jmklix]

I'm not sure that is something that is effected by the sdk. It sounds like that exception might be returned by the service not the sdk. Do you mind linking a minimal code snippet that returns the same exception that you are seeing?

[Phanindra-labs]

You are right. I am getting the exception as an http error code in response. Seems like issue is on server side. Container logs show it has gone through all credential providers in default credential provider chain and successfully authorized by instance profile (metadata service) before making a call to metering server. Unfortunately I cannot paste code since the container is bought from market place. Here are the related logs of metering client.

0.0 AWSME main warn : awssdk[ClientConfiguration]: Retry Strategy will use the default max attempts.
0.0 AWSME main info : awssdk[CurlHandleContainer]: Pool grown by 2
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main info : awssdk[EC2MetadataClient]: Detected current region as us-east-1
0.0 AWSME main info : awssdk[Aws::Config::AWSConfigFileProfileConfigLoader]: Initializing config loader against fileName /home//.aws/credentials and using profilePrefix = 0
0.0 AWSME main info : awssdk[ProfileConfigFileAWSCredentialsProvider]: Setting provider to read credentials from /home//.aws/credentials for credentials file and /home//.aws/config for the config file , for use with profile default
0.0 AWSME main info : awssdk[ProcessCredentialsProvider]: Setting process credentials provider to read config from default
0.0 AWSME main warn : awssdk[STSAssumeRoleWithWebIdentityCredentialsProvider]: Token file must be specified to use STS AssumeRole web identity creds provider.
0.0 AWSME main info : awssdk[SSOCredentialsProvider]: Setting sso credentials provider to read config from default
0.0 AWSME main info : awssdk[InstanceProfileCredentialsProvider]: Creating Instance with default EC2MetadataClient and refresh rate 300000
0.0 AWSME main info : awssdk[DefaultAWSCredentialsProviderChain]: Added EC2 metadata service credentials provider to the provider chain.
0.0 AWSME main info : awssdk[Aws::Config::AWSConfigFileProfileConfigLoader]: Unable to open config file /home//.aws/credentials for reading.
0.0 AWSME main info : awssdk[Aws::Config::AWSProfileConfigLoader]: Failed to reload configuration.
0.0 AWSME main info : awssdk[ProcessCredentialsProvider]: Failed to find credential process's profile: default
0.0 AWSME main info : awssdk[SSOCredentialsProvider]: Unable to open token file on path: /home//.aws/sso/cache/da39a3swddeeded5e6b4b0d325ded5xssbfef95601890afd80709.json
0.0 AWSME main info : awssdk[InstanceProfileCredentialsProvider]: Credentials have expired attempting to repull from EC2 Metadata Service.
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main error: awssdk[CurlHttpClient]: Curl returned error code 28 - Timeout was reached
0.0 AWSME main error: awssdk[EC2MetadataClient]: Http request to retrieve credentials failed
0.0 AWSME main warn : awssdk[EC2MetadataClient]: Request failed, now waiting 0 ms before attempting again.
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main error: awssdk[CurlHttpClient]: Curl returned error code 28 - Timeout was reached
0.0 AWSME main error: awssdk[EC2MetadataClient]: Http request to retrieve credentials failed
0.0 AWSME main error: awssdk[EC2MetadataClient]: Can not retrieve resource from http://169.254.169.254/latest/api/token
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main info : awssdk[Aws::Config::EC2InstanceProfileConfigLoader]: Successfully pulled credentials from metadata service with access key
0.0 AWSME main info : awssdk[Aws::Config::AWSProfileConfigLoader]: Successfully reloaded configuration.
0.0 AWSME main info : awssdk[CurlHandleContainer]: Initializing CurlHandleContainer with size 25
0.0 AWSME main info : awssdk[ProcessCredentialsProvider]: Failed to find credential process's profile: default
0.0 AWSME main info : awssdk[SSOCredentialsProvider]: Unable to open token file on path: /home//.aws/sso/cache/dfda39a3ee5e6b4b0d325sdrss5bfef9cs5601890afd80709.json
0.0 AWSME main info : awssdk[CurlHandleContainer]: Pool grown by 2
0.0 AWSME main info : awssdk[CurlHandleContainer]: Connection has been released. Continuing.
0.0 AWSME main warn : awssdk[AWSErrorMarshaller]: Encountered AWSError 'PlatformNotSupportedException': This operation can only be called from within an ECS task or an EKS pod
0.0 AWSME main error: awssdk[AWSClient]: HTTP response code: 400
0.0 AWSME main error: Resolved remote host IP address:
0.0 AWSME main error: Request ID:
0.0 AWSME main error: Exception name: PlatformNotSupportedException
0.0 AWSME main error: Error message: This operation can only be called from within an ECS task or an EKS pod
0.0 AWSME main error: 5 response headers:
0.0 AWSME main error: connection : close
0.0 AWSME main error: content-length : 126
0.0 AWSME main error: content-type : application/x-amz-json-1.1
0.0 AWSME main error: date : Sun, 11 Sep 2022 05:30:54 GMT
0.0 AWSME main error: x-amzn-requestid :
0.0 AWSME main warn : awssdk[AWSClient]: If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
0.0 AWSME main warn : Error registering usage: This operation can only be called from within an ECS task or an EKS pod
0.0 AWSME main error: AWS Marketplace metering API not available. This usualy happens due to the following reasons:
0.0 AWSME main error: 1. You have not subscribed to the container image in AWS Marketplace.
0.0 AWSME main error: 2. You are not running under EKS or ECR.
0.0 AWSME main error: 3. You have no allowed Metering API access through IAM configuration.
0.0 AWSME main error: Stopping now...

[jmklix]

Sorry, I can't be of more help. This link has more details about the PlatformNotSupportedException that you are seeing and might be helpful.

Entitlement: RegisterUsage allows you to verify that the customer running your paid software is subscribed to your product on AWS Marketplace, enabling you to guard against unauthorized use. Your container image that integrates with RegisterUsage is only required to guard against unauthorized use at container startup, as such a CustomerNotSubscribedException or PlatformNotSupportedException will only be thrown on the initial call to RegisterUsage. Subsequent calls from the same Amazon ECS task instance (e.g. task-id) or Amazon EKS pod will not throw a CustomerNotSubscribedException, even if the customer unsubscribes while the Amazon ECS task or Amazon EKS pod is still running.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.