Overview
Charges for this image cover the security hardening, optimization, and pre-integration work Hanwei performs on top of the upstream PostgreSQL 17 and CentOS Stream 9 projects. PostgreSQL 17 is installed from the PostgreSQL Global Development Group repository, the cluster is initialized and the service is enabled, so the database is listening when the instance finishes booting. This version replaces the earlier PostgreSQL 15 image. The operating system underneath carries the same hardened and tuned baseline used across this catalogue.
What Hanwei Adds to Upstream PostgreSQL 17
- Cluster installed and initialized at build time: packages come from the PostgreSQL Global Development Group repository, the cluster lives under /var/lib/pgsql/17/data and the postgresql-17 service is enabled.
- Transparent huge pages disabled at boot: a oneshot unit sets them to never before the database starts, following the vendor's guidance. This is not the distribution default, where the tuned virtual-guest profile leaves them enabled.
- contrib extensions present: pg_stat_statements, pgcrypto and the other bundled modules can be created without adding packages.
- Tuning baseline applied identically across the catalogue: the file descriptor limit goes from 1024 to 65536 and the memory-map ceiling from 65530 to 262144; the device receive backlog goes from 1000 to 16384 and the TCP SYN backlog from 128 to 8192, so bursts queue instead of being dropped; socket buffer maxima reach 16 MB for larger autotuned windows; connections keep their congestion window across idle periods; and the journal is capped at 500 MB. The profile raises ceilings only and does not alter protocol semantics or application behaviour.
- Applied hardening beyond the distribution default: SSH is limited to a vetted cipher, key exchange and MAC list, X11 forwarding is off, the login grace period is shortened and verbose authentication logging is on; auditd runs a base rule set for privileged command execution; the kernel drops ICMP redirects on IPv4 and IPv6, logs martian packets, filters reverse paths in loose mode, restricts dmesg, disables setuid core dumps and turns off sysrq.
- AWS operational integration: the SSM Agent is installed and enabled for Session Manager and Patch Manager without an inbound SSH rule; chrony points at the Amazon Time Sync Service; and the root filesystem extends at boot when the volume exceeds the image default.
- Patch level set at the build date: packages come from official upstream repositories at the newest level published when the image was built.
- Repeatable build and EC2 validation: each version comes from the same build process and is launched and exercised on EC2 before release.
Access and Security Posture
- SELinux runs in enforcing mode and auditd records activity against a base rule set.
- Sign in as 'ec2-user' with the key pair selected at launch, then use 'sudo su -' for a root shell. Session Manager is available as an alternative that needs no inbound port.
- Direct root login over SSH is disabled and password authentication is not accepted.
- No authorized keys and no SSH private keys are embedded in the image.
Operational Impact on EC2
- Launch-to-usable-database time is reduced to a single boot cycle.
- Every instance starts from an identical configuration, removing drift between development, staging and production hosts.
- Network services need no per-host limit or backlog adjustment before handling load.
- Clock accuracy comes from the Amazon Time Sync Service, which matters for log correlation and request signing.
- Post-launch patching effort is lower because the package set is current at release.
Where This Image Fits
- Application backends that need a PostgreSQL endpoint on an instance the team controls.
- Development and test environments recreated frequently from an identical configuration.
- Analytical and reporting databases where the raised descriptor and memory-map ceilings matter under many concurrent connections.
- Migration staging, where a target cluster must be available quickly for dump and restore rehearsals.
About PostgreSQL 17 and CentOS Stream 9
PostgreSQL is an object-relational database known for standards compliance, transactional DDL and an extension mechanism covering geospatial data, full-text search, time series and vector similarity. Version 17 adds incremental backup, a rewritten vacuum memory manager, faster bulk loading through COPY and better planning for correlated subqueries. The 17 series is supported by the PostgreSQL project into 2029.
CentOS Stream 9 is a Linux distribution that tracks the development stream of Red Hat Enterprise Linux 9. Packages land in CentOS Stream before they appear in a RHEL minor release, so it stays close to the RHEL package set and toolchain while remaining freely redistributable. It uses dnf, systemd and SELinux, which makes it a predictable base for server workloads that need RHEL compatibility.
Highlights
- WHAT IS PACKAGED - This image provides PostgreSQL 17 installed from the PostgreSQL Global Development Group repository with the cluster initialized and the service enabled, contrib extensions present, and transparent huge pages disabled as the database documentation requires.
- HOW THE BASELINE IS HARDENED AND TUNED - SELinux enforcing, root login locked and SSH limited to key-based authentication with a vetted cipher, key exchange and MAC list. auditd runs a base rule set for privileged commands. The kernel drops ICMP redirects, logs martian packets and restricts dmesg. The file descriptor limit goes from 1024 to 65536 and the memory-map ceiling from 65530 to 262144; receive and SYN backlogs are enlarged and socket buffers reach 16 MB.
- HOW IT FITS AWS OPERATIONS - The SSM Agent is installed and enabled, so instances can be managed through Session Manager and Patch Manager without an inbound SSH rule. chrony is pointed at the Amazon Time Sync Service, the root filesystem extends automatically when the volume exceeds the image default, and cloud-init handles user-data provisioning in launch templates and Auto Scaling groups.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
- ...
Dimension | Cost/hour |
|---|---|
t3.medium Recommended | $0.09 |
t2.micro | $0.04 |
t3.micro | $0.04 |
m7a.24xlarge | $2.39 |
c7i.2xlarge | $0.99 |
c5a.large | $0.09 |
r6idn.large | $0.19 |
c5a.8xlarge | $1.59 |
c6i.12xlarge | $0.99 |
r5.metal | $3.19 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
no refunds
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Updated to the latest
Additional details
Usage instructions
SSH as user "ec2-user" to the running instance and use sudo to run commands requiring root access.
Use "sudo su - " to switch to root.
OS: CentOS Stream 9
Server version: PostgreSQL-17
Postgresql database user: postgres
Connecting to PostgreSQL using the local shell:
1: $sudo -i -u postgres
2: $psql
Service Management:
To start/stop/status PostgreSQL-17 Service: sudo systemctl start/stop/status postgresql-17
Please note that you should use systemctl start/stop/status postgresql-17 instead of systemctl start/stop/status postgresql
Configuration File Path: /var/lib/pgsql/17/data/
postgresql.conf File Path: /var/lib/pgsql/17/data/postgresql.conf
pg_hba.conf File Path: /var/lib/pgsql/17/data/pg_hba.conf
For security reasons, remote connection to the postgresql service is not configured. You can modify the two configuration files:/var/lib/pgsql/17/data/postgresql.conf,/var/lib/pgsql/17/data/pg_hba.conf to configure remote connections.
PostgreSQL Default Port:5432 this is by default not allowed on cloud firewall for security. Please allow SSH port 22, PostgreSQl Port 5432 to limited IPs for access.
Support
Vendor support
If you encounter problems in the process of using the system, please feel free to contact us by email: prosupport@hanweie.com , thank you!
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.