Pulse Connect Secure on Amazon Web Services
Prerequisites and System Requirements on AWS
To deploy the Pulse Connect Secure Virtual Appliance on AWS, you need the following:
•An AWS account
•Access to the AWS portal (https://console.aws.amazon.com/)*
•Pulse Connect Secure Virtual Appliance Image (.ami file)
•AWS CloudFormation template / AWS Terraform template
•Pulse Connect Secure licenses **
•Site-to-Site VPN between AWS and the corporate network (optional)
Note: This is needed only if the Pulse Connect Secure users need to access corporate resources.
•Pulse License Server (optional)**
•Located at corporate network, accessible through site-to-site VPN
•Pulse Connect Secure configuration in XML format (optional)
- * Pulse Connect Secure Virtual Appliance can be deployed only through AWS CloudFormation style.
- ** From 9.0R3 release, Pulse Connect Secure Virtual Appliance, by default, has two evaluation licenses, and supports licensing with License server located at corporate network.
Deploying Pulse Connect Secure on Amazon Web Services
As depicted in the below diagram, a remote user can use Pulse Connect Secure to securely access cloud resources as well as corporate resources. To access corporate resources, the Pulse Connect Secure administrator needs to ensure that site-to-site VPN is already established between AWS and the corporate network.
Supported Platform Systems
This section helps you in choosing the instance types that should be deployed with Pulse Connect Secure for AWS.
•PSA3000v is equivalent to t2 medium
•PSA5000v is equivalent to t2.xlarge
•PSA7000v is equivalent to t2.2xlarge
|
Model |
vCPU |
CPU Credits / hour |
Memory (GiB) |
Storage |
|
t2.nano |
1 |
3 |
0.5 |
EBS-Only |
|
t2.micro |
1 |
6 |
1 |
EBS-Only |
|
t2.small |
1 |
12 |
2 |
EBS-Only |
|
t2.medium |
2 |
24 |
4 |
EBS-Only |
|
t2.large |
2 |
36 |
8 |
EBS-Only |
|
t2.xlarge |
4 |
54 |
16 |
EBS-Only |
|
t2.2xlarge |
8 |
81 |
32 |
EBS-Only |