Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateServiceRequest

import type { CreateServiceRequest } from "https://aws-api.deno.dev/v0.3/services/servicediscovery.ts?docs=full";
interface CreateServiceRequest {
CreatorRequestId?: string | null;
Description?: string | null;
DnsConfig?: DnsConfig | null;
HealthCheckConfig?: HealthCheckConfig | null;
HealthCheckCustomConfig?: HealthCheckCustomConfig | null;
Name: string;
NamespaceId?: string | null;
Tags?: Tag[] | null;
Type?: ServiceTypeOption | null;
}

§Properties

§
CreatorRequestId?: string | null
[src]

A unique string that identifies the request and that allows failed CreateService requests to be retried without the risk of running the operation twice. CreatorRequestId can be any unique string (for example, a date/timestamp).

§
Description?: string | null
[src]

A description for the service.

§
DnsConfig?: DnsConfig | null
[src]

A complex type that contains information about the Amazon Route 53 records that you want Cloud Map to create when you register an instance.

§
HealthCheckConfig?: HealthCheckConfig | null
[src]

Public DNS and HTTP namespaces only. A complex type that contains settings for an optional Route 53 health check. If you specify settings for a health check, Cloud Map associates the health check with all the Route 53 DNS records that you specify in DnsConfig.

! IMPORTANT: ! If you specify a health check configuration, you can specify either HealthCheckCustomConfig or HealthCheckConfig but not both.

For information about the charges for health checks, see Cloud Map Pricing.

§
HealthCheckCustomConfig?: HealthCheckCustomConfig | null
[src]

A complex type that contains information about an optional custom health check.

! IMPORTANT: ! If you specify a health check configuration, you can specify either HealthCheckCustomConfig or HealthCheckConfig but not both.

You can't add, update, or delete a HealthCheckCustomConfig configuration from an existing service.

§
Name: string
[src]

The name that you want to assign to the service.

If you want Cloud Map to create an SRV record when you register an instance and you're using a system that requires a specific SRV format, such as HAProxy, specify the following for Name:

  • Start the name with an underscore (_), such as _exampleservice.
  • End the name with _.protocol, such as ._tcp.

When you register an instance, Cloud Map creates an SRV record and assigns a name to the record by concatenating the service name and the namespace name (for example,

_exampleservice._tcp.example.com).

Note: For services that are accessible by DNS queries, you can't create multiple services with names that differ only by case (such as EXAMPLE and example). Otherwise, these services have the same DNS name and can't be distinguished. However, if you use a namespace that's only accessible by API calls, then you can create services that with names that differ only by case.

§
NamespaceId?: string | null
[src]

The ID of the namespace that you want to use to create the service. The namespace ID must be specified, but it can be specified either here or in the DnsConfig object.

§
Tags?: Tag[] | null
[src]

The tags to add to the service. Each tag consists of a key and an optional value that you define. Tags keys can be up to 128 characters in length, and tag values can be up to 256 characters in length.

§

If present, specifies that the service instances are only discoverable using the DiscoverInstances API operation. No DNS records is registered for the service instances. The only valid value is HTTP.