When you create a Deployment, your container is generating logs. You have the possibility to save these logs to an S3 Bucket of your choice, once the deployment is finished.
To accomplish this, you will need first to link your App Version to your Endpoint Storage. You will need to go to the App Version detail page, under the Container Logs Storage Management section.
Enable the switch box and select your Endpoint Storage in the select box. Be sure to hit the save button. Once it is saved, you can press the "Test" button.
It will show the same box as when you test it in the setup of your Endpoint Storage.
That's it, every Deployment with this App Version will now store the container logs into your S3 Bucket, if available on its location. Some location does not support container logs, but this is a minority and you will probably not be concerned.
The path in your S3 Bucket will look like this.
- The first part of your client email, most S3 browser don't like "@"
- The name of your Endpoint Storage
- app / app version / container_log
- The date YYYY-MM-DD
You can create multiple Endpoint Storage with the same S3 Bucket, but with a different name. That way you could have multiple directories for multiple environments if you wanted.
You can also specify if you want to store your container logs with your Deployment request, even if it is not activated or set up in your App Version. Necessarily, you must have previously created a functional Endpoint Storage.
This can be useful when you are testing and don't want all of your deployments logs to be sent to a storage. The opposite is also true, if you have enabled log storage from your App Version, you can disable it with your Deployment request.
Another convenient way to use it is when your deployment is terminated. This way, if you have the means to determine that something went wrong inside your container, you can ask to save the container logs. You can use this option with the Deployment stop and Self stop route.
You can check our API Documentation API Documentation for more detail on parameters for the deploy and stop request.