7 results found
-
Ability to shutdown a service that has privatelink configured, without breaking any config or deleting the privatelink.
As an Aiven customer
I want to be able to decouple privatelink configuration from the service lifecycle
so that I can shut down the service without having to delete the privatelink16 votes -
Ability to add additional networks to existing VPC
As a customer, I want the ability to add networks to my Aiven VPC, so that I can easily extend my existing networks, or move my services to a different network.
8 votes -
Google PSC multiple connect endpoints
As a customer, I want Aiven to expand the number of possible endpoints to connect to using Google PSC, so that I can connect more of my applications and services together.
6 votes -
IP whitelisting with expiration
As an Aiven user,
I want to have the ability to whitelist an IP address for a limited time, eg. in hours, so that I can access the database only within this specified window. The whitelist should automatically update once that time is up.
This would give database access only when needed, and would be beneficial for both network efficiency and security as the whitelist is kept as small as possible, thus also reducing potential attack surface.5 votes -
Choose a custom port
As DBA
I want to be able to choose a custom service port
so that I can migrate databases to Aiven without changing the port in the applications connection string.
In addition, this would help to avoid issues with the migration because of wrong ports.5 votes -
Automatically Allocate Static IP addresses
As IT Administrator
I want to have Aiven manage the number of static IP addresses I need for my services.
so that I can not have to deal with it.
In addition, it would be ideal if when creating a service there was just a flag for "Use Static IPs". This is most notable when using privatelink on Azure, as there are potentially a lot of static IPs to be created.3 votesToday, you can only manage static IPs via CLI and API. We are adding two things into the Console UI:
- Management of static IPs (along with more networking features).
- Building of an end-to-end solution at once which will also provision static IPs.
The second item is prioritized, however the first is not yet.
-
Private DNS Support for AWS PrivateLink
Users would like to use the private DNS feature with their PrivateLink endpoint connections, as shown in the error below.
Error Message:
There was an error modifying private DNS names Private DNS can't be enabled because the service com.amazonaws.vpce.us-east-1.vpce-svc-xxxxxxxxxxxxxxxxx does not provide a private DNS name.1 vote
- Don't see your idea?