SQS AWS Integration:can't make sense of this example code

[Greg Charles]

I'm pretty new to Spring AWS integration. Right now I'm just trying to get a prototype working that will implement a message listener for an SQS  ... something like you'd handle in JEE with RabbitMQ and an MDB. The example I'm seeing at libraries.io and repeated elsewhere at various sites has this setup code:

@SpringBootApplication
public static class MyConfiguration {

    @Autowired
    private AmazonSQSAsync amazonSqs;

    @Bean
    public PollableChannel inputChannel() {
        return new QueueChannel();
    }

    @Bean
    public MessageProducer sqsMessageDrivenChannelAdapter() {
        SqsMessageDrivenChannelAdapter adapter = new SqsMessageDrivenChannelAdapter(this.amazonSqs, "myQueue");
        adapter.setOutputChannel(inputChannel());
        return adapter;
    }
}

First, it's annotated as SpringBootApplication not Configuration. That doesn't seem to be a typo, because they have many examples done the same way. Also, the class is declared static, so it can't be an outer class. Maybe the intention is that this should be an inner class within the Spring Boot class? There's nothing to suggest this interpretation though, and it would still need a Configuration annotation, wouldn't it?

[Peter Rooke]

Greg, the @SpringBootApplication annotation is a shortcut for the other three common annotations @Configuration, @EnableAutoConfiguration and @ComponentScan.

@SpringBootApplication Spring Boot Reference Guide

Sorry that this is just half an answer, I'm still trying to work out exactly how Java / Spring / AWS fit together.  From AWS I'm seeing a movement towards serverless (aws lambda) while I'm thinking spring boot would require servers (EC2) with IAM roles defined to allow access to the queuing service.  Maybe you could use Spring with AWS Lambda