Скачать или смотреть How To Connect A AWS Postgres With My Computer

Today we moved from a local development environment into the AWS Cloud. We successfully provisioned a PostgreSQL database, bypassed complex networking roadblocks, and secured AWS credits for our efforts.
Here is the step-by-step breakdown of how we achieved a functional cloud database and what we learned along the way.
Step 1: Provisioning the PostgreSQL Instance
We began by launching a PostgreSQL instance via Amazon RDS. While the setup wizard is user-friendly, the default settings are "Secure by Default," which means the database starts completely invisible to the outside world.
Step 2: Overcoming the Connection "Time Out"
The biggest challenge today was the initial connection failure. Our terminal threw a Connection timed out error because of two missing links:
Public Accessibility: By default, RDS instances resolve to a Private IP (like 172.31.x.x). We had to go into the RDS Dashboard, click Modify, and set Public Access to Yes.
Security Group Firewall: We navigated to the VPC Security Group and added an Inbound Rule for Port 5432. We set the source to "My IP" so only our specific computer could talk to the database.
Step 3: Verifying with Networking Tools
Before jumping back into SQL, we used the nc (netcat) networking tool to verify the "pipe" was open. This confirmed our computer could finally "see" the AWS port.
bash
Testing if the AWS port is reachable
nc -zv your-db-endpoint.aws.com 5432
Result: Connection to port 5432 [tcp/postgresql] succeeded!
Use code with caution.

Step 4: Database Creation and Data Entry
Once the handshake was successful, we used the psql command-line tool to log in, create a schema, and input data.
sql
-- Connecting via Terminal
psql -h database-1.c2x46o486k9m.us-east-1.rds.amazonaws.com -U postgres

-- Success! Now we create our first table
CREATE TABLE users (
id SERIAL PRIMARY KEY,
name TEXT NOT NULL,
created_at TIMESTAMP DEFAULT NOW()
);

-- Inputting data
INSERT INTO users (name) VALUES ('Felex');

-- Verifying the achievement
SELECT * FROM users;
Use code with caution.

Step 5: Claiming the $20 AWS Credit
By completing this "Explore AWS" project for RDS, we successfully triggered a $20.00 AWS Credit. This credit is now applied to the account (valid until 11/16/2026), effectively making our learning session today free of charge.
Step 6: The Clean-Up (Deletion Process)
To avoid unexpected costs, we walked through the proper way to shut down a cloud resource:
Disable Deletion Protection: We had to "Modify" the instance first to uncheck this safety feature.
Delete Action: We selected the instance and clicked Delete.
Final Snapshot: We opted to create a final snapshot—this acts as a "save game" file, allowing us to restore this exact database in the future even though the instance is gone.
Confirmation: We typed delete me to finalize the termination.
Summary: Today we didn't just "start a database"—we navigated VPC security, handled public/private IP routing, and mastered the lifecycle of cloud infrastructure. Stay tuned for our next architecture deep-dive!