When I apply the above changes using terraform it starts loading new sp-enrich-server but I can see following error in cloudwatch logs
"message": "$.parameters.geo.database: does not have a value in the enumeration [GeoLite2-City.mmdb, GeoIP2-City.mmdb]",
All other events also stop because of above error and nothing is logged in database. As I revert the changes it starts working.
I have my bucket and GeoLite2-City.mmdb file.
Let me know what is that I am missing to enable the IP lookup enrichment?
In your custom_s3_hosted_assets_bucket_name you just need to provide the name of the bucket not an S3 URI so likely the IAM policy is not going to work as expected to resolve the files once you fix your Enrichment input.
Could you give that a try and see if it fixes it for you?
Thanks you for the clarification. My application is using custom schemas. We have separate tables in postgresql that store data collected by tracker. These tables have columns corresponding to custom schema. Is it possible to have ip enrichment details like, geo_city, geo_country, geo_region, geo_zipcode,geo_latitude,geo_longitude, geo_regionname etc in my custom tables? We can modify our custom schema for the above fields if required.