Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra.
AWS App Mesh points de terminaison et quotas
Pour vous connecter par programmation à un AWS service, vous utilisez un point de terminaison. AWS les services proposent les types de terminaux suivants dans certaines ou toutes les AWS régions prises en charge par le service : points de terminaison, IPv4 points de terminaison à double pile et points de terminaison FIPS. Certains services fournissent des points de terminaison mondiaux. Pour de plus amples informations, veuillez consulter AWS points de terminaison de service.
Les quotas de service, également appelés limites, correspondent au nombre maximal de ressources ou d'opérations de service pour votre AWS compte. Pour de plus amples informations, veuillez consulter AWS quotas de service.
Vous trouverez ci-dessous les points de terminaison et les quotas de service pour ce service.
Points de terminaison de service
Nom de la région | Région | Point de terminaison | Protocole |
---|---|---|---|
US East (Ohio) | us-east-2 |
appmesh.us-east-2.amazonaws.com appmesh-envoy-management-fips.us-east-2.amazonaws.com appmesh.us-east-2.api.aws appmesh-envoy-management-fips.us-east-2.api.aws appmesh-envoy-management.us-east-2.amazonaws.com appmesh-envoy-management.us-east-2.api.aws appmesh-fips.us-east-2.api.aws appmesh-fips.us-east-2.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
US East (N. Virginia) | us-east-1 |
appmesh.us-east-1.amazonaws.com appmesh-envoy-management.us-east-1.api.aws appmesh-fips.us-east-1.amazonaws.com appmesh-envoy-management-fips.us-east-1.api.aws appmesh-envoy-management.us-east-1.amazonaws.com appmesh.us-east-1.api.aws appmesh-fips.us-east-1.api.aws appmesh-envoy-management-fips.us-east-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
USA Ouest (Californie du Nord) | us-west-1 |
appmesh.us-west-1.amazonaws.com appmesh-envoy-management.us-west-1.amazonaws.com appmesh.us-west-1.api.aws appmesh-fips.us-west-1.api.aws appmesh-fips.us-west-1.amazonaws.com appmesh-envoy-management.us-west-1.api.aws appmesh-envoy-management-fips.us-west-1.amazonaws.com appmesh-envoy-management-fips.us-west-1.api.aws |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
US West (Oregon) | us-west-2 |
appmesh.us-west-2.amazonaws.com appmesh-envoy-management.us-west-2.amazonaws.com appmesh-envoy-management-fips.us-west-2.amazonaws.com appmesh-fips.us-west-2.amazonaws.com appmesh.us-west-2.api.aws appmesh-fips.us-west-2.api.aws appmesh-envoy-management-fips.us-west-2.api.aws appmesh-envoy-management.us-west-2.api.aws |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
Afrique (Le Cap) | af-south-1 |
appmesh.af-south-1.amazonaws.com appmesh-envoy-management.af-south-1.amazonaws.com appmesh.af-south-1.api.aws appmesh-envoy-management.af-south-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asie-Pacifique (Hong Kong) | ap-east-1 |
appmesh.ap-east-1.amazonaws.com appmesh.ap-east-1.api.aws appmesh-envoy-management.ap-east-1.api.aws appmesh-envoy-management.ap-east-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS |
Asie-Pacifique (Jakarta) | ap-southeast-3 |
appmesh.ap-southeast-3.amazonaws.com appmesh-envoy-management.ap-southeast-3.amazonaws.com appmesh.ap-southeast-3.api.aws appmesh-envoy-management.ap-southeast-3.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asia Pacific (Mumbai) | ap-south-1 |
appmesh.ap-south-1.amazonaws.com appmesh.ap-south-1.api.aws appmesh-envoy-management.ap-south-1.amazonaws.com appmesh-envoy-management.ap-south-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asie-Pacifique (Osaka) | ap-northeast-3 |
appmesh.ap-northeast-3.amazonaws.com appmesh-envoy-management.ap-northeast-3.amazonaws.com appmesh-envoy-management.ap-northeast-3.api.aws appmesh.ap-northeast-3.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asia Pacific (Seoul) | ap-northeast-2 |
appmesh.ap-northeast-2.amazonaws.com appmesh-envoy-management.ap-northeast-2.api.aws appmesh-envoy-management.ap-northeast-2.amazonaws.com appmesh.ap-northeast-2.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asie-Pacifique (Singapour) | ap-southeast-1 |
appmesh.ap-southeast-1.amazonaws.com appmesh-envoy-management.ap-southeast-1.api.aws appmesh.ap-southeast-1.api.aws appmesh-envoy-management.ap-southeast-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS |
Asia Pacific (Sydney) | ap-southeast-2 |
appmesh.ap-southeast-2.amazonaws.com appmesh-envoy-management.ap-southeast-2.api.aws appmesh-envoy-management.ap-southeast-2.amazonaws.com appmesh.ap-southeast-2.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Asia Pacific (Tokyo) | ap-northeast-1 |
appmesh.ap-northeast-1.amazonaws.com appmesh-envoy-management.ap-northeast-1.api.aws appmesh-envoy-management.ap-northeast-1.amazonaws.com appmesh.ap-northeast-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Canada (Central) | ca-central-1 |
appmesh.ca-central-1.amazonaws.com appmesh-envoy-management-fips.ca-central-1.api.aws appmesh.ca-central-1.api.aws appmesh-envoy-management.ca-central-1.api.aws appmesh-fips.ca-central-1.amazonaws.com appmesh-envoy-management.ca-central-1.amazonaws.com appmesh-fips.ca-central-1.api.aws appmesh-envoy-management-fips.ca-central-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS HTTPS |
Europe (Francfort) | eu-central-1 |
appmesh.eu-central-1.amazonaws.com appmesh.eu-central-1.api.aws appmesh-envoy-management.eu-central-1.amazonaws.com appmesh-envoy-management.eu-central-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Europe (Irlande) | eu-west-1 |
appmesh.eu-west-1.amazonaws.com appmesh-envoy-management.eu-west-1.api.aws appmesh-envoy-management.eu-west-1.amazonaws.com appmesh.eu-west-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Europe (Londres) | eu-west-2 |
appmesh.eu-west-2.amazonaws.com appmesh.eu-west-2.api.aws appmesh-envoy-management.eu-west-2.amazonaws.com appmesh-envoy-management.eu-west-2.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Europe (Milan) | eu-south-1 |
appmesh.eu-south-1.amazonaws.com appmesh-envoy-management.eu-south-1.api.aws appmesh-envoy-management.eu-south-1.amazonaws.com appmesh.eu-south-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Europe (Paris) | eu-west-3 |
appmesh.eu-west-3.amazonaws.com appmesh-envoy-management.eu-west-3.amazonaws.com appmesh-envoy-management.eu-west-3.api.aws appmesh.eu-west-3.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Europe (Espagne) | eu-south-2 |
appmesh.eu-south-2.amazonaws.com appmesh-envoy-management.eu-south-2.api.aws appmesh.eu-south-2.api.aws appmesh-envoy-management.eu-south-2.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS |
Europe (Stockholm) | eu-north-1 |
appmesh.eu-north-1.amazonaws.com appmesh.eu-north-1.api.aws appmesh-envoy-management.eu-north-1.api.aws appmesh-envoy-management.eu-north-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS |
Europe (Zurich) | eu-central-2 |
appmesh.eu-central-2.amazonaws.com appmesh-envoy-management.eu-central-2.amazonaws.com appmesh-envoy-management.eu-central-2.api.aws appmesh.eu-central-2.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Israël (Tel Aviv) | il-central-1 |
appmesh.il-central-1.amazonaws.com appmesh-envoy-management.il-central-1.amazonaws.com appmesh-envoy-management.il-central-1.api.aws appmesh.il-central-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Moyen-Orient (Bahreïn) | me-south-1 |
appmesh.me-south-1.amazonaws.com appmesh-envoy-management.me-south-1.api.aws appmesh-envoy-management.me-south-1.amazonaws.com appmesh.me-south-1.api.aws |
HTTPS HTTPS HTTPS HTTPS |
Amérique du Sud (São Paulo) | sa-east-1 |
appmesh.sa-east-1.amazonaws.com appmesh.sa-east-1.api.aws appmesh-envoy-management.sa-east-1.api.aws appmesh-envoy-management.sa-east-1.amazonaws.com |
HTTPS HTTPS HTTPS HTTPS |
Quotas de service
Nom | Par défaut | Ajustable | Description |
---|---|---|---|
Backends par nœud virtuel | Chaque région prise en charge : 50 | Non | Nombre de backends par nœud virtuel |
Processus Envoy connectés par passerelle virtuelle | Chaque Région prise en charge : 50 | Oui |
Nombre de processus Envoy connectés simultanément par passerelle virtuelle |
Processus Envoy connectés par nœud virtuel | Chaque Région prise en charge : 50 | Oui |
Nombre de processus Envoy connectés simultanément par nœud virtuel |
Routes de passerelle par passerelle virtuelle | Par région prise en charge : 10 | Oui |
Nombre de routes de passerelle par passerelle virtuelle |
Maillages par compte | Chaque région prise en charge : 15 | Oui |
Nombre de maillages par compte |
Routes par routeur virtuel | Chaque Région prise en charge : 50 | Oui |
Nombre de routes par routeur virtuel |
Passerelles virtuelles par maillage | Chaque région prise en charge : 3 | Oui |
Nombre de passerelles virtuelles par maillage |
Nœuds virtuels par maillage | Chaque région prise en charge : 200 | Oui |
Nombre de nœuds virtuels par maillage |
Routeurs virtuels par maillage | Chaque région prise en charge : 200 | Oui |
Nombre de routeurs virtuels par maillage |
Services virtuels par maillage | Chaque région prise en charge : 200 | Oui |
Nombre de services virtuels par maillage |
Objectifs pondérés par itinéraire | Chaque Région prise en charge : 10 | Non | Nombre de cibles pondérées par itinéraire |