Skip to main content

Hi All,

We're looking at setting up a PostGIS database on a PostGIS database sitting on an AWS Serverless RDS and are unclear whether our desktop FME will be able to successfully interact with it.

Our main concern is with some of our existing FME workspaces that we would want to read from the PostGIS database, process for 2-3 days then write the output back to the database. During this processing we'd expect the AWS Serverless RDS to switch itself off as all the processing is happening on my desktop, but will FME "wake-up" the Serverless RDS when it's time to write to the database?

 

Cheers

 

Rich

 

 

 

In my experience FME is able to both read and write to RDS Postgresql, granted that all the security groups etc have been correctly configured.

Concerning interacting with the RDS instance itself, this is something that is out of FME's control, but you can e.g. use the AWS command line interface inside a SystemCaller to interact with the instance at different points in your process. In other words, you will have to manually implement the functionality to switch on or off the RDS instance.


@yorkie As David pointed out FME as able to read & write from & to PostGIS databases.

 

 

When you say "AWS Serverless RDS" does that mean that you are using the Serverless option of the Amazon Aurora with PostgreSQL compatibility?

 

 

I am asking because the regular AWS RDS database with PostgreSQL/PostGIS engine type is not serverless. So you would be in charge of pausing and starting the RDS instance similar to what David described. Instead of using a SystemCaller to call the AWS CLI you could also use the AWS Simple Notification Service (SNS) and to notify an AWS Lambda function to stop & start your instance. This would probably give you more control and allow you to put safeguards in place that make sure your instance is indeed up & running and ready to be accessed by FME. Here are some resources that might be useful:

https://aws.amazon.com/blogs/database/implementing-db-instance-stop-and-start-in-amazon-rds/

 

 

https://docs.aws.amazon.com/lambda/latest/dg/with-sns.html

@yorkie As David pointed out FME as able to read & write from & to PostGIS databases.

 

 

When you say "AWS Serverless RDS" does that mean that you are using the Serverless option of the Amazon Aurora with PostgreSQL compatibility?

 

 

I am asking because the regular AWS RDS database with PostgreSQL/PostGIS engine type is not serverless. So you would be in charge of pausing and starting the RDS instance similar to what David described. Instead of using a SystemCaller to call the AWS CLI you could also use the AWS Simple Notification Service (SNS) and to notify an AWS Lambda function to stop & start your instance. This would probably give you more control and allow you to put safeguards in place that make sure your instance is indeed up & running and ready to be accessed by FME. Here are some resources that might be useful:

https://aws.amazon.com/blogs/database/implementing-db-instance-stop-and-start-in-amazon-rds/

 

 

https://docs.aws.amazon.com/lambda/latest/dg/with-sns.html

+1 for SNS + Lambda, a very powerful combination, although a step up in complexity from using the AWS CLI.


@yorkie As David pointed out FME as able to read & write from & to PostGIS databases.

 

 

When you say "AWS Serverless RDS" does that mean that you are using the Serverless option of the Amazon Aurora with PostgreSQL compatibility?

 

 

I am asking because the regular AWS RDS database with PostgreSQL/PostGIS engine type is not serverless. So you would be in charge of pausing and starting the RDS instance similar to what David described. Instead of using a SystemCaller to call the AWS CLI you could also use the AWS Simple Notification Service (SNS) and to notify an AWS Lambda function to stop & start your instance. This would probably give you more control and allow you to put safeguards in place that make sure your instance is indeed up & running and ready to be accessed by FME. Here are some resources that might be useful:

https://aws.amazon.com/blogs/database/implementing-db-instance-stop-and-start-in-amazon-rds/

 

 

https://docs.aws.amazon.com/lambda/latest/dg/with-sns.html

@gerhardatsafe @david_r

thanks for your response and the links. Yes, I mean Serverless option of the Amazon Aurora with PostgreSQL compatibility (sorry my terminology is poor). I'll forward your responses to our Developer and let you know how we get on!

Cheers,

Rich

 

 


@gerhardatsafe @david_r

thanks for your response and the links. Yes, I mean Serverless option of the Amazon Aurora with PostgreSQL compatibility (sorry my terminology is poor). I'll forward your responses to our Developer and let you know how we get on!

Cheers,

Rich

 

 

@yorkie According to this doc I would assume your scenario works if the Automatic Pause and Resume for Aurora Serverless is configured correctly:

 

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.how-it-works.html

Reply