AWS components for OPDK setup

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?

Solved Solved
1 3 291
1 ACCEPTED SOLUTION

Not applicable

@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

3 REPLIES 3

Hi Subrahmanyam,

As to be very quick, we wouldn't need any other components to have Edge up and running.

However, there would be couple of components you might have to consider based on your requirements, like ELB - in case of load balancing and high availability, Splunk - for operational analytics etc.,

Many other tools comes into picture based on your E2E stack where you would wish to go beyond Edge out of box features.

Thanks,
Karthick.

As @Karthick Vankayala pointed out, you would want to have ELBs configured with port forwarding for your IP names with certificates to terminate the connection. In a previous setup with a 2 data center high availability we used 4 ELBs:

  1. Dev Portal
  2. External API traffic
  3. Internal API traffic
  4. Management Server UI/APIs

In addition you would want to set up security groups for Edge components and the Internet Gateway and VPC Gateway.

Not applicable

@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