aws – GLU Global https://glu.global Innovation at Speed Thu, 25 Apr 2024 06:34:00 +0000 en-GB hourly 1 https://glu.global/wp-content/uploads/2022/01/cropped-favicon-1-32x32.png aws – GLU Global https://glu.global 32 32 AWS ECR configuration https://glu.global/glu-guide/aws-ecr-configuration/ Thu, 02 Feb 2023 11:23:19 +0000 https://glu.global/?post_type=ht_kb&p=4433 Configure GLU.Engine settings

To configure GLU.Engine settings for pushing Docker containers to an AWS ECR repository, follow these steps. Please refer to AWS ECR documentation for details (AWS ECR):

Step 1:

  • First a temporary token needs to be acquired through the AWS CLI command:  $ aws ecr get-login-password

Step 2:

  • Ensure that the server running the CLI commands has access to the AWS environment where the ECR repository is located. Use the aws configure command to set up access.
  • The following example shows how to view if the settings exist. Press return after each line and it will show you he value which has been set. 
$ aws configure
AWS Access Key ID [****************XXXD]:
AWS Secret Access Key [****************8996]:
Default region name [us-east-1]:
Default output format [json]:

Step 3:

  • Once the connection has been established then the get-login-password command can be used to get a password, which can be used in the GLUConsole DOCKER PASSWORD field.

$ aws ecr get-login-password
eyJwYXlsb2FkIjoiQm0zNStqa2JrMUZodVF2bDBLUFR0UkNuNnY5aFE1bU5Sekd5N1ZIN0grekg5QlJ3SUNod0RGVlQ1TnI5OVI5OW1EQTZoUG1vTVBvamFqVVBNZDJ
yc1hkK1o1aDYwczBpZTVrUktCSW54NGxFNnhzeHNYWHErWGJ2enZkNjVYUzVQRlhxY2NFV1R0QThuUTR6Tk1VQjhYVzR3dlZ6RFYrVXRBNURVNCtHVWltTDdaTmhYQ0
JzNW9DNWNqOWZxLzVEVG1sT1lSUlFlbXp6SlRSY1FZR3VQMk5kSEtiWHUxZGxyWFdPRWI1VkZrWVFISUFtN2lYQlVQRjRZei9XdHZ0QTEzS3VGa25Kd1RwOHBQL0FHe
m9NVk14YXRFZVdVVCtKSi9pNWhldHZlTGwrQXgzSDkwSVQ1UmhpZWxZZ3NIK0xPSTNuT24vZmxSTmg2XXXXXXXXXXXXXXXXXXXXXXXHVMSVRrTUYrckMvUGZ6
T2JITUZ0S2F1eU8wQUg2dW52eWNyVzYrQVZ5M0JkNFpURzdSbHJ4R1hsd0QyQjlQdW5mTFBWNi9HaWNmUlRFQ2VKYUUvNlJvTW82ZHRDN3BCVmVHRzNidkRkcE1pckM
2Y3plMjVMcGpYNlU5QXVyUTA4MGowUHc0R2IxOWp5RWwyYldQQWgwa0NvWGlHNDFlWUJmOVdGeWxWQkdJK1I5cVhvOVJjdG9BbHdobGZ4WFRNSHJYKzR2U0xYNVFpaV
UyRExPYW5JTEJENGowK0pXVUZvZXBXeHNOQ2d6WVlVWlkvTlQyS2ZnYU1FKzBuVUVmUGcyUks2TXpDZHoxWGVwQUZpV3YrVUFNSDFtckQ3M2E1dkZLQTBiWGdSLzRKc
0JXXXXXXXXXXXXXXXXXXXXSTjM5dGR5ekZNV2pkRkxMZjZyRTAzRjBVZUFYQ0RQdVJSenAva1NjVDE4a1NXMmFNb201T1ArOFFaZmdnZWNDdnFzMG1p
bDVLVm1ialFsRFNZQWdDRUJSWm9nSGRFNkRiQTAxbEQ1Ujkya2JsRWYvREhiWHdDb0hLWWdNNE9ON1ozQmFJZ1hQK3Z6VFJwMEFoL3o5bmN3Mkd4REVab0NrU0taRlR
Nb2NxWEVsWjE0S21ONmh1M0xpS083UjhjMWxwNW1GaFBvOXFidmNaRU51Ym0zSFBSRVpEblpKYW1aS0lwbGw5eXRGRDJEL2dka3hpSWhzdkFUbUxDZDdsbHlSL3JCQj
I0RVMvTzNkdDEwcTEweUU2OEZyTXFOcGVlMDB4MmlmMWhHWXhVNUoybEJnendNR3JVQXNwYm9GVmcvM0IwODJ2TGMrM0p0ZDZ3S09JWU8wV2RNYWxrbmtHcEoyL0Q2R
VhyOTAzR1EwOW94U0kvUTZvKzhrK0E9PSIsImRhdGFrZXkiOiJBUUVCQUhod20wWWFJU0plUnRKbTVuMUc2dXFlZWtYdW9YWFBlNVVGY2U5UnE4LzE0d0FBQUg0d2ZB
WUpLb1pJaHZjTkFRY0dvRzh3YlFJQkFEQm9CZ2txaGtpRzl3MEJCd0V3SGdZSllJWklBV1VEQkFFdU1CRUVESmtIVDBiMFNPUDRXSWhqdGdJQkVJQTdaM1lHMnZqd0V
jUTY5QkNBeWRpdTFBeTRKZ041b3h2UG80anp0K2VSWGkxQnFOSGZqaWJDNEFtUCtiY1dPY0g3YjRZbGNkcko0eHBqM3JnPSIsInZlcnNpb24iOiIyIiwidHlwZSI6Ik
RBVEFfS0VZIiwiZXhwaXJhdGlvbiI6MTY2NTUzODA0MH0=


Step 4:

  • A = DOCKER IMAGE REPOSITORY , to be entered in the GLU.Engines Settings below
  • B = Must match the GLU.Engine name (See screen shot below, please also note the constraint applied to the GLU.Engine name by AWS i.e. a name like GLU_USSD_Demo will not work.)
  • C = DOCKER URL , to be entered in the GLU.Engines Settings below



NOTE: Constraint applied by AWS on the GLU.Engine name if AWS ECR is to be used.



All below the fields are mandatory:

nameValueDescription
DOCKER URL42588888888835.dkr.ecr.us-east-1.amazonaws.compath to the docker.io instance (C)
DOCKER USERNAMEAWSFor AWS ECR Repos. this will always be “AWS”
SKIP DOCKERfalsetrue or false, When set to false docker will be used.
DOCKER PASSWORD{Long string of characers from above}The token generated by the aws ecr get-login-password
DOCKER IMAGE REPOSITORYgluwarein docker the repository name (A)






In the example below, when this is configured and a build is executed the GLU.Console will execute the command below at the end of the build process. This will then push the Docker container 1.5-SNAPSHOT to the AWS ECR repo demo.

  • $ push 42558888888535.dkr.ecr.us-east-1.amazonaws.com/gluware/demo:1.5-SNAPSHOT

Useful AWS commands

CommandDescription
aws ecr get-login-password | docker login –username AWS –password-stdin 92266666477.dkr.ecr.us-east-1.amazonaws.comto be used to log into the AWS instance of the ECR
aws ecr get-login-password If connected to AWS it will display the password, which needs to be put in the GLU Application Settings page.
aws ecr list-images –repository-name gluware/demoUseful to list the repositories which are held by the ECR, also to confirm connection is correct.
]]>