1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Ok, so I discovered that after hitting some consistent requests during the defined evaluation period, data was loaded into the alarm. I can assume that this is due to the idle container features.
From the App Runner pricing page:
When your application is idle, you pay per GB of memory for provisioned container instances which keep your application warm and eliminate cold starts. When requests come in, your application responds in milliseconds, and you pay for the vCPU and memory consumed by your active container instances as your application is processing requests.
beantwortet vor einem Jahr
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren