AWS Blu Insights Terminals runs on the customer environment. This guide focuses on how to run the Terminals jar, but it can also be launched with Docker.
Make sure you requested the tool on Blu Age Toolbox of AWS Blu Insights before moving to the next sections
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket"
],
"Resource": [
"arn:aws:s3:::toolbox-terminals-bt"
]
},
{
"Effect": "Allow",
"Action": [
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::toolbox-terminals-bt/*"
]
}
]
}
Toolbox buckets are replicated on the us-east-1 and us-east-2 regions. To use these replicated buckets, append the region to the bucket name: e.g. s3://toolbox-terminals-bt-us-east-1
. Make sure to adapt your user or role policy accordingly.
aws s3 cp --recursive s3://toolbox-terminals-bt/latest
LOCAL_PATH
LOCAL_PATH
java -Dsecure.token=<random_token> -jar terminals-....jar
-Dsecure.token=test
.You can also set it as an environment variable: export SECURE_TOKEN=<token>
-Dserver.port=<port>
Create a Dockerfile with:
FROM amazoncorretto:17-alpine
COPY terminals-*.jar terminals.jar
CMD ["java", "-Dserver.port=80", "-jar", "/terminals.jar"]
docker build -t terminals .
docker run -p 80:80 -e SECURE_TOKEN=<random_token> terminals
The logs of the Terminals application are the CloudWatch logs of the ECS task that run it. We log by default messages of socket creation and termination, and data exchange. For more detailed logs, you can add an environment variable to the docker container named JAVA_NET_LOG_OPT
.
It points to a java option javax.net.debug=, and it takes values like all and ssl. For more information about debugging, you can visit ReadDebug and DebugBlog.