To white list an IP in Amazon AWS security group using aws command line tool, run
|
1 |
aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID_HERE --protocol tcp --port PORT_HERE --cidr IP_IN_CIDR_HERE |
Example
|
1 |
aws ec2 authorize-security-group-ingress --group-id sg-a777eee6 --protocol tcp --port 443 --cidr 94.31.33.128/27 |
Here are some useful command working with AWS Elastic Beanstalk
|
1 2 3 4 5 6 7 8 9 10 11 12 |
eb init = initialize environment eb list eb logs eb console = open aws console eb open = open application in web browser eb appversion = show application versions eb health = show health of application eb codesource = select local or codecommit eb deploy = deploy code eb events = Gets recent events. eb create = Creates a new environment. eb labs download = download application to local computer |
Application get stored in folder
|
1 |
/var/app/ondeck |
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”.
Click on Virtual Cloud Network link, that will take you to page with VPC details.
Scroll down, you will see 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.
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.
On Add Ingress Rules page, select
|
1 2 3 |
SOURCE TYPE = CIDR SOURCE CIDR = 0.0.0.0/0 IP PROTOCOL = ICMP |
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
To connect to Google Cloud SQL, run
|
1 |
gcloud sql connect DB_INSTANE_NAME |
To enable CORS for Amazon S3 bucket, add
|
1 2 3 4 5 6 7 8 9 10 11 |
<?xml version="1.0" encoding="UTF-8"?> <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <CORSRule> <AllowedOrigin>*</AllowedOrigin> <AllowedMethod>PUT</AllowedMethod> <AllowedMethod>POST</AllowedMethod> <AllowedMethod>DELETE</AllowedMethod> <MaxAgeSeconds>1800</MaxAgeSeconds> <AllowedHeader>*</AllowedHeader> </CORSRule> </CORSConfiguration> |
To list instances in Google Cloud App Engine, run
|
1 |
gcloud app instances list |
To create an application
|
1 |
gcloud app create |
To deploy an application
|
1 |
gcloud app deploy |
To create a Google Cloud SQL database, run
|
1 |
gcloud sql instances create INSTANCE_NAME_HERE --activation-policy=ALWAYS --tier=db-n1-standard-1 |
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
|
1 |
gcloud sql databases create DB_NAME_HERE --instance INSTANCE_NAME_HERE |
To create a User, run
|
1 |
gcloud sql users set-password root --host=% --instance INSTANCE_NAME_HERE --password=PASSWORD_HERE |
To list all google cloud SQL instances, run
|
1 |
gcloud sql instances list |
To list all databases in a Google Cloud SQL server, run
|
1 |
gcloud sql databases list --instance INSTANCE_NAME_HERE |
To connect to Google Cloud SQL database, run
|
1 |
gcloud sql connect INSTANCE_NAME_HERE |
This will open firewall rule and add your IP so you can connect to Google Cloud SQL 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
|
1 |
hostnamectl set-hostname --static HOSTNAME_HERE |
Example
|
1 |
hostnamectl set-hostname --static server1.serverok.in |
To disable change of hostname, run
|
1 |
echo "preserve_hostname: true" > /etc/cloud/cloud.cfg.d/99_hostname.cfg |
Now reboot your server with
|
1 |
reboot |
