You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/cca-veraison-aws/domain-and-cert.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,20 +12,22 @@ Veraison provides cloud services for attestation. These services are published o
12
12
13
13
[Route53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Welcome.html) is an AWS service that allows you to register and manage domains. In order to create your Veraison deployment in AWS, you first need to choose a domain name and register it with Route53.
14
14
15
-
### Choosing your domain name
15
+
### Choosing Your Domain Name
16
16
17
17
Your domain name must be unique and specific to your Veraison deployment. Remember that this domain name is for creating public internet services, so it cannot clash with any other domains that exist on the public internet.
18
18
19
19
In this Learning Path, you will use `example-veraison.com` as an illustrative example of a domain name. However, do not use this name for your own deployment. Choose your own name, and use it in place of the example as you progress through the Learning Path.
20
20
21
-
### Registering your Domain with Route53
21
+
### Registering Your Domain with Route53
22
22
23
23
The easiest way to create your domain is using the Route53 dashboard in the AWS Management Console:
24
24
25
25
* Using your web browser and AWS account credentials, sign into the console and search for the Route53 service. This takes you to the Route53 dashboard.
26
26
* Locate the domain registration option, which looks something like the image below. Remember to use your own domain name where highlighted, not the `example-veraison.com` domain.
27
27
28
-
**Note:** If you have an existing domain and you wish to transfer it into Route53, instead of creating a new domain, you can use this option as well as shown below. Otherwise, the instructions here assume that you are creating a new domain.
28
+
{{% notice Note %}}
29
+
If you have an existing domain, you can transfer it into Route53 instead of registering a new one, as shown below. Otherwise, the instructions here assume that you are creating a new domain.
30
+
{{% /notice %}}
29
31
30
32

31
33
@@ -35,8 +37,8 @@ Route53 charges an annual fee for domain registration, which varies depending on
35
37
36
38
## Request Your Domain Certificate
37
39
38
-
### What is a Domain Certificate?
39
-
Veraison publishes secure cloud services that can be reached on the internet using HTTPs. You'll need a certificate for your domain to help users trust and securely connect to your Veraison services.
40
+
### Why Do I Need a Domain Certificate?
41
+
Veraison publishes secure cloud services that can be reached on the internet using HTTPs. You need a domain certificate so users can securely and confidently connect to your Veraison services.
40
42
41
43
### Requesting a Certificate with AWS Certificate Manager
42
44
You can use the [AWS Certificate Manager (ACM)](https://aws.amazon.com/certificate-manager/) to issue a certificate for your domain:
@@ -47,11 +49,13 @@ You can use the [AWS Certificate Manager (ACM)](https://aws.amazon.com/certifica
47
49
48
50

49
51
50
-
On the first page of the certificate wizard, select **public certificate**, then click **Next**.
52
+
On the first page of the certificate wizard, select **Request a public certificate**, then click **Next**.
51
53
52
54

53
55
54
-
The next page of the wizard is for setting other properties of the certificate, starting with the domain name. The primary domain name of the certificate must precisely match the domain name that you registered with Route53 in the previous step. However, the Veraison deployment also creates a number of named services nested within that primary domain. In order for the certificate to adequately cover all of those named services, you need to give the certificate an additional name, which uses an asterisk (*) wildcard as shown below. Remember, once again, substitute your chosen domain name to use in place of `example-veraison.com`.
56
+
The next page of the wizard is for setting other properties of the certificate, starting with the domain name. The primary domain name of the certificate must precisely match the domain name that you registered with Route53 in the previous step. However, the Veraison deployment also creates a number of named services nested within that primary domain.
57
+
58
+
In order for the certificate to adequately cover all of those named services, you need to give the certificate an additional name, which uses an asterisk (*) wildcard as shown below. Remember, once again, substitute your chosen domain name to use in place of `example-veraison.com`.
55
59
56
60
Use the **Add another name to this certificate** button to create the secondary name with the wildcard.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/cca-veraison-aws/use-verifier.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,10 +9,10 @@ layout: learningpathall
9
9
## Use Your AWS Deployment to Verify a CCA Attestation Token
10
10
Now that your Veraison services are deployed into AWS and initialized with endorsements for the CCA reference platform, you are ready to make use of the verification service to verify a CCA attestation token.
11
11
12
-
To do this, you should follow the steps set out in the Learning Path [Get Started with CCA Attestation and Veraison](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-veraison/). Follow the steps in that Learning Path exactly, except you'll use your AWS-hosted Veraison deployment instead of Linaro's service.
12
+
To do this, you should follow the steps set out in the Learning Path [Get Started with CCA Attestation and Veraison](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-veraison/). Follow the steps in this Learning Path exactly, except you'll use your AWS-hosted Veraison deployment instead of Linaro's service.
13
13
14
14
The URL for the Veraison server provided by Linaro is `https://veraison.test.linaro.org:8443`.
15
15
16
-
Instead of using this URL, you should use the URL for your Veraison service, which will be of the form `https://services.example-veraison.com:8443`, although you need to replace `example-veraison.com` with your own registered AWS domain.
16
+
Instead of this URL, use the one for your own Veraison service, which will be of the form `https://services.example-veraison.com:8443`, although you need to replace `example-veraison.com` with your AWS domain.
17
17
18
18
Apart from this URL change, all other steps in the Learning Path remain the same.
0 commit comments