Deployment Assets
Please look at the RapidFort Helm Chart AWS Deployment.
Please look at the RapidFort AWS Commercial Console Deployment.
This section describes issues that are commonly encountered by users.
When deploying RapidFort for the first time, the super administrator user should receive a confirmation email indicating that RapidFort has been successfully deployed.
The RapidFort application is expected to take at most 30 minutes to finish being deployed.
If the super administrator user does not receive an email after this time, please verify the following:
- The RapidFort Kubernetes deployment was successful (i.e. all pods in the RapidFort cluster are running and in healthy states)
- The correct email address was specified in the Kubernetes
secret.yamlfile (Kubernetes deployment) or User Data section (AMI deployment) - The RapidFort Kubernetes deployment has access to
public.ecr.aws/rapidfort - The RapidFort Kubernetes deployment has egress access to
email-smtp.us-east-1.amazonaws.comover port 574
SSL certificates must be added to the RapidFort application load balancer.
Hardening a stub image requires the runtime profile to be available. The runtime profile is generated when running and tracing the stub image. RapidFort must have the runtime profile to determine which files were used. Another option is to use workload tags and reuse the profile for a stub image that has already been traced.
Another potential root cause is that the environment in which the stub image was deployed does not have access to the RapidFort deployment.
Please run the following command in the environment in which the stub image has been deployed to verify connectivity to the RapidFort deployment:
nc -vz <rapidfort_host> 443
For more information, please refer to the following pages:
When running stub images, the
SYS_PTRACE Linux kernel capability must be added.For more information, please refer to the following page:
RapidFort requires egress access to
api.rapidfort.com over port 443 to download vulnerabilities database updates.Please run the following command in the RapidFort deployment to verify this:
nc -vz api.rapidfort.com 443
Please review the minimum requirements for installing the RapidFort command line interface tools. In particular, you will need the following:
- Linux, Mac OS X, or Windows Intel 64-bit client system
- Python 3.7 or later
- pip3
- Bash
- Docker or Podman Container Runtime