Menu
AWS Service Configuration
Error when creating service
This is the error:
creation failed: ns-4qwdjfuohtlmpiua (Service: AWSServiceDiscovery; Status Code: 400; Error Code: NamespaceNotFound; Request ID: 025b29e2-f73b-11e8-be57-33d9b1393e60)
I am setting Namespace to create new private namespace, but it doesn't appear to matter what I put, it will says Created private namespace with a random string.
Any help is greatly appreciated!
449
Namespaces are global resources in ECS. A System Administrator or Namespace Administrator can access ECS from any federated VDC and can configure the namespace settings. The object users that you assign to a namespace are global and can access the object store from any federated VDC.
You can create a namespace with a call to the aws servicediscovery create-private-dns-namespace command or in the ECS console. Namespaces are roughly equivalent to hosted zones in Route 53.
To configure service discoveryOn the Configure network page, select Enable service discovery integration. For Namespace, select an existing Amazon Route 53 namespace, if you have one, otherwise select create new private namespace.
Services configured to use Amazon ECS service discovery have a limit of 1,000 tasks per service. This is due to the AWS Cloud Map service quota for the number of instances per service.
The same thing just has happened to me, and the way to move past it was simply to go "Back" in the Console creation wizard, up to the "Service Discovery" section. I could find the namespace in the dropdown list, selected, and simply retried the service creation. It worked. I suspect there is a race condition between the namespace creation and verification.
135
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
