View Source aws_servicediscovery (aws v1.0.4)
Cloud Map
With Cloud Map, you can configure public DNS, private DNS, or HTTP namespaces that your microservice applications run in.
When an instance becomes available, you can call the Cloud Map API to register the instance with Cloud Map. For public or private DNS namespaces, Cloud Map automatically creates DNS records and an optional health check. Clients that submit public or private DNS queries, or HTTP requests, for the service receive an answer that contains up to eight healthy records.Summary
Functions
Creates an HTTP namespace.
Creates a private namespace based on DNS, which is visible only inside a specified Amazon VPC.
Creates a public namespace based on DNS, which is visible on the internet.
Creates a service.
Deletes a namespace from the current account.
Deletes a specified service.
Discovers registered instances for a specified namespace and service.
Gets the current health status (Healthy
, Unhealthy
, or Unknown
) of one or more instances that are associated with a specified service.
Gets information about any operation that returns an operation ID in the response, such as a CreateHttpNamespace
request.
Creates or updates one or more records and, optionally, creates a health check based on the settings in a specified service.
Submits a request to change the health status of a custom health check to healthy or unhealthy.
Submits a request to perform the following operations
Functions
Creates an HTTP namespace.
Service instances registered using an HTTP namespace can be discovered using a DiscoverInstances
request but can't be discovered using DNS.
Creates a private namespace based on DNS, which is visible only inside a specified Amazon VPC.
The namespace defines your service naming scheme. For example, if you name your namespaceexample.com
and name your service backend
, the resulting DNS name for the service is backend.example.com
. Service instances that are registered using a private DNS namespace can be discovered using either a DiscoverInstances
request or using DNS. For the current quota on the number of namespaces that you can create using the same Amazon Web Services account, see Cloud Map quotas: https://docs.aws.amazon.com/cloud-map/latest/dg/cloud-map-limits.html in the Cloud Map Developer Guide.
Creates a public namespace based on DNS, which is visible on the internet.
The namespace defines your service naming scheme. For example, if you name your namespace example.com
and name your service backend
, the resulting DNS name for the service is backend.example.com
. You can discover instances that were registered with a public DNS namespace by using either a DiscoverInstances
request or using DNS. For the current quota on the number of namespaces that you can create using the same Amazon Web Services account, see Cloud Map quotas: https://docs.aws.amazon.com/cloud-map/latest/dg/cloud-map-limits.html in the Cloud Map Developer Guide.
CreatePublicDnsNamespace
API operation is not supported in the Amazon Web Services GovCloud (US) Regions.
Creates a service.
This action defines the configuration for the following entities:
For public and private DNS namespaces, one of the following combinations of DNS records in Amazon Route 53:
A
AAAA
A
andAAAA
SRV
CNAME
Optionally, a health check
After you create the service, you can submit a RegisterInstance: https://docs.aws.amazon.com/cloud-map/latest/api/API_RegisterInstance.html request, and Cloud Map uses the values in the configuration to create the specified entities.
For the current quota on the number of instances that you can register using the same namespace and using the same service, see Cloud Map quotas: https://docs.aws.amazon.com/cloud-map/latest/dg/cloud-map-limits.html in the Cloud Map Developer Guide.Deletes a namespace from the current account.
If the namespace still contains one or more services, the request fails.Deletes a specified service.
If the service still contains one or more registered instances, the request fails.Discovers registered instances for a specified namespace and service.
You can useDiscoverInstances
to discover instances for any type of namespace. DiscoverInstances
returns a randomized list of instances allowing customers to distribute traffic evenly across instances. For public and private DNS namespaces, you can also use DNS queries to discover instances.
Gets the current health status (Healthy
, Unhealthy
, or Unknown
) of one or more instances that are associated with a specified service.
Gets information about any operation that returns an operation ID in the response, such as a CreateHttpNamespace
request.
Creates or updates one or more records and, optionally, creates a health check based on the settings in a specified service.
When you submit a RegisterInstance
request, the following occurs:
For each DNS record that you define in the service that's specified by
ServiceId
, a record is created or updated in the hosted zone that's associated with the corresponding namespace.If the service includes
HealthCheckConfig
, a health check is created based on the settings in the health check configuration.The health check, if any, is associated with each of the new or updated records.
One RegisterInstance
request must complete before you can submit another request and specify the same service ID and instance ID.
For more information, see CreateService: https://docs.aws.amazon.com/cloud-map/latest/api/API_CreateService.html.
When Cloud Map receives a DNS query for the specified DNS name, it returns the applicable value:
If the health check is healthy: returns all the records
If the health check is unhealthy: returns the applicable value for the last healthy instance
If you didn't specify a health check configuration: returns all the records
Submits a request to change the health status of a custom health check to healthy or unhealthy.
You can use UpdateInstanceCustomHealthStatus
to change the status only for custom health checks, which you define using HealthCheckCustomConfig
when you create a service. You can't use it to change the status for Route 53 health checks, which you define using HealthCheckConfig
.
Submits a request to perform the following operations:
Update the TTL setting for existing
DnsRecords
configurationsAdd, update, or delete
HealthCheckConfig
for a specified serviceYou can't add, update, or delete a
HealthCheckCustomConfig
configuration.
For public and private DNS namespaces, note the following:
If you omit any existing
DnsRecords
orHealthCheckConfig
configurations from anUpdateService
request, the configurations are deleted from the service.If you omit an existing
HealthCheckCustomConfig
configuration from anUpdateService
request, the configuration isn't deleted from the service.