AWS Elastic Beanstalk

Install Raygun APM into the underlying Windows or Linux instances used by the Elastic Beanstalk environment.

Windows/IIS environments

Use the current signed Windows installer in an elevated instance provisioning step or a custom AMI. Then configure each IIS application pool with the Raygun Configuration Utility or the current Raygun Agent command line and restart the pool.

The current 3.x Agent does not ship the legacy rgc.exe CLI. Do not reuse older .ebextensions examples that download RaygunAgent-x64.msi from the uppercase /APM/latest path or call rgc -register and rgc -enable.

For repeatable image creation, pin an exact installer version. For rolling environments, verify the Agent and application configuration on the replacement instance before terminating the old instance.

Linux environments

Install the Agent from an instance provisioning hook or custom AMI:

curl -fsSL https://downloads.raygun.com/apm/install.sh | sudo sh

Add the variables from .NET on Linux profiler setup to the application service and restart it. The installer supports AMD64 and ARM64 on glibc 2.27 or newer.

Verify every replacement instance

Elastic Beanstalk can replace or scale instances automatically. Ensure each instance:

1. has a healthy Raygun Agent at http://127.0.0.1:18100/status;
2. gives the application its Raygun API key, stable profiler path, and, for ASP.NET Core, startup-hook path;
3. restarts the application after configuration; and
4. produces representative traces before it receives production traffic.

If the environment is created from an AMI, do not bake an application API key into a shared image. Inject it through the environment's approved secret or configuration mechanism.