Mengakses Basis Data dalam VPC
Pelajari praktik terbaik untuk menghubungkan fungsi Lambda ke basis data relasional (misalnya RDS) dan penyimpanan data lain yang berada dalam jaringan VPC privat Anda.
Mengakses Basis Data dalam VPC adalah pelajaran Serverless AWS Lambda Development gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Serverless AWS Lambda Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Serverless AWS Lambda Development mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Connect Lambda to Private DBs
Welcome! In this lesson, you'll learn how to securely connect your Lambda functions to databases that reside within your private Amazon Virtual Private Cloud (VPC).
This is crucial for serverless applications that need to interact with sensitive or internal data stores like Amazon RDS or other databases that aren't publicly accessible.
Lambda & Your Private Database
You've already configured your Lambda function to operate within a VPC (from the previous lesson). Now, we'll focus on how that Lambda can reach a database that's also inside the same VPC.
This setup ensures secure, internal communication, keeping your database isolated from the public internet.
Security Groups: The Gatekeepers
Security Groups are fundamental here. Think of them as virtual firewalls for your instances and resources within a VPC.
- They control both inbound (incoming) and outbound (outgoing) traffic.
- Both your Lambda function and your database will have associated security groups.
- These groups must be configured to explicitly allow communication between them.
Database Inbound Rules
Your database's security group needs an inbound rule to allow connections from your Lambda function.
- Type: Custom TCP
- Port Range: The specific port your database listens on (e.g.,
3306for MySQL,5432for PostgreSQL). - Source: Crucially, this should be the Security Group ID of your Lambda function.
This ensures only your Lambda can initiate connections to the database.
Lambda Outbound Rules
Conversely, your Lambda function's security group needs an outbound rule to allow it to send traffic to your database.
- Type: Custom TCP
- Port Range: Again, the database's specific port (e.g.,
3306). - Destination: This should be the Security Group ID of your database.
This allows your Lambda to successfully reach out and connect to the database.
Subnets & Network Reachability
Beyond security groups, ensure your Lambda function is deployed into subnets that have proper network routing access to the subnets where your database instances reside.
- Typically, both Lambda and the database will be placed in private subnets within the same VPC.
- AWS handles the internal routing within the VPC, but proper subnet association is key for reachability.
Connecting from Lambda Code
Inside your Lambda function's code, you'll use standard database drivers and connection strings, just like any other application.
You'll need these key details:
- Database endpoint: (e.g.,
your-db.xxxx.rds.amazonaws.com) - Port: (e.g.,
3306) - Database name
- Username
- Password
Java DB Connection Example
Here's a conceptual Java snippet demonstrating how a Lambda might attempt to connect to a database. In a real application, you would handle credentials securely.
This example shows the basic structure; it won't run successfully without a live database and environment variables set.
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.SQLException;
public class Main {
public static void main(String[] args) {
String dbUrl = System.getenv("DB_URL");
String dbUser = System.getenv("DB_USER");
String dbPass = System.getenv("DB_PASS");
if (dbUrl == null || dbUser == null || dbPass == null) {
System.out.println("Error: DB environment variables not set.");
return;
}
try {
System.out.println("Attempting to connect to database...");
Connection conn = DriverManager.getConnection(dbUrl, dbUser, dbPass);
System.out.println("Connection successful!");
conn.close();
} catch (SQLException se) {
System.err.println("Database connection error: " + se.getMessage());
} catch (Exception e) {
System.err.println("An unexpected error occurred: " + e.getMessage());
}
}
}Securely Manage Credentials
Never hardcode database credentials directly in your Lambda code! This is a major security risk.
Best practices for managing sensitive information:
- AWS Secrets Manager: The recommended way to store, retrieve, and rotate database credentials securely.
- Environment Variables: Suitable for non-sensitive configuration, but not for passwords or API keys.
Always prioritize security for sensitive data.
Check Your Understanding
Imagine your Lambda function (associated with Security Group SG-A) needs to connect to an RDS database (associated with Security Group SG-B) on port 3306.
Which inbound rule must be configured on SG-B (the database's security group) to allow this connection?
Recap: Database Access in VPC
Great job! You've learned the essentials of connecting your Lambda functions to private databases within your VPC.
- Both your Lambda and database must be in the same VPC.
- Security groups are vital for controlling traffic flow between them.
- Configure inbound rules on the database's SG and outbound rules on Lambda's SG.
- Always manage database credentials securely, ideally using AWS Secrets Manager.
This knowledge is key to building secure and robust serverless applications!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Mengakses Basis Data dalam VPC” gratis?
Ya — teks lengkap “Mengakses Basis Data dalam VPC” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Serverless AWS Lambda Development, upgrade ke CoddyKit PRO. Kursus Serverless AWS Lambda Development mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Mengakses Basis Data dalam VPC”?
Pelajari praktik terbaik untuk menghubungkan fungsi Lambda ke basis data relasional (misalnya RDS) dan penyimpanan data lain yang berada dalam jaringan VPC privat Anda. Kamu berlatih Serverless AWS Lambda Development dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Serverless AWS Lambda Development?
Tidak diperlukan pengalaman sebelumnya. Serverless AWS Lambda Development di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.
Berapa lama pelajaran “Mengakses Basis Data dalam VPC” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Serverless AWS Lambda Development ini?
Ya. Setiap pelajaran Serverless AWS Lambda Development menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Lambda dalam VPC untuk Sumber Daya Privat
- Mengakses Basis Data dalam VPC
- Praktik Terbaik Keamanan Jaringan
- Gateway NAT dan Akses Internet dari VPC