Solved: AWS components for OPDK setup - Page 2

ksprashu · 05-03-2017 09:26 PM

When we install Edge for Private Cloud, all the components that are relevant to the Edge installation (including runtime) are installed in the setup process. These components are installed + configured on the VMs / Compute instances that have been made available.

In addition to this, are there are any AWS components that would be needed if we are installing on AWS? Or more generically, on any private cloud provider, what the additional components that will be needed / recommended. Is there a recommended setup / point of view that is available to refer to?

Report Inappropriate Content

@Prashanth K S reinforcing and expanding the feedback above.

On every Private Cloud installation (physical data center, GCP, AWS, Azure, or any other) you will require:

Global Load Balancer or DNS configuration to route traffic to the different regions
Local Load Balancer on each region
Registration on local Load Balancer of components exposed to Internet traffic (Routers Virtual Hosts, Developer Portal)
VPN, VPC-peering or similar strategy to connect Message Processors to your backend systems
Storage for backup archival
Assuming you are planning to do log aggregation, then syslog server
Integration of Edge with existing (used by your Ops Team) monitoring tools. I suggest looking at https://cloud.google.com/stackdriver/.
If applicable, installation of Edge Monitoring Dashboard.
If applicable, provisioning of Apigee Repository Mirror to support non-internet installations.

The above does not include typical installation prerequisites, installation and post installation activities. For those refer to official documentation:

http://docs.apigee.com/private-cloud/latest/installing-edge-private-cloud

View solution in original post