oracle cloud vpc

Allow ICMP (ping) in Oracle Cloud

Oracle cloud do not allow ICMP/ping to compute instances. To enable ping, you need to enable ICMP in the security group.

On your compute instance details page, you will see “Virtual Cloud Network”.

oracle cloud vpc

Click on Virtual Cloud Network link, that will take you to page with VPC details.

Oracle Virtual Cloud Network

Scroll down, you will see subnet.

Oracle Cloud Public Subnet

Click on Public Subnet, on next page, it shows details about the subnet. Under Security Lists, you will see Default Security List for VirtualCloudNetwork. Click on it to see your firewall rules.

oracle cloud ingress rules

Click Add Ingress Rules button to add new rule. By default port 22 (SSH) allowed from everyone. ICMP was blocked for everyone (rule 2 and 3).

To allow ICMP, you can add a new Rule for ICMP.

Oracle Cloud Add Ingress Rule

On Add Ingress Rules page, select

Click Add Ingress Rules button. Now you should be able to ping to any compute instances on this VPC. It is safe to remove 2 of the existing ICMP rules or edit them instead of adding new rule.

See Oracle Cloud

Amazon S3 CORS

To enable CORS for Amazon S3 bucket, add

Google Cloud SQL

Google Cloud SQL

To create a Google Cloud SQL database, run

INSTANCE_NAME_HERE = this can be anything, lowercase letters, 0-9, for identification purpose only.

db-n1-standard-1 => this is size of the server, you can change it as needed.

To create a Database, run

To create a User, run

To list all google cloud SQL instances, run

Google Cloud SQL

To list all databases in a Google Cloud SQL server, run

list databases in google cloud sql

To connect to Google Cloud SQL database, run

This will open firewall rule and add your IP so you can connect to Google Cloud SQL server.

Set Permanant hostname on AWS EC2 CentOS 7 server

On AWS EC2 when you boot, hostname set something like ip-172-31-41-172.eu-central-1.compute.internal

To chaneg this, run

Example

To disable change of hostname, run

Now reboot your server with

aws-attach-volume

Resize Amazon EC2 Boot Disk

Once you resize disk in Amazon AWS console, it get auto resized on reboot. Some times this won’t happen, you have to manually resize the disk.

To resize disk, do the following.

1) Take a snapshot of the disk
2) Create a new server in same availability zone as current server. Lets call it tmpServer.
3) Shutdown tmpServer.
4) Shutdown the server that need disk resized. Lets call it mainServer. Make sure you have Elastic IP, if not shutting down changes IP of the server.
5) Detach the disk.
6) Attack the disk in tmpServer as /dev/xvdf
7) Start tmpServer.

Login to tempServer and do the following.

Resize Partition

Firt find the devices

In this cause /dev/xvdf is the disk that need to be resized. Current Size is approx 107 GB.

To see free disk space on this disk, run

There is 21.5GB free space on the disk.

To grow partition 1 to use up remaining disk space, run command

Verify free disk space after. Now you see there is not much free disk space left after partition 1.

Resize FileSystem

Resize file system depends on the type of file system you are using. For ext4, do the folllowing.

Check disk using e2fsck

If any errors found, you will be asked to press “y” to fix the errors. After e2fsck run, you can reszie filesystem with command

You have completed resizeing the disk. All you need to do now is

8) Shutdown tmpServer
9) Detact the disk from tmpServer (/dev/xvdf)
10) Attach the disk on original server mainServer as /dev/sda1.

11) start the mainServer.