AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
License Server Endpoint Provisioning Failed - Internal Server Error
We're experiencing an issue with the AWS License Manager license server endpoint that's showing a failed status, but provides almost no information.
Error: After 30+ minutes, license server endpoint just displays "Internal Server Error. Service not available."
See screenshot:
Configuration Details: This is happening when trying to register a new managed active directory with License Manager, for RDS SAL or Office Licenses. As far as I can tell, our security groups, VPC setup, and other things are correct. I've checked the following:
-
VPC endpoints are properly configured and available -
Security groups allow HTTPS traffic (port 443) -
Individual license servers are healthy and provisioned -
No issues with my AWS account or IAM permissions
Question: Since the individual license servers are healthy but the overall endpoint provisioning is failing with an "Internal Server Error," this appears to be an AWS service-side issue. The error suggests a problem with the License Manager service itself rather than my configuration.
Has anyone encountered this specific error with License Manager endpoints? Is this a known issue with the service, or are there additional troubleshooting steps I should try? It'd be especially helpful if we could get any more detailed errors or the process that it's trying to do to set things up so we can check for a misconfiguration
Tags: license-manager, rds-sal, vpc-endpoints, provisioning-failed
- Newest
- Most votes
- Most comments
When encountering a "License Server Endpoint Provisioning Failed - Internal Server Error" in AWS License Manager, there are several potential causes and troubleshooting steps to consider.
First, this could be related to issues with the AWS Secrets Manager configuration. License Manager requires a properly formatted secret for service account credentials. Ensure your secret:
- Has the prefix
license-manager-user- - Is formatted in JSON with non-empty values for both "username" and "password" keys
- Contains valid service account credentials for your Active Directory domain
Beyond the secrets configuration, there are several other common causes for License Manager failures:
-
Service throttling: The License Manager operation might have been throttled by a backend service. This can happen during periods of high activity.
-
Role permissions issues: License Manager may be unable to assume the necessary role. Verify that the servicecatalog.amazonaws.com principal (or the regional equivalent) is properly configured in the trust policy.
-
Internal service errors: Sometimes AWS License Manager experiences internal errors that require waiting or contacting AWS Support.
For troubleshooting:
-
Check EventBridge for more detailed events related to the failure. License Manager sends events like "License Server Endpoint Provisioning Failed" to EventBridge, which might contain additional diagnostic information.
-
Verify that your IAM permissions are correct. Common errors include AccessDeniedException or AuthorizationException when your AWS account doesn't have the necessary permissions.
-
If the issue persists after checking these configurations, it could indeed be an internal AWS service issue, in which case contacting AWS Support would be the next step.
For RDS licensing specifically, also verify that your Remote Desktop Licensing Manager is properly configured and that you have the appropriate Client Access Licenses (CALs) installed if you're seeing licensing-related errors in your environment.
Sources
User subscriptions in AWS License Manager events - Amazon EventBridge
Issue with Remote Desktop Licensing Manager on AWS Microsoft AD | AWS re:Post
AWS Service Catalog Service Actions - AWS Service Catalog
GetServiceSettings - AWS License Manager
Getting error - No CALs are installed or issued on this License Server | AWS re:Post
Relevant content
asked 11 years ago
asked 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
