After "Announcement: AWS Step Functions adds support for over 200 AWS Services with AWS SDK Integration": https://forums.aws.amazon.com/ann.jspa?annID=8933
We wanted to use the new AWS SDK Integration in Step Functions to start up a OpenSearch/Elasticsearch Domain, however Step Functions does not seem to support the EBSOptions parameter https://docs.aws.amazon.com/opensearch-service/latest/developerguide/configuration-api.html#configuration-api-datatypes-ebsoptions, as it errors with:
The Parameters '{"ElasticsearchClusterConfig":{"InstanceType":"t3.small.elasticsearch","InstanceCount":1,"DedicatedMasterEnabled":false,"ZoneAwarenessEnabled":false},"DomainName":"test-12345","ElasticsearchVersion":"7.1","EBSOptions":{"EBSEnabled":true,"VolumeType":"gp2","VolumeSize":100},"VPCOptions":OMITTED,"AccessPolicies":OMITTED}' could not be used to start the Task: The field "EBSOptions" is not supported by Step Functions
The same parameters work just fine using boto3.
Is this by design? Should we expect support in the future or it is never going to be an option? Is there any documentation about these limitations?
Is there a workaround other than using the SDK directly in a Lambda?
Edited by: LPKTech on Oct 22, 2021 5:15 AM - Fix formatting of the error and added detail about it running on boto3