MARKETPLACE / Networking

OpenVPN Access Server on FibaCloudDesign a clear path from your team to private resources.

Connect authorised users to the resources they need through a planned VPN service. OpenVPN Access Server brings connection management into an application, while identity, routing, firewall rules and subscription scope remain essential deployment decisions.

Configure a cloud instance Browse the catalogue

OpenVPN Access ServerFIBACLOUD

Identity, tunnel and destination policy work together

Application context Deployment decisions Maintenance planning

01 / OpenVPN Access Server

A VPN connection should follow an access policy.

OpenVPN Access Server provides administration for VPN connections and client access. A useful deployment begins with the resources that users need to reach, the identity system they will use and the routes their devices should receive. Define those requirements before exposing the service or distributing client profiles.

Encryption protects traffic within the configured tunnel; it does not by itself authorise every destination beyond it. Align VPN access with host and network firewall rules, review administrative exposure and define how accounts and client credentials are revoked. Confirm the available image, supported operating system and license requirements in the deployment flow.

Remote access for small teams

Give staff a defined route to selected internal services. Use individual identities and review the difference between a connected device and a user who is authorised to reach a particular application.

Administrative access paths

Place infrastructure administration behind a deliberate access route. Combine VPN access with service-level authentication, limited privileges and logging rather than treating the tunnel as the only security control.

Partner and contractor access

Plan narrower access for time-limited collaboration. Document approved destinations, account expiry and revocation so temporary work does not become a permanent route into the environment.

02 / DEPLOYMENT DECISIONS

Choose the scope before the instance.

Confirm the current image, operating system, software versions and license requirements in the cloud configuration.

OpenVPN Access Server deployment decisions
Decision	What to review	Why it matters
Identity and credentials	Choose the supported authentication method and define account provisioning, recovery and revocation.	A connection policy is only useful while user access reflects current responsibilities.
Routing and DNS	Specify the networks and DNS information clients should use, including the intended tunnel-routing model.	Routing choices affect both application reachability and user device traffic.
Network boundaries	Review inbound exposure, administration access and the destinations VPN clients may reach.	The VPN gateway and destination services need consistent access rules.
License and capacity	Check the available licensing terms and expected concurrent use before selecting resources.	Subscription scope and actual connection demand are separate from basic instance sizing.

THE OPERATING VIEW

Identity, tunnel and destination policy work together

An example access path. Gateway authentication, routing and destination permissions each control a different part of the connection.

01User identity
02VPN gateway
03Allowed routes
04Private services

An example access path. Gateway authentication, routing and destination permissions each control a different part of the connection.

FROM PLAN TO OPERATION

Build a process you can repeat.

Validate the application and prepare its operating process before depending on it for daily work.

01
Confirm the deployment scope
Review the Access Server image, supported operating system, license terms and the network destinations the service will provide.
02
Prepare gateway access
Configure the public endpoint, required network rules and protected administrator access following the vendor’s deployment guidance.
03
Validate with a test user
Configure identity and client access, then test expected routes, DNS resolution and denied destinations from an external connection.
04
Operate the access lifecycle
Maintain software and certificates, review access logs, remove expired accounts and rehearse the recovery of gateway configuration.

PRACTICAL QUESTIONS

Before you move forward.

Clarify the application and operating requirements before choosing the deployment.

Discuss your requirements

Is the VPN license included in the instance price?

Do not infer license entitlement from the cloud instance alone. Review the available image and current OpenVPN Access Server licensing terms before choosing the deployment and expected connection capacity.

Will connected users reach every private service?

Reachability depends on routes, firewall rules and application permissions. Define the permitted destinations and test both allowed and denied access for representative users.

Should all user traffic pass through the VPN?

Choose the routing model based on your application and access requirements. Evaluate DNS, bandwidth and device behavior, then document the expected traffic path for users and administrators.

How should access be removed when someone leaves?

Disable the user in the relevant identity system and revoke the associated VPN access or client credentials as the configuration requires. Verify that existing and new connections no longer provide access.

OFFICIAL DOCUMENTATION

Go deeper with the application’s own guidance.

Use the documentation for the product and version selected at deployment.

FIBACLOUD / OpenVPN Access Server

Turn the plan into your next deployment.

Review the available configuration and choose the resources for your project.

Configure a cloud instance Discuss your requirements

Compute

Storage

Networking & security

OpenVPN Access Server on FibaCloudDesign a clear path from your team to private resources.