Cloud Map

AWS Cloud Map (servicediscovery) on fakecloud: namespace control plane over HTTP, public-DNS, and private-DNS namespaces, driven by the async operation model. awsJson1.1.

fakecloud implements AWS Cloud Map (servicediscovery), the service-discovery and application resource registry, as an awsJson1.1 control plane. The complete 30-operation surface ships — namespaces, operation tracking, services, instances, the DiscoverInstances data-plane lookup, and tagging — backed by account-partitioned state that persists across restarts in persistent mode.

Supported now (all 30 operations)

  • Namespaces — CreateHttpNamespace, CreatePrivateDnsNamespace, CreatePublicDnsNamespace, GetNamespace, ListNamespaces, DeleteNamespace, UpdateHttpNamespace, UpdatePrivateDnsNamespace, UpdatePublicDnsNamespace. Each namespace carries an Id (ns-...), an ARN, its Type (HTTP / DNS_PUBLIC / DNS_PRIVATE), Properties (HttpProperties.HttpName; DNS types also get a synthesized DnsProperties.HostedZoneId and default SOA), a ServiceCount, and tags. CreatePrivateDnsNamespace requires a Vpc.

  • Operations — GetOperation, ListOperations. Cloud Map's create/delete/ update calls are asynchronous: they return an OperationId rather than the resource. fakecloud mints an Operation (SUBMITTED) whose status settles to SUCCESS when you call GetOperation (deterministic, no background timer), with a Targets map pointing at the affected namespace. The namespace itself is visible immediately via GetNamespace / ListNamespaces.

  • Services — CreateService, GetService, ListServices, UpdateService, DeleteService, plus GetServiceAttributes, UpdateServiceAttributes, DeleteServiceAttributes. Each service carries an Id (srv-...), an ARN, its NamespaceId, DnsConfig (RoutingPolicy + DnsRecords), HealthCheckConfig / HealthCheckCustomConfig, an InstanceCount, and a string-map of service attributes. CreateService/DeleteService are synchronous (and adjust the parent namespace's ServiceCount); UpdateService is asynchronous (returns an OperationId). ListServices filters by NAMESPACE_ID.

  • Instances — RegisterInstance, DeregisterInstance, GetInstance, ListInstances, GetInstancesHealthStatus, UpdateInstanceCustomHealthStatus. Instances register with well-known attributes (AWS_INSTANCE_IPV4 / IPV6 / PORT / CNAME, validated against the service's DnsConfig record types), carry a health status (custom health for services with a HealthCheckCustomConfig), and adjust the service's InstanceCount. RegisterInstance / DeregisterInstance are asynchronous (return an OperationId).

  • Discovery — DiscoverInstances resolves a namespace + service by name and returns matching instances, filtered by QueryParameters (attribute equality) and a HealthStatus filter (default HEALTHY_OR_ELSE_ALL); it carries a per-service InstancesRevision counter surfaced by DiscoverInstancesRevision.

  • Tagging — TagResource, UntagResource, ListTagsForResource over both namespace and service ARNs (create-time Tags are reflected).

ListNamespaces, ListServices, ListInstances, and ListOperations paginate with MaxResults / NextToken and honor Filters. 100% conformance across the full surface: all 1,062 generated Smithy probe variants for the 30 operations pass. There is no DNS/HTTP data plane beyond the DiscoverInstances API.

Example

import boto3
sd = boto3.client("servicediscovery", endpoint_url="http://localhost:4566")

op = sd.create_http_namespace(Name="my-app")
# create returns an operation id; poll it to completion
status = sd.get_operation(OperationId=op["OperationId"])["Operation"]["Status"]
print(status)  # SUCCESS

ns_id = sd.get_operation(OperationId=op["OperationId"])["Operation"]["Targets"]["NAMESPACE"]
print(sd.get_namespace(Id=ns_id)["Namespace"]["Name"])  # my-app