...
| Tip |
|---|
You may create security groups either via Morpheus UI settings OR via Community Hub Item deployment. |
eumetcast
Create a designated security group with a descriptive name (e.g. "eumetcast" ) and add to it the following rules:
| Name | Direction | Rule Type | Protocol | Port Range | Source Type | Source | Destination Type | Destination Port Range |
|---|---|---|---|---|---|---|---|---|
| 2268-udp | ingress | Custom Rule | TCP | 2268 | Network | 0.0.0.0/0 | Instance | |
| 8500-tcp | ingress | Custom Rule | TCP | 8500 | Network | 0.0.0.0/0 | Instance |
ssh
A security group for ssh access should exist in your tenancy by default. Simply verify it is available and enforcing the following rules:
| Name | Direction | Rule Type | Protocol | Port Range | Source Type | Source | Destination Type | Destination Port Range |
|---|---|---|---|---|---|---|---|---|
| 22-tcp | ingress | Custom Rule | TCP | 22 | Network | 0.0.0.0/0 | Instance |
Deployment based on the EWC Community Hub
...
11. (Optional) Enable ssh access to the VM, by browsing the Morpheus UI to your eumetcast VM → Network → Security Group → Edit Security Group → add ssh-internal.
| Warning |
|---|
Adding the ssh-internal security group implies your VM is only reachable via ssh from other VMs within the same network, and that you require ssh tunneling to connect. See How to Connect to a VM Hidden Behind the SSH Bastion for an example on to achieve a secure connection. |
Once the service is provisioned, the user will start to receive their subscribed data on their VM (stored by default in in /root/data/eumetcast/ but can be changed in the /etc/cast-client-channels_ter-1.ini file).
...