Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
Kinesis ComponentAvailable as of Camel 2.17 The Kinesis component supports receiving messages from and sending messages to Amazon Kinesis service. Prerequisites You must have a valid Amazon Web Services developer account, and be signed up to use Amazon Kinesis. More information are available at AWS Kinesis URI Formataws-kinesis://stream-name[?options] The stream needs to be created prior to it being used. URI Options
Required Kinesis component options You have to provide the amazonKinesisClient in the Registry with proxies and relevant credentials configured. Batch ConsumerThis component implements the Batch Consumer. This allows you for instance to know how many messages exists in this batch and for instance let the Aggregator aggregate this number of messages. UsageMessage headers set by the Kinesis consumer
Message headers set by the Kinesis producer
AmazonKinesis configurationYou will need to create an instance of AmazonKinesisClient and bind it to the registry ClientConfiguration clientConfiguration = new ClientConfiguration(); clientConfiguration.setProxyHost("http://myProxyHost"); clientConfiguration.setProxyPort(8080); Region region = Region.getRegion(Regions.fromName(region)); region.createClient(AmazonKinesisClient.class, null, clientConfiguration); // the 'null' here is the AWSCredentialsProvider which defaults to an instance of DefaultAWSCredentialsProviderChain registry.bind("kinesisClient", client); You then have to reference the AmazonKinesisClient in the amazonKinesisClient URI option. from("aws-kinesis://mykinesisstream?amazonKinesisClient=#kinesisClient") .to("log:out?showAll=true"); Providing AWS CredentialsIt is recommended that the credentials are obtained by using the DefaultAWSCredentialsProviderChain that is the default when creating a new ClientConfiguration instance, however, a different AWSCredentialsProvider can be specified when calling createClient(...). DependenciesMaven users will need to add the following dependency to their pom.xml. pom.xml <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-aws</artifactId> <version>${camel-version}</version> </dependency> where |