Over the years, the Aptible product teams have learned that a vast number of teams would benefit from not just having greater visibility into the security safeguards Aptible has in place across different aspects of the infrastructure, but also get insights to understand what they need to do to further improve their posture to reach a compliance goal.
Broadly speaking, two levels of access can be granted to Users through Aptible Roles on a per-Environments basis
We've released the newest version of the Aptible CLI -
v0.19.1 that adds more command line functionality to help you better automate management of Log Drains, Metric Drains and Database Endpoints.
Aptible Deploy has always allowed developers to trigger a backup, something we call a manual backup.
Aptible Deploy comes with built-in support for easily aggregating your container, SSH session and HTTP(S) endpoint logs and routing them to your destinations of choice for record-keeping and future analysis, be it in popular external destinations like Datadog, SumoLogic and PaperTrail, or to a self-hosted Elasticsearch database.
We are very excited to introduce a new command for the Aptible CLI :
aptible db:modify. This command lets you make modifications to your databases without requiring any restarts.
We understand that reviewing your backups regularly is essential for business continuity planning and optimizing your infrastructure spend.
All new Aptible Deploy databases created today - either newly provisioned or restored from backup - will default to using gp3 volumes. This new volume type provides a baseline IOPS performance of 3,000 IOPS without regard for disk size. For most databases, this will be a large improvement on existing performance. However, some larger databases (bigger than 1 TB) may require more IOPS. If you would like to provision more than 3000 IOPS, reach out to [email protected] and we can help you with this - up to 16,000 IOPS.
Aptible has released support for version 7 of the Elasticsearch Database type. This major version includes: