
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.






Deploying your Laravel application to a VPS gives you full control over your environment, performance, and security. In this guide, you'll learn how to deploy Laravel from GitHub to a VPS using the LEMP stack (Linux, Nginx, MySQL, PHP).

---

## Step 1: Connect to Your VPS and Update the System

Start by connecting to your VPS via SSH. Once connected, update your package list and upgrade the system:

```bash
sudo apt update && sudo apt upgrade -y
```

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/cara-deploy-laravel-dari-github-ke-vps-dengan-lemp/gambar-01.webp?updatedAt=1733737401685)

---

## Step 2: Install PHP and Required Extensions

Install PHP along with the extensions required by Laravel:

```bash
sudo apt install php php-cli php-common php-mbstring php-xml php-bcmath php-curl php-mysql unzip curl php-zip php-tokenizer php-fileinfo php-fpm -y
```

Check the installed PHP version:

```bash
php -v
```

Expected output: PHP 8.3 (or newer)

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/cara-deploy-laravel-dari-github-ke-vps-dengan-lemp/gambar-02.webp?updatedAt=1733737401685)

---

## Step 3: Install MySQL and Create a Database

Install MySQL Server:

```bash
sudo apt install mysql-server -y
```

Access the MySQL shell:

```bash
sudo mysql
```

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/cara-deploy-laravel-dari-github-ke-vps-dengan-lemp/gambar-03.webp?updatedAt=1733737401685)

Create a database and a user for your Laravel app:

```sql
CREATE DATABASE laravel_db;
CREATE USER 'laravel_user'@'localhost' IDENTIFIED BY 'your_secure_password';
GRANT ALL PRIVILEGES ON laravel_db.* TO 'laravel_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;
```

---

## Step 4: Set Up SSH Key to Pull From GitHub

To pull your Laravel project from GitHub, add your VPS SSH key to GitHub:

1. Generate SSH key (if not yet):

   ```bash
   ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
   ```
2. Copy the key:

   ```bash
   cat ~/.ssh/id_rsa.pub
   ```
3. Paste it into **GitHub → Settings → SSH and GPG keys**

![Image 4](https://ik.imagekit.io/n1hqrcegw/articles/cara-deploy-laravel-dari-github-ke-vps-dengan-lemp/gambar-04.webp?updatedAt=1733737401685)

---

## Step 5: Clone the Laravel Project and Configure

Clone the repository into your web directory:

```bash
git clone git@github.com:yourusername/your-laravel-project.git
```

Navigate to the project folder:

```bash
cd your-laravel-project
```

Install dependencies and configure the app:

```bash
composer install
cp .env.example .env
php artisan key:generate
```

Update the `.env` file with your database credentials:

```
DB_DATABASE=laravel_db
DB_USERNAME=laravel_user
DB_PASSWORD=your_secure_password
```

Run Laravel migrations:

```bash
php artisan migrate
```

If your project uses frontend assets:

```bash
npm install && npm run build
```

Set permissions for the storage and bootstrap directories:

```bash
sudo chown -R www-data:www-data .
sudo chmod -R 775 storage bootstrap/cache
```

---

## Step 6: Configure Nginx

Create a new server block for Laravel:

```bash
sudo nano /etc/nginx/sites-available/your-laravel-project
```

Paste the following configuration:

```nginx
server {
    listen 80;
    server_name yourdomain.com;
    root /var/www/your-laravel-project/public;

    index index.php index.html index.htm;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }
}
```

Enable the site and restart Nginx:

```bash
sudo ln -s /etc/nginx/sites-available/your-laravel-project /etc/nginx/sites-enabled/
sudo nginx -t
sudo systemctl reload nginx
```

---

## Step 7: Access Your Laravel Application

Once everything is configured, visit your server's public IP or domain to view the Laravel dashboard.

![Image 5](https://ik.imagekit.io/n1hqrcegw/articles/cara-deploy-laravel-dari-github-ke-vps-dengan-lemp/gambar-05.webp?updatedAt=1733737401685)

---

## Conclusion

Congratulations! You've successfully deployed your Laravel application to a VPS. This setup gives you complete control over the environment and scales better for production. You can now secure your server with SSL and configure auto-deployment for better CI/CD.




Amazon EC2 (Elastic Compute Cloud) lets you run virtual servers in the cloud. In this beginner-friendly guide, you’ll learn how to launch your first EC2 instance on AWS using Ubuntu and Free Tier resources.

---

## Step 1: Log In to the AWS Console

Go to the [AWS Console](https://aws.amazon.com/console/) and log in with your credentials.

![Image 0](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-0.webp?updatedAt=1733639881913)

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-01.webp?updatedAt=1733639881913)

---

## Step 2: Search for EC2 Service

In the search bar at the top, type `EC2` and click on the EC2 service.

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-02.webp?updatedAt=1733639881913)

---

## Step 3: Launch a New EC2 Instance

Click the **Launch Instances** button.

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-03.webp?updatedAt=1733639881913)

---

## Step 4: Choose an Amazon Machine Image (AMI)

Choose **Ubuntu** or a similar Free Tier-eligible AMI.

![Image 4](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-04.webp?updatedAt=1733639881913)

---

## Step 5: Choose an Instance Type

Select **t2.micro**, which is eligible for the AWS Free Tier.

![Image 5](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-05.webp?updatedAt=1733639881913)

---

## Step 6: Configure Instance Details

Set the number of instances to **1**.

![Image 6](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-06.webp?updatedAt=1733639881913)

---

## Step 7: Add Storage

Keep the default of **8 GiB**, which is sufficient for basic applications.

![Image 7](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-07.webp?updatedAt=1733639881913)

---

## Step 8: Create a Key Pair

Create a new key pair to access the server:

* Type: RSA
* Format: `.pem`

Download and save the key securely.

![Image 8](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-08.webp?updatedAt=1733639881913)

---

## Step 9: Configure Security Group

Add inbound rules for the following protocols:

* SSH (port 22)
* HTTP (port 80)
* HTTPS (port 443)

Then click **Launch Instances**.

![Image 9](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-09.webp?updatedAt=1733639881913)

---

## Step 10: View Running Instances

Once launched, you will see your EC2 instance listed on the dashboard.

![Image 10](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-10.webp?updatedAt=1733639881913)

---

## Step 11: Connect to Your Instance via SSH

Open your terminal and connect to your instance using the `.pem` key:

```bash
chmod 400 your-key.pem
ssh -i your-key.pem ubuntu@your-ec2-public-ip
```

Replace `your-ec2-public-ip` with the public IPv4 address of your EC2 instance.

![Image 11](https://ik.imagekit.io/n1hqrcegw/articles/cara-buat-ec2-di-aws/gambar-11.webp?updatedAt=1733639881913)

---

## Conclusion

You’ve successfully launched and connected to an EC2 instance using the AWS Free Tier. From here, you can deploy web apps, run servers, and explore AWS cloud services. Be sure to stop or terminate unused instances to avoid unexpected charges.



PhpStorm is a powerful IDE for Laravel development. With the right setup, you can automate code formatting using **Laravel Pint** for PHP and **Prettier** for frontend files (like JavaScript, CSS, and Blade). This guide walks you through configuring both tools to run automatically on save.

---

## Step 0: Install and Configure Pint & Prettier

First, install **Laravel Pint** as a development dependency:

```bash
composer require laravel/pint --dev
```

Then, create a `pint.json` file at the root of your project (optional, but recommended for custom rules):

```json
{
  "preset": "laravel",
  "exclude": [
    "vendor",
    "node_modules"
  ]
}
```

Next, install **Prettier** and its plugins for Tailwind CSS and Blade:

```bash
npm install -D prettier prettier-plugin-tailwindcss @shufo/prettier-plugin-blade
```

Create a `.prettierrc` file at the root of your project:

```json
{
  "semi": true,
  "singleQuote": true,
  "printWidth": 100,
  "plugins": [
    "prettier-plugin-tailwindcss",
    "@shufo/prettier-plugin-blade"
  ]
}
```

You are now ready to continue with PhpStorm setup.

---

## Step 1: Open Your Laravel Project in PhpStorm

Ensure that your Laravel project has Pint and Prettier already installed.

![Image 1](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-1.webp?updatedAt=1733060511724)

---

## Step 2: Open Settings → Actions on Save

Go to `Preferences` (or `Settings` on Windows/Linux) → **Actions on Save**.

![Image 2](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-2.webp?updatedAt=1733060511724)

---

## Step 3: Configure Reformat Code (Uncheck PHP)

Enable **Reformat Code**, but uncheck **PHP** to avoid conflict with Pint.

![Image 3](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-3.webp?updatedAt=1733060511724)

---

## Step 4: Add a Custom File Watcher for Laravel Pint

Go to `Settings → Tools → File Watchers`, then click the **+** icon to add a new watcher.

![Image 4](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-4.webp?updatedAt=1733060511724)

Use the following configuration:

```
Name: Pint
File type: PHP
Program: $ProjectFileDir$/vendor/bin/pint
Arguments: $FileRelativePath$
Output paths to refresh: $FileRelativePath$
Working directory: $ProjectFileDir$
```

Under **Advanced Options**, only check:

* *Trigger the watcher on external changes*

![Image 5](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-5.webp?updatedAt=1733060511724)

---

## Step 5: Enable Prettier Integration

Check the box for **Run Prettier** and click **Configure**.

![Image 6](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-6.webp?updatedAt=1733060511724)

Enable **Automatic Prettier configuration**.
Add `*.blade.php` to the list of files that Prettier should process.

![Image 7](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-7.webp?updatedAt=1733060511724)

Make sure Prettier appears with its version number under **Actions on Save** to confirm it’s working.

![Image 8](https://ik.imagekit.io/n1hqrcegw/articles/tingkatkan-produktivitas-phpstorm-laravel-pint-prettier/Screenshot-8.webp?updatedAt=1733060511724)

---

## Conclusion

With Laravel Pint and Prettier configured in PhpStorm, your code stays clean and consistent every time you save. This setup ensures a smooth development workflow, especially when collaborating in a team environment. You can also explore additional automation like PHPStan or ESLint integration for more robust quality checks.




Blog