1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
---
title: Building for AWS EC2 (arm64 or x86-64)
---
Building an image for emulation allows you to simulate your
image without actual target hardware. In this case using an EC2 instance.
This section describes the steps you need to take to build the
AGL demo image for emulation using EC2 either for arm64 or x86-64.
In the commanline examples below, we will focus on aws-ec2-arm64 primarily.
If you need x86-64, then replace it with aws-ec2-x86-64 likewise.
## 1. Making Sure Your Build Environment is Correct
The
"[Initializing Your Build Environment](./04_Initializing_Your_Build_Environment.md)"
section presented generic information for setting up your build environment
using the `aglsetup.sh` script.
If you are building the AGL demo image for emulation, you need to specify some
specific options when you run the script:
**Sample Qt based IVI demo :**
```sh
$ source meta-agl/scripts/aglsetup.sh -f -m aws-ec2-arm64 -b build-aws-ec2 agl-demo agl-devel
$ echo "# reuse download directories" >> $AGL_TOP/site.conf
$ echo "DL_DIR = \"$HOME/downloads/\"" >> $AGL_TOP/site.conf
$ echo "SSTATE_DIR = \"$AGL_TOP/sstate-cache/\"" >> $AGL_TOP/site.conf
$ ln -sf $AGL_TOP/site.conf conf/
```
**IVI-EG Flutter based demo :**
```
$ source meta-agl/scripts/aglsetup.sh -f -m aws-ec2-arm64 -b build-aws-ec2 agl-demo agl-devel
$ echo "# reuse download directories" >> $AGL_TOP/site.conf
$ echo "DL_DIR = \"$HOME/downloads/\"" >> $AGL_TOP/site.conf
$ echo "SSTATE_DIR = \"$AGL_TOP/sstate-cache/\"" >> $AGL_TOP/site.conf
$ ln -sf $AGL_TOP/site.conf conf/
```
The "-m" option specifies the "aws-ec2-arm64" machine.
The list of AGL features used with script are appropriate for development of
the AGL demo image. For production use, you need to omit agl-devel and tailor your image.
## 2. Using BitBake
Start the build using the `bitbake` command.
**NOTE:** An initial build can take many hours depending on your
CPU and and Internet connection speeds.
The build also takes approximately 100G-bytes of free disk space.
**Sample Qt based IVI demo :**
The target is `agl-ivi-demo-qt`.
```
$ time bitbake agl-ivi-demo-qt
```
By default, the build process puts the resulting image in the Build Directory and further exporting that as `$IMAGE_NAME`:
```
<build_directory>/tmp/deploy/images/aws-ec2-arm64/agl-ivi-demo-qt-aws-ec2-arm64.rootfs.wic.vhd
$ export IMAGE_NAME=agl-ivi-demo-qt
```
**IVI-EG Flutter based demo :**
The target is `agl-ivi-demo-flutter`.
```
$ time bitbake agl-ivi-demo-flutter
```
By default, the build process puts the resulting image in the Build Directory and further exporting that as $IMAGE_NAME:
```
<build_directory>/tmp/deploy/images/aws-ec2-arm64/agl-ivi-demo-flutter-aws-ec2-arm64.rootfs.wic.vhd
$ export IMAGE_NAME=agl-ivi-demo-flutter
```
## 3. Deploying the AGL Demo Image
Deploying the image consists of uploading the image to S3 and
conversion to to an AMI image. The whole process is done using
a script out of meta-aws . Next you need to start a new instance
using your new image.
The image is setup to expose its screen over rdp. This is ok for
development, but you need to keep security in mind when configuring
the EC2 security groups and/or tunnel over ssh.
### 3.1 Uploading using create-ec2-ami.sh
The script required to upload the resulting image is part of meta-aws in the subfolder scripts/ec2-ami/.
**It has a few requirements that you need to setup first.**
**These are documented in the [Readme there](https://github.com/aws4embeddedlinux/meta-aws/blob/scarthgap/scripts/ec2-ami/README.md).**
**Read it and set it up accordingly.**
The script itself is called creat-ec2-ami.sh and takes 4 arguments:
* your S3 bucket name
* the size of the AMI (don't make it too small)
* the target image name
* the machine name
```
Example run
../bsp/meta-aws/scripts/ec2-ami/create-ec2-ami.sh my_s3_bucket 8 agl-ivi-demo-flutter aws-ec2-arm64
```
After this process is complete, your image is available as AMI to you (only to you).
### 3.2 Configuring within AWS EC2
In your EC2 dashboard go the the same region as you configured the upload for,
select "Launch instance" and enter a name.
Select under "My AMIs" the uploaded AGL image in question. Select an instance type
that is big enough (>= 4GB RAM, 8GB RAM recommended).
Select your key pair, select the security group.
Finally start the instance.
**Note1: AWS serial console does not help as you have no root password available until you reset it.**
**Note2: You cannot connect as 'root' (as shown in the connect tab) - you have to substitute 'root' with 'user'.**
**Note3: There is no web output, you need to use RDP. See below ...**
### 3.3 Connecting via RDP
For security reasons, you should always tunnel over ssh.
For this, connect using 'ssh -i "yourkey.pem" -L 3389:localhost:3389 user@publicIPofSERVER' .
Then use an rdp client and connect to 'localhost' .
### 3.4 Security considerations
As mentioned above, do not expose port 3389 to the internet by opening up the port.
|
