Examples of using Edge-optimized in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Import an Edge-Optimized API Using the AWS CLI.
You cannot change a private API into an edge-optimized API.
Import an Edge-Optimized API Using the API Gateway Console.
You can migrate your custom domain name between edge-optimized and regional endpoints.
Import an Edge-Optimized API Using the API Gateway REST API.
The reference to an AWS-managed certificate for use by the edge-optimized endpoint for this domain name.
Set Up an Edge-Optimized Custom Domain Name for an API Gateway API.
If you set the endpoint type to EDGE or do not set the type at all,you create an edge-optimized custom domain name.
You can then remove the edge-optimized API custom domain name.
The edge-optimized domain certificate must be created in the us-east-1 region.
When you create a custom domain name for an edge-optimized API, API Gateway sets up a CloudFront distribution.
For an edge-optimized API and its custom domain name, the endpoint type is EDGE.
It may take up to 60 seconds to complete a migration between an edge-optimized custom domain name and a regional custom domain name in API Gateway.
As with an edge-optimized API, you can create a custom domain name for a regional API.
For the specified custom domain name, API Gateway returns the edge-optimized API host name as the distributionDomainName property value.
For edge-optimized endpoints, the Route 53 Hosted Zone ID is Z2FDTNDATAQYW2 for all the regions.
You must set a DNS record to point the edge-optimized custom domain name to this distribution domain name.
An edge-optimized custom domain name is created in a specific region and owned by a specific AWS account.
After the DNS record is set, you can remove the edge-optimized custom domain name by calling the update-domain-name command of AWS CLI.
To set up an edge-optimized API explicitly, you can set EDGE as the type of the endpointConfiguration.
From here on,you can follow the same instructions given in Set up an Edge-Optimized API Using AWS CLI Commands to set up methods and integrations for this API.
Notice that the edge-optimized hosted zone is independent of regions and the DNSName takes the value of the associated CloudFront distribution name.
If you are changing a public API from edge-optimized to regional or vice versa, note that an edge-optimized API may have different behaviors than a regional API.
To set up an edge-optimized custom domain name or to update its certificate, you must have a permission to update CloudFront distributions.
Similarly, you can run the same command to map an edge-optimized custom domain name to its associated CloudFront distribution with a different setup-dns-rescord.
You can migrate an edge-optimized custom domain name that is not in the us-east-1 region to a regional custom domain name by first requesting a new ACM Certificate from the region that is local to the API.
To use the AWS CLI to update a custom domain name from an edge-optimized endpoint to a regional endpoint or vice versa, call the update-domain-name command to add the new endpoint type and, optionally, call the update-domain-name command to remove the old endpoint type.
API Gateway supports edge-optimized custom domain names by leveraging Server Name Indication(SNI) on the CloudFront distribution.
After deploying your edge-optimized or regional API, you(and your customers) can invoke the API using the default base URL of the following format.
In contrast, to create an edge-optimized custom domain name, you set the required certificate ARN on the input property of certificateArn.