To setup Prodfiler on ECS two scripts should be run on a Linux/Mac (respect the order):
prodfiler-ecs-auth.sh: configures credentials to pull the
optimyze/pf-host-agentimage and IAM resources to consume the secret
prodfiler-ecs-task.sh: deploys a
DAEMONtask in an already-existing ECS cluster
Before installing Prodfiler, verify that your nodes meet the requirements. So far, the default Linux AMI 2 ships with an unsupported Linux kernel version (4.14); check the Amazon Linux 2 AMI release notes to verify support for the current kernel version.
Currently Prodfiler is available only on ECS clusters with EC2 launch type.
Fargate launch type does not allow deploying
DEAMON tasks and thus is not an option at the moment.
To run this script we suggest to use AWS credentials with the following policies attached:
Both scripts are not idempotent, so please be sure to run them with AWS credentials that are granted with the authorizations listed above. If the script fails during the execution, the resources created so far will have to be deleted manually for the script to succeed on the next run.
Scripts use AWS CLI v2, refer to the official documentation to set it up.
To see the help message, execute the scripts with
Follow the instructions in the
... > Instructions menu from the Prodfiler UI, switching to the ECS tab.
You will be guided through the execution of the scripts mentioned above.
The following describes how to change the default settings.
Pass the provided credentials as arguments to this script in order to access the private Docker image.
<PASSWORD> placeholder content with the token shown in the
Run this command from the root of the
./prodfiler-ecs-auth.sh --username optimyzeprodfilerbeta --password <PASSWORD>
It will create the secrets used by the ECS DAEMON task using AWS Secret Manager.
secretToken values visible in the Prodfiler web UI
when creating a new project.
The values are defined as environment variables in the deployment command visible in the UI,
they are called
To customize the setup, edit task.json.template as required by your environment.
Then run the script, passing the proper data as displayed in the
./prodfiler-ecs-task.sh --cluster-arn <YOUR_CLUSTER_ARN> \ --collection-agent "data-v2.run.prodfiler.com:443" \ --project-id <YOUR_PROJECT_ID> --version "v2.5.2" --tracers "all" --secret-token <YOUR_SECRET_TOKEN>
At this point Prodfiler Host Agent should be running in your ECS cluster and you should start seeing data in the UI.