Get email notifications whenever LocalStack creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
All Systems Operational
About This Site
LocalStack Status Page
Uptime over the past 90 days. View historical uptime.
LocalStack Platform
?
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Sep 12, 2024
No incidents reported today.
Sep 11, 2024
No incidents reported.
Sep 10, 2024
No incidents reported.
Sep 9, 2024
No incidents reported.
Sep 8, 2024
No incidents reported.
Sep 7, 2024
No incidents reported.
Sep 6, 2024
Resolved -
We are reaching out with good news about the localhost.localstack.cloud certificate issue being resolved.
Current status: Incident resolved with a new LocalStack patched version 3.7.2. No further service degradation observed for the past 48 hours.
Important:
New LocalStack version: All relevant fixes are applied in the new patched version 3.7.2. Make sure to update your LocalStack image with the latest version by using latest or 3.7.2 tag.
Older LocalStack versions: Fixes are not applied to older versions of LocalStack, so customers using these may still encounter certificate revocation issues. If you experience this, please update to the latest version or follow the steps outlined in our documentation.
Clear cached certificates: If you continue to experience certificate revocation issues with the latest LocalStack version, please ensure that cached certificates are cleared from your host machine.
Sep 6, 13:57 UTC
Current status: Incident resolved with a new LocalStack patched version 3.7.2. No further service degradation observed for the past 48 hours.
Important:
New LocalStack version: All relevant fixes are applied in the new patched version 3.7.2. Make sure to update your LocalStack image with the latest version by using latest or 3.7.2 tag.
Older LocalStack versions: Fixes are not applied to older versions of LocalStack, so customers using these may still encounter certificate revocation issues. If you experience this, please update to the latest version or follow the steps outlined in our documentation.
Clear cached certificates: If you continue to experience certificate revocation issues with the latest LocalStack version, please ensure that cached certificates are cleared from your host machine.
Sep 6, 13:57 UTC
Update -
We have good news on the ongoing issue with the localhost.localstack.cloud certificate.
Current status: No service degradation observed for the past 24 hours. Incident under control with short and midterm solutions implemented in the latest LocalStack version.
We continue to monitor the behavior and actively work on a long-term solution.
Sep 5, 11:39 UTC
Current status: No service degradation observed for the past 24 hours. Incident under control with short and midterm solutions implemented in the latest LocalStack version.
We continue to monitor the behavior and actively work on a long-term solution.
Sep 5, 11:39 UTC
Update -
We are reaching out with another update on the ongoing issue with the localhost.localstack.cloud certificate.
Current status: Incident contained, with temporary workarounds. We continue to work on a long-term solution.
Update
New LocalStack version (v3.7+): We strongly recommend updating to the latest LocalStack version for the most reliable and seamless experience.
Older LocalStack versions
CI/CLI usage: Older images were encountering issues downloading the certificate from GitHub and the CDN, resulting in a fallback to a self-signed certificate that affected CI/CLI functionality. We’ve implemented a fix to restore certificate downloads from GitHub, resolving the CI/CLI issues with older LS images.
Web App usage: If you continue to experience certificates being revoked issues, previously mentioned workarounds still apply.
Temporary workarounds:
1. Set the environment variable SKIP_SSL_CERT_DOWNLOAD=1 to use a self-signed SSL certificate.
2. Use http:// instead of https:// where possible.
Long-term solution: We continue working on a permanent fix and will update you as we progress.
We continue to work on a long-term solution and will keep you updated.
Sep 4, 12:20 UTC
Current status: Incident contained, with temporary workarounds. We continue to work on a long-term solution.
Update
New LocalStack version (v3.7+): We strongly recommend updating to the latest LocalStack version for the most reliable and seamless experience.
Older LocalStack versions
CI/CLI usage: Older images were encountering issues downloading the certificate from GitHub and the CDN, resulting in a fallback to a self-signed certificate that affected CI/CLI functionality. We’ve implemented a fix to restore certificate downloads from GitHub, resolving the CI/CLI issues with older LS images.
Web App usage: If you continue to experience certificates being revoked issues, previously mentioned workarounds still apply.
Temporary workarounds:
1. Set the environment variable SKIP_SSL_CERT_DOWNLOAD=1 to use a self-signed SSL certificate.
2. Use http:// instead of https:// where possible.
Long-term solution: We continue working on a permanent fix and will update you as we progress.
We continue to work on a long-term solution and will keep you updated.
Sep 4, 12:20 UTC
Monitoring -
Hello,
We are reaching out with another update on the ongoing issue with the localhost.localstack.cloud certificate.
Current status:
Incident contained: We’ve implemented short-term fixes to contain the issue. While the issue is contained, the incident isn’t fully resolved yet.
Temporary workarounds: If you continue to experience certificate revocation issues, previously mentioned workarounds still apply:
1. Set the environment variable SKIP_SSL_CERT_DOWNLOAD=1 to use a self-signed SSL certificate.
2. Use http:// instead of https:// where possible.
Long-term solution: We’re working on a permanent fix and will update you as we progress.
Recent issues:
DNS resolution: Some customers experienced DNS issues from yesterday afternoon until this morning (CET). This has been fixed, and certificate renewals should no longer impact DNS resolution.
Thank you for your patience and understanding as we work through this. Please feel free to reach out if you have any questions or concerns.
Sep 3, 14:54 UTC
We are reaching out with another update on the ongoing issue with the localhost.localstack.cloud certificate.
Current status:
Incident contained: We’ve implemented short-term fixes to contain the issue. While the issue is contained, the incident isn’t fully resolved yet.
Temporary workarounds: If you continue to experience certificate revocation issues, previously mentioned workarounds still apply:
1. Set the environment variable SKIP_SSL_CERT_DOWNLOAD=1 to use a self-signed SSL certificate.
2. Use http:// instead of https:// where possible.
Long-term solution: We’re working on a permanent fix and will update you as we progress.
Recent issues:
DNS resolution: Some customers experienced DNS issues from yesterday afternoon until this morning (CET). This has been fixed, and certificate renewals should no longer impact DNS resolution.
Thank you for your patience and understanding as we work through this. Please feel free to reach out if you have any questions or concerns.
Sep 3, 14:54 UTC
Update -
Hello,
We wanted to provide an update on the ongoing issue with the localhost.localstack.cloud certificate. Unfortunately, the incident is still active, and we understand the challenges this has presented. We are committed to resolving this as quickly as possible and want to keep you informed about our progress.
Current Progress
Increased Certificate Re-Issuance Frequency: We have increased the frequency of re-issuing the certificate to once every hour. This should help in ensuring that the latest versions of LocalStack have a valid certificate available, although we recognize this is a temporary measure.
Medium and Long-Term Solutions: We are actively working on several medium and long-term strategies to prevent this issue from recurring. We will make sure to provide more updates on those once they are in place.
We understand the ongoing nature of this issue is frustrating, and we sincerely apologize for the inconvenience. Our team is working diligently to resolve the problem and to ensure the long-term reliability of LocalStack.
Thank you for your continued patience and understanding. Please don’t hesitate to contact us with any questions or to discuss specific concerns.
Sep 2, 13:01 UTC
We wanted to provide an update on the ongoing issue with the localhost.localstack.cloud certificate. Unfortunately, the incident is still active, and we understand the challenges this has presented. We are committed to resolving this as quickly as possible and want to keep you informed about our progress.
Current Progress
Increased Certificate Re-Issuance Frequency: We have increased the frequency of re-issuing the certificate to once every hour. This should help in ensuring that the latest versions of LocalStack have a valid certificate available, although we recognize this is a temporary measure.
Medium and Long-Term Solutions: We are actively working on several medium and long-term strategies to prevent this issue from recurring. We will make sure to provide more updates on those once they are in place.
We understand the ongoing nature of this issue is frustrating, and we sincerely apologize for the inconvenience. Our team is working diligently to resolve the problem and to ensure the long-term reliability of LocalStack.
Thank you for your continued patience and understanding. Please don’t hesitate to contact us with any questions or to discuss specific concerns.
Sep 2, 13:01 UTC
Identified -
Hello,
We wanted to provide an update on the ongoing issue with the localhost.localstack.cloud certificate. Unfortunately, the issue persists, and we have identified that the certificates are still being revoked. However, we want to assure you that this issue is not due to any particular security breach, and we are actively working on a permanent solution. In the meantime, we recommend the following temporary workarounds to mitigate the impact:
1. Disable Certificate Download: To prevent downloading a revoked certificate, set the environment variable 'SKIP_SSL_CERT_DOWNLOAD=1'. This will cause LocalStack to use a self-signed SSL certificate. Additionally, it’s important to clear the cached certificate from your host machine. This can be done by deleting the cached certificate file. For example, on Linux systems, you can locate and remove the file at '~/.cache/localstack/volume/cache/server.test.pem'. The exact path may differ depending on your operating system and how you’ve started LocalStack. Please refer to our documentation for specific instructions.
2. Use HTTP Instead of HTTPS: Where possible, use 'http://' instead of 'https://' to avoid issues related to the revoked certificates. This workaround works with most browsers. However, Safari requires additional steps:
- Safari Users: To make this work, you’ll need to first navigate to the page in a new tab and accept the security warning. To do this, make sure that LocalStack is started with 'SKIP_SSL_CERT_DOWNLOAD=1' and that you have cleared the cached certificate as mentioned above. Once you’ve accepted the warning, you should be able to proceed.|
We understand the inconvenience this may cause and sincerely apologize for any disruption this has brought to your workflow. Rest assured, resolving this issue remains our top priority, and we appreciate your patience and understanding. We are committed to providing you with regular updates as we progress, should you have any questions or need further assistance, please do not hesitate to reach out
Aug 30, 09:49 UTC
We wanted to provide an update on the ongoing issue with the localhost.localstack.cloud certificate. Unfortunately, the issue persists, and we have identified that the certificates are still being revoked. However, we want to assure you that this issue is not due to any particular security breach, and we are actively working on a permanent solution. In the meantime, we recommend the following temporary workarounds to mitigate the impact:
1. Disable Certificate Download: To prevent downloading a revoked certificate, set the environment variable 'SKIP_SSL_CERT_DOWNLOAD=1'. This will cause LocalStack to use a self-signed SSL certificate. Additionally, it’s important to clear the cached certificate from your host machine. This can be done by deleting the cached certificate file. For example, on Linux systems, you can locate and remove the file at '~/.cache/localstack/volume/cache/server.test.pem'. The exact path may differ depending on your operating system and how you’ve started LocalStack. Please refer to our documentation for specific instructions.
2. Use HTTP Instead of HTTPS: Where possible, use 'http://' instead of 'https://' to avoid issues related to the revoked certificates. This workaround works with most browsers. However, Safari requires additional steps:
- Safari Users: To make this work, you’ll need to first navigate to the page in a new tab and accept the security warning. To do this, make sure that LocalStack is started with 'SKIP_SSL_CERT_DOWNLOAD=1' and that you have cleared the cached certificate as mentioned above. Once you’ve accepted the warning, you should be able to proceed.|
We understand the inconvenience this may cause and sincerely apologize for any disruption this has brought to your workflow. Rest assured, resolving this issue remains our top priority, and we appreciate your patience and understanding. We are committed to providing you with regular updates as we progress, should you have any questions or need further assistance, please do not hesitate to reach out
Aug 30, 09:49 UTC
Sep 5, 2024
Sep 4, 2024
Sep 3, 2024
Sep 2, 2024
Sep 1, 2024
No incidents reported.
Aug 31, 2024
No incidents reported.
Aug 30, 2024
Aug 29, 2024
Resolved -
We have implemented changes that should resolve the issue with the revoked certificate. These changes are incorporated in LocalStack version 3.7.0.
To update your LocalStack container image to the latest version, or specifically to version 3.7.0, you can pull the latest image by using the following command:
```
docker pull localstack/localstack-pro:latest
```
Or, if you prefer to use a tagged version:
```
docker pull localstack/localstack-pro:3.7.0
```
Should you have any more questions or require further assistance, please do not hesitate to contact us on Slack or via support email.
Aug 29, 12:57 UTC
To update your LocalStack container image to the latest version, or specifically to version 3.7.0, you can pull the latest image by using the following command:
```
docker pull localstack/localstack-pro:latest
```
Or, if you prefer to use a tagged version:
```
docker pull localstack/localstack-pro:3.7.0
```
Should you have any more questions or require further assistance, please do not hesitate to contact us on Slack or via support email.
Aug 29, 12:57 UTC
Monitoring -
We have resolved the issue and the certificates should be valid and active now for the latest community image (localstack/localstack:latest). The fix for the Pro image (localstack/localstack-pro) would be available latest by tomorrow (August 29th).
We apologize again for any inconvenience, and thank you for your patience. We've put measures in place to prevent this type of issue from happening again in the future.
Aug 28, 19:16 UTC
We apologize again for any inconvenience, and thank you for your patience. We've put measures in place to prevent this type of issue from happening again in the future.
Aug 28, 19:16 UTC
Identified -
We are currently investigating an incident regarding the revocation of our `localhost.localstack.cloud` certificate used in the LocalStack container. A revoked certificate may cause certain browsers and tools to distrust it, which can cause issues with HTTPS/TLS communication with the LocalStack APIs. Consequently, this could lead to errors when using the LocalStack Web Application, Desktop Application, or any other tools that rely on an HTTPS connection.
As a temporary workaround, we recommend using HTTP connections when accessing LocalStack. We will keep you informed and provide an update as soon as the issue is resolved. Thank you for your understanding and patience.
Aug 28, 08:47 UTC
As a temporary workaround, we recommend using HTTP connections when accessing LocalStack. We will keep you informed and provide an update as soon as the issue is resolved. Thank you for your understanding and patience.
Aug 28, 08:47 UTC