
Amazon S3 (Simple Storage Service) is a popular cloud storage service from AWS that allows users to store and retrieve any amount of data at any time. Whether you're hosting static websites, storing backups, or serving media content, S3 is a reliable and scalable solution.

In this guide, you'll learn how to create an S3 bucket step-by-step using the AWS Console.

---

## Step 1: Log in to AWS Console

Start by logging in to your AWS account via the [AWS Management Console](https://aws.amazon.com/console/).

![image 1](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-01.webp?updatedAt=1733887150760)

---

## Step 2: Open the Amazon S3 Service

After logging in, search for **S3** in the search bar at the top and click the **S3** service.

![image 2](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-02.webp?updatedAt=1733887150760)

---

## Step 3: Create a New Bucket

- Click the **Create bucket** button.  
- Enter a unique **Bucket name** (must be globally unique).  
- Under **Object Ownership**, choose **ACLs disabled (recommended)** to simplify permissions.

![image 3](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-03.webp?updatedAt=1733887150760)

---

## Step 4: Configure Encryption

- Scroll down to the **Default encryption** section.  
- Choose **Amazon S3 managed keys (SSE-S3)**.  
- Enable the **Bucket Key** to reduce the cost of encryption requests.

![image 4](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-04.webp?updatedAt=1733887150760)

---

## Step 5: Finalize and View Your Bucket

After completing the setup, your new bucket will appear in the S3 bucket list.

![image 5](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-05.webp?updatedAt=1733887150760)

Click the bucket name to open it and start uploading files, setting permissions, or enabling static website hosting.

![image 6](https://ik.imagekit.io/n1hqrcegw/articles/cara-membuat-amazon-s3-bucket-di-aws/gambar-06.webp?updatedAt=1733887150760)

---

## Conclusion

Setting up an S3 bucket is simple and essential for many AWS-powered applications. With just a few clicks, you can start storing data securely in the cloud. Don't forget to manage access policies and monitor your storage usage for optimal performance and cost.

Need help with setting permissions or enabling static site hosting? Stay tuned for our upcoming guides on advanced S3 configurations!


Enabling HTTPS on your website is crucial for security, SEO, and user trust. Thankfully, Let’s Encrypt offers free SSL/TLS certificates that are easy to set up on an Nginx server. In this tutorial, we’ll walk through how to secure your Nginx server using Let’s Encrypt on Ubuntu.

---

## Step 1: Check Your Website Before SSL

Before adding SSL, your website is likely still served over plain HTTP.

Example:
`http://jadifullstack.id`

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/cara-mengamankan-nginx-ssl-tls-https-lets-encrypt-ubuntu/gambar-01.webp?updatedAt=1733852578858)

---

## Step 2: Install Certbot and the Nginx Plugin

Make sure your system is up to date:

```bash
sudo apt update
sudo apt install certbot python3-certbot-nginx
```

Certbot is the tool that will communicate with Let’s Encrypt and configure Nginx automatically.

---

## Step 3: Request an SSL Certificate

Run the following command to request and install your SSL certificate:

```bash
sudo certbot --nginx -d jadifullstack.id
```

If successful, you'll see a confirmation message:

> "Successfully received certificate"

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/cara-mengamankan-nginx-ssl-tls-https-lets-encrypt-ubuntu/gambar-02.webp?updatedAt=1733852578858)

---

## Step 4: Verify HTTPS is Working

After a successful setup, your website will now be accessible via HTTPS.

Example:
`https://jadifullstack.id`

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/cara-mengamankan-nginx-ssl-tls-https-lets-encrypt-ubuntu/gambar-03.webp?updatedAt=1733852578858)

Check that your browser shows a secure padlock and that HTTP requests are redirected to HTTPS.

---

## Step 5: Enable Auto Renewal

Let’s Encrypt certificates expire every 90 days. Certbot makes it easy to auto-renew them.

You can verify the auto-renewal configuration with this command:

```bash
sudo certbot renew --dry-run
```

To schedule auto-renewal using `cron`, run:

```bash
crontab -e
```

Then add the following line to renew the certificate daily at noon:

```bash
0 12 * * * /usr/bin/certbot renew --quiet
```

![Image 4](https://ik.imagekit.io/n1hqrcegw/articles/cara-mengamankan-nginx-ssl-tls-https-lets-encrypt-ubuntu/gambar-04.webp?updatedAt=1733852578858)

---

## Conclusion

Now your Ubuntu VPS running Nginx is secured with HTTPS using a free SSL certificate from Let’s Encrypt. This simple setup improves trust, SEO ranking, and data protection. Always monitor your certificate expiration or use Certbot's auto-renewal to avoid disruptions.

Want to take it further? Consider setting up a redirect from HTTP to HTTPS or enabling HTTP/2 for better performance!





When launching an EC2 instance, the public IP address assigned to it can change if the instance is stopped and restarted. To avoid this, AWS provides **Elastic IP addresses**—a static IPv4 address designed for dynamic cloud computing.

In this guide, we’ll show you how to allocate and associate an Elastic IP address with your EC2 instance.

---

## Step 1: Allocate a New Elastic IP Address

From the AWS Management Console, go to the **EC2 Dashboard**, then select **Elastic IPs** from the sidebar. Click on **Allocate Elastic IP address** and confirm.

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/panduan-menggunakan-elastic-ip-address-ec2-instance/gambar-01.webp?updatedAt=1733759701308)

---

## Step 2: Associate the Elastic IP with Your EC2 Instance

Once the IP is allocated, select it from the list and click **Actions → Associate Elastic IP address**.

* In the **Resource type**, choose **Instance**.
* In **Instance**, select the EC2 instance you want to assign the IP to.
* Click **Associate** to finalize the configuration.

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/panduan-menggunakan-elastic-ip-address-ec2-instance/gambar-02.webp?updatedAt=1733759701308)

---

## Step 3: Verify IP Assignment

Go to your **EC2 Instances dashboard** and confirm that the public IP has been updated with your new Elastic IP.

This IP will remain the same even if you stop and start the instance.

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/panduan-menggunakan-elastic-ip-address-ec2-instance/gambar-03.webp?updatedAt=1733759701308)

---

## Conclusion

Elastic IP addresses are essential for maintaining a consistent public IP for your cloud services, especially for production environments. Remember that AWS charges for unused Elastic IPs, so always release any IP addresses that are no longer in use.

With this setup, your EC2 instance is now more stable and accessible under a static IP.




If you're hosting a website or application on AWS, using Amazon Route 53 as your DNS provider gives you full control over routing traffic. In this guide, you'll learn how to move your domain's name servers to Route 53.

---

## Step 1: Create a Public Hosted Zone in Route 53

Go to the AWS Route 53 Console. Click on **Hosted zones** in the sidebar, then choose **Create hosted zone**.

* Enter your **domain name**.
* Choose **Public hosted zone**.
* Click **Create hosted zone**.

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-kinerja-domain-cara-pindahkan-name-server-route-53/gambar-01.webp?updatedAt=1733752674448)

---

## Step 2: View Your Route 53 NS Records

After creating the hosted zone, Route 53 automatically generates several records, including the **NS (Name Server)** records. These are the name servers you need to use for your domain.

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-kinerja-domain-cara-pindahkan-name-server-route-53/gambar-02.webp?updatedAt=1733752674448)

---

## Step 3: Update Name Servers on Your Domain Registrar (GoDaddy Example)

Log in to your domain registrar (e.g., GoDaddy), go to your domain settings, and choose **Manage DNS**.

* Scroll to **Nameservers** and choose: **I'll use my own nameservers**.
* Copy and paste the NS records from Route 53 into the fields.
* Save the changes.

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-kinerja-domain-cara-pindahkan-name-server-route-53/gambar-03.webp?updatedAt=1733752674448)

Note: DNS changes can take up to 48 hours to fully propagate.

---

## Conclusion

Using AWS Route 53 as your DNS provider helps ensure high availability, fast response times, and tight integration with other AWS services. After updating your nameservers, you can manage DNS records directly from the Route 53 dashboard.

Be sure to monitor your DNS configuration and test it using tools like `dig`, `nslookup`, or online DNS checkers to verify the update was successful.



If you’ve purchased a domain on GoDaddy and host your application on a VPS, pointing your domain to your server allows users to access your website easily. This guide shows you how to connect a GoDaddy domain to a Linux VPS (using Nginx as the web server).

---

## Step 1: Get Your VPS IP Address

Connect to your VPS using SSH and run the following command to find your public IP address:

```bash
curl ifconfig.me
```

This IP address will be used in your DNS settings on GoDaddy. Initially, your Laravel application or Nginx welcome page can be accessed via this IP in the browser, such as `http://123.456.789.123`.

Later, after DNS is properly set up, your site will be accessible using the domain name instead, such as `http://jadifullstack.id`.

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/cara-menghubungkan-domain-godaddy-ke-vps-linux-nginx/gambar-01.webp?updatedAt=1733743922149)

---

## Step 2: Access Your Domain Settings in GoDaddy

Log in to your [GoDaddy account](https://www.godaddy.com/) and navigate to **My Products**. Find the domain you want to configure and click **DNS** or **Manage DNS**.

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/cara-menghubungkan-domain-godaddy-ke-vps-linux-nginx/gambar-02.webp?updatedAt=1733743922149)

---

## Step 3: Set Up an A Record

In the DNS Management page:

* Find the **A Record** section
* Set **Host** to `@`
* Set **Points to** to your VPS IP address
* Set **TTL** to `600 seconds` (or default)
* Click **Save**

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/cara-menghubungkan-domain-godaddy-ke-vps-linux-nginx/gambar-03.webp?updatedAt=1733743922149)

Note: DNS propagation may take a few minutes up to 48 hours.

Once this is complete, your server will no longer need to be accessed by IP. Instead, you can use your domain (e.g., `jadifullstack.id`) to open your Laravel or Nginx site.

---

## Step 4: Verify It Works

If Nginx is correctly configured on your VPS (as explained in our [Laravel deployment guide](/blog/deploy-laravel-to-vps)), your Laravel site should now be accessible from your GoDaddy domain.

Initially: `http://123.456.789.123`
Now: `http://jadifullstack.id`

![Image 4](https://ik.imagekit.io/n1hqrcegw/articles/cara-menghubungkan-domain-godaddy-ke-vps-linux-nginx/gambar-04.webp?updatedAt=1733743922149)

---

## Conclusion

You've successfully pointed your GoDaddy domain to your VPS. Now, your server can be accessed through a human-readable domain name. For production, don’t forget to set up HTTPS using Let’s Encrypt and monitor your DNS settings for consistency.






### 🔧 **Service Management (Ubuntu-based systems)**

| Command                             | Description                             |
| ----------------------------------- | --------------------------------------- |
| `sudo systemctl start supervisor`   | Start the Supervisor service            |
| `sudo systemctl stop supervisor`    | Stop the Supervisor service             |
| `sudo systemctl restart supervisor` | Restart Supervisor                      |
| `sudo systemctl status supervisor`  | Check the status of Supervisor          |
| `sudo systemctl enable supervisor`  | Enable Supervisor to run at boot        |
| `sudo systemctl disable supervisor` | Disable Supervisor from running at boot |

---

### ⚙️ **Supervisor CLI Commands**

These use the `supervisorctl` command:

| Command                                | Description                                          |
| -------------------------------------- | ---------------------------------------------------- |
| `sudo supervisorctl`                   | Enter Supervisor interactive mode                    |
| `sudo supervisorctl status`            | View the status of all managed processes             |
| `sudo supervisorctl start <program>`   | Start a specific program                             |
| `sudo supervisorctl stop <program>`    | Stop a specific program                              |
| `sudo supervisorctl restart <program>` | Restart a specific program                           |
| `sudo supervisorctl reread`            | Reread config files (does **not** apply changes yet) |
| `sudo supervisorctl update`            | Apply changes after `reread` (add/remove programs)   |
| `sudo supervisorctl reload`            | Restart Supervisor and all managed processes         |
| `sudo supervisorctl shutdown`          | Gracefully shut down Supervisor daemon               |

---

### 📁 **Supervisor Config Locations (Ubuntu)**

| Path                               | Description                                        |
| ---------------------------------- | -------------------------------------------------- |
| `/etc/supervisor/supervisord.conf` | Main Supervisor config file                        |
| `/etc/supervisor/conf.d/`          | Directory to store individual program config files |

---

### 🛠️ **Example Workflow After Adding a New Program**

```bash
sudo supervisorctl reread
sudo supervisorctl update
sudo supervisorctl start your_program_name
```




### 🚀 **Basic Process Management**

| **Command**                                            | **Description**                                    |
| ------------------------------------------------------ | -------------------------------------------------- |
| `pm2 start app.js`                                     | Start a Node.js application                        |
| `pm2 start app.js --name my-app`                       | Start the app with a custom process name           |
| `pm2 list`                                             | List all running processes managed by PM2          |
| `pm2 show <id or name>` or `pm2 describe <id or name>` | Show detailed information about a specific process |
| `pm2 restart <id or name>`                             | Restart a specific process                         |
| `pm2 reload <id or name>`                              | Gracefully reload a process (zero downtime)        |
| `pm2 stop <id or name>`                                | Stop a specific process                            |
| `pm2 delete <id or name>`                              | Delete a process from the PM2 process list         |
| `pm2 delete all`                                       | Remove all processes from PM2 management           |


---

### 🔁 **Startup & Auto-Restart**

| Command         | Description                                              |
| --------------- | -------------------------------------------------------- |
| `pm2 startup`   | Generate and configure PM2 to launch on system boot      |
| `pm2 save`      | Save current process list for automatic reload on reboot |
| `pm2 resurrect` | Restore processes saved via `pm2 save`                   |

---

### 📈 **Monitoring & Logs**

| **Command**             | **Description**                                     |
| ----------------------- | --------------------------------------------------- |
| `pm2 monit`             | Launch PM2's real-time process monitoring dashboard |
| `pm2 logs`              | Show logs for all processes                         |
| `pm2 logs <id or name>` | Show logs for a specific process                    |
| `pm2 flush`             | Clear all logs                                      |
| `pm2 reloadLogs`        | Reload logs in real-time                            |

---

### 🛠️ **Miscellaneous**

| **Command**                      | **Description**                                   |
| -------------------------------- | ------------------------------------------------- |
| `pm2 env <id or name>`           | Show environment variables for a specific process |
| `pm2 reload ecosystem.config.js` | Reload all apps defined in an ecosystem file      |
| `pm2 start ecosystem.config.js`  | Start all apps from an ecosystem file             |





A complete and beginner-friendly guide to install **Certbot Let’s Encrypt SSL** on **Ubuntu servers with NGINX**, enabling free **HTTPS encryption** with **automatic certificate renewal**.

---

## 📦 Installing Certbot on Ubuntu 16.04

For users running Ubuntu 16.04, execute the following commands:

```bash
apt-get update
sudo apt-get install certbot
sudo apt-get install python-certbot-nginx
```

---

## 📦 Installing Certbot on Ubuntu 18.04 and Later

For Ubuntu 18.04 or any newer version, run the following:

```bash
apt-get update
sudo apt-get install certbot
sudo apt-get install python3-certbot-nginx
```

---

## 🌐 Obtain a Let’s Encrypt SSL Certificate for NGINX

Once Certbot is installed, use this command to **automatically configure HTTPS for your domain**:

```bash
sudo certbot --nginx -d example.com
```

Replace `example.com` with your actual domain name.

---

## 🔁 Automatically Renew Let’s Encrypt SSL Certificates

To ensure your SSL certificates are **renewed automatically**, add a cron job as follows:

### Edit Crontab

```bash
crontab -e
```

### Add the Following Line

```bash
0 12 * * * /usr/bin/certbot renew --quiet
```

This command runs the renewal process **daily at 12:00 PM**.

---

## ✅ Conclusion

Your website is now secured with **free HTTPS using Let’s Encrypt**, and the SSL certificate will automatically renew without manual intervention.



### 🔧 **Service Management**

Use `sudo` if you're not logged in as root.

| Command                        | Description                                       |
| ------------------------------ | ------------------------------------------------- |
| `sudo systemctl start nginx`   | Start the Nginx service                           |
| `sudo systemctl stop nginx`    | Stop the Nginx service                            |
| `sudo systemctl restart nginx` | Restart Nginx and reload all configs              |
| `sudo systemctl reload nginx`  | Reload config without dropping active connections |
| `sudo systemctl status nginx`  | Check the current status of Nginx                 |
| `sudo systemctl enable nginx`  | Enable Nginx to start at boot                     |
| `sudo systemctl disable nginx` | Disable Nginx from auto-starting at boot          |

---

### ⚙️ **Configuration & Testing**

| Command                | Description                                 |
| ---------------------- | ------------------------------------------- |
| `sudo nginx -t`        | Test Nginx configuration for syntax errors  |
| `sudo nginx -s reload` | Reload Nginx via CLI                        |
| `sudo nginx -s stop`   | Stop Nginx via CLI                          |
| `sudo nginx -s quit`   | Gracefully shut down Nginx                  |
| `nginx -v`             | Show Nginx version                          |
| `nginx -V`             | Show version with build options and modules |

---

### 📁 **Default Configuration Paths (Ubuntu)**

| Path                          | Description                                                    |
| ----------------------------- | -------------------------------------------------------------- |
| `/etc/nginx/nginx.conf`       | Main Nginx config file                                         |
| `/etc/nginx/sites-available/` | Directory for available virtual host configs                   |
| `/etc/nginx/sites-enabled/`   | Directory for enabled sites (symlinked from `sites-available`) |
| `/var/www/html/`              | Default web root directory                                     |

---

### 🛠️ **Extra Tips**

* After editing the config:

  ```bash
  sudo nginx -t && sudo systemctl reload nginx
  ```

* To view logs:

  ```bash
  tail -f /var/log/nginx/access.log
  tail -f /var/log/nginx/error.log
  ```


Ferry Dermawan

Blog

Shorts