Amplify-cli: @searchable option for encrypted Elasticsearch

Created on 20 Mar 2019  路  3Comments  路  Source: aws-amplify/amplify-cli

The @searchable directive creates an unencrypted at rest elasticsearch domain. There is no way to change the encryption after the domain is created so can we get an option to encrypt elasticsearch at rest similar to the recently added option to enable DynamoDB encryption at rest? Thanks

enhancement graphql-transformer pending-review

Most helpful comment

Is this issue still being worked? We have a requirement to employ ES with a number of security features (data encryption at rest, require HTTPS) but don't know where this is being tracked or if there is a workaround to accomplish this at this point.

All 3 comments

@gabriel-wilkes thanks for your feedback. I have added this to the backlog and we will get this prioritized

The project this was added to back in May just closed yesterday. I suppose you're tracking this internally instead? Still need this feature, thanks.

Is this issue still being worked? We have a requirement to employ ES with a number of security features (data encryption at rest, require HTTPS) but don't know where this is being tracked or if there is a workaround to accomplish this at this point.

Was this page helpful?
0 / 5 - 0 ratings