# rds Published articles for rds. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Klarna Built Cloud Inventory for AWS Configuration Management DevFeed: [How Klarna Built Cloud Inventory for AWS Configuration Management]() Original publisher: [Read original article]() Author: Maxim Savin Published: 2025-06-06T06:38:06Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [configuration-management](), [cloud-infrastructure](), [Amazon Web Services](), [configuration](), [Cloud](), [Security](), [digital]() Tags: [automated](), [aws](), [change-management](), [cloud](), [cloud-infrastructure](), [cloud-inventory-software](), [configuration-management](), [engineering-management](), [lead-time](), [load-balancer](), [logs](), [rds](), [security](), [snapshots](), [technical-change]() ### AI overview Klarna describes Cloud Inventory, an ecosystem of services for collecting, normalizing, mapping, and serving information about ICT assets across its cloud infrastructure. The article explains how it supports configuration management through automated controls and reports faster control rollout and large-scale infrastructure optimization work. ### Source excerpt A long time ago, as a punishment for his crimes, Hades, the king of the underworld, made Sisyphus roll a huge enchanted boulder endlessly up a steep hill. Since then, many tech companies have learned to do that at scale by the hardships of cloud configuration management. Consider an Engineer who wants to ensure that the data that moves through their system is encrypted along the way. This is a noble goal, and to achieve it they must identify every classic load balancer in their AWS environment to replace it with an application load balancer that enforces encryption in transit. Now imagine doing that at the scale of a company like Klarna, where teams collectively own more than a thousand AWS accounts? Add to this a multitude of other configuration challenges -- databases that have not been deployed in a multi-availability zone set-up, missing Cloudwatch logs, expired digital certificates, systems running on unsupported framework versions -- the list is endless. Identifying and rectifying violating cloud assets often feels like an endless game of whack-a-mole played blindfolded. This is the steep price tech companies pay to operate their systems securely and confidently, day by day. Klarna Engineering Platform (KEP) has been on a mission to facilitate configuration management for Klarna Engineers. After a few iterations we have built an ecosystem of Klarna services designed to collect, normalize, map, and serve data on ICT assets within Klarna's cloud infrastructure. We call this system Cloud Inventory. Over the last few months Klarna has: Rolled out over 100 automated controls enhancing every aspect of our configuration management (security, governance, and operational excellence), each control aimed to help system owners to identify and fix violations quickly. Reduced the lead time of rolling out a control from several weeks to a matter of minutes And as a result, successfully completed several large-scale cloud infrastructure optimization projects, such as a company- ## Configuring Just-in-Time Access to Amazon RDS with Teleport and Slack DevFeed: [Configuring Just-in-Time Access to Amazon RDS with Teleport and Slack]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Amazon RDS](), [JIT](), [Slack](), [Amazon Web Services](), [Databases](), [DevOps]() Tags: [amazon-rds](), [aws](), [blog-post](), [database](), [devops](), [how-to](), [jit](), [maintenance](), [rds](), [slack]() ### AI overview This tutorial explains how to configure just-in-time privilege escalation for Amazon RDS using Teleport and Slack. It describes time-limited access requests, approval workflows, and a scenario involving third-party DevOps and database operations. ### Source excerpt This blog post explains how to configure Just-in-time (JIT) Access to Amazon RDS with Teleport and Slack. ## The Two AWS RDS Postgres Errors I Always Make DevFeed: [The Two AWS RDS Postgres Errors I Always Make]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-08T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Amazon RDS](), [Amazon Web Services](), [Amazon VPC](), [Databases](), [Security](), [ui]() Tags: [amazon-rds](), [aws](), [database](), [postgres](), [rds](), [security](), [user-interface](), [vpc]() ### AI overview A personal guide to three recurring mistakes when creating Amazon RDS PostgreSQL instances: failing to specify an initial database name, placing the database server in the wrong VPC, and using the wrong security group. ### Source excerpt You know that awful feeling of personal stupidity when you consistently make the same mistake time after time? Well my approach to addressing that is to document said mistakes, here, each time I make them. Sometimes I take the approach of admitting to them and sometimes I take the approach of just writing them as a blog post. There are two errors, nay three, I make almost every single time I create an RDS postgres instance and I thought "maybe it is time to write them down and (hopefully) curse less" the next time. Note: I wrote this as a text post with pictures below so that the quick answers appear first before a whole bunch of screenshots. Error 1: Not Creating the Database When you Create the Database Server When you create a "database" on RDS you are actually creating a database server on which you then create the database itself. Now the core issue here is that AWS makes it very hard, at least when you are making a Postgres database to create that database later. I'm sure there is a way but, yesterday, in a few hours of messing with this, I never found it. What I had to do was drop my database server and walk through the creation process again, finally finding it nested away in an expandable section of the user interface. When you are walking through the "Create Database" form, there is a final section called "Additional Configuration". If you expand this then the very first option is "Initial Database Name" along with the helpful message: If you do not specify a database name, Amazon RDS does not create a database. Groan. Keep in mind that this whole feature starts on a web page titled "Create Database" (but the default is to NOT create a database). Error 2: Not Putting the Database Server in the Same VPC Generally speaking most of us tend to use a single VPC (virtual private cloud) for our AWS boxes. Despite this it is not guaranteed that your database server ends up in the same VPC as your other boxes unless you explicitly specify this. Error 3: Not Putting ## Update Amazon RDS max\_connections with Parameter Group DevFeed: [Update Amazon RDS max\_connections with Parameter Group]() Original publisher: [Read original article]() Published: 2016-01-28T15:46:52Z Content type: tutorial Language: en Sources: [Jolly Good Code]() Topics: [RDS for PostgreSQL](), [Amazon RDS](), [PostgreSQL]() Tags: [amazon](), [amazon-rds](), [parameter](), [postgresql](), [rds](), [rds-for-postgresql](), [update]() ### AI overview The article concerns updating the max_connections setting for Amazon RDS for PostgreSQL using a parameter group. It notes that default max_connections values differ by instance. ### Source excerpt Do you use Amazon RDS for PostgreSQL? Do you know that, by default, each instance comes with a different number of max_connections?