Examples of using Custom origin in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
The HTTPS port the custom origin listens on.
HTTPS Only- CloudFront uses only HTTPS to communicate with your custom origin.
If you're using a custom origin: Configure your origin server to handle all methods.
You can specify either a custom origin or an Amazon S3 origin in a single request; not both.
Do You Need Help Troubleshooting a Custom Origin?
Match Viewer- CloudFront communicates with your custom origin using HTTP or HTTPS, depending on the protocol of the viewer request.
You can identify the requests that are forwarded to your custom origin by CloudFront.
Custom origin- You can configure CloudFront to cache based on the value of any request header except the following.
You can use an SSL/TLS certificate from the following sources on your custom origin.
If you're using an Amazon EC2 server or another custom origin, review Using Amazon EC2 or Other Custom Origins. .
This topic containsinformation about how CloudFront processes responses from your custom origin.
You can't use an OAI when you switch from a custom origin to an Amazon S3 origin. .
We recommend that you store custom error pages in an Amazon S3 bucket even ifyou're using a custom origin.
The two options that CloudFront supports for connections with a custom origin are RSA and Elliptic Curve Digital Signature Algorithm ECDSA.
You can also make the media player available to end users in other ways, for example,using CloudFront and a custom origin.
If you use a custom origin, examine the application logs to ensure that your origin has sufficient resources, such as memory, CPU.
The process works basically the same way whether yourorigin is an Amazon S3 bucket or a custom origin such as an HTTP/S server.
If you need AWS to help you troubleshoot a custom origin, we probably will need to inspect the X-Amz-Cf-Id header entries from your requests.
You use the same URL format whether you store the content in Amazon S3 buckets or at a custom origin, like one of your own web servers.
When you're using a custom origin, the SSL/TLS certificate on your origin includes a domain name in the Common Name field, and possibly several more in the Subject Alternative Names field.
If you configure CloudFront to process all of the HTTP methods that it supports,CloudFront accepts the following requests from viewers and forwards them to your custom origin.
For information about installing an SSL/TLS certificate on your custom origin server, see Requiring HTTPS for Communication Between CloudFront and Your Custom Origin.
If the compressed file is not in the cache, CloudFront forwards the request to the origin server,which can be either an Amazon S3 bucket or a custom origin.
If you want to require HTTPS for communication between CloudFront and your custom origin, and you're using the domain name that CloudFront assigned to your distribution in the URLs for your objects for example, https: //d111111abcdef8.
Using Lambda@Edge can help you configure your CloudFrontdistribution to serve private content from your own custom origin, as an option to using signed URLs or signed cookies.
If you configure your custom origin to respond to requests only if they include a custom header, you can prevent users from bypassing CloudFront and submitting requests directly to your origin. .
When CloudFront requests an object from your Amazon S3 bucket or custom origin server, your origin sometimes returns an HTTP 4xx or 5xx status code, which indicates an error has occurred.