Creating a new stream with wrong bucket config in rabbit.conf

[SimonUnge]

Describe the bug

Two issues:

If you configure your s3.bucket with a bucket that your account does not have permission to use, you will see the following crash:

2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>   crasher:
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     initial call: osiris_writer:init/1
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     pid: <0.765.0>
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     registered_name: []
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     exception exit: {timeout,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                         {gen_server,call,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                             [rabbitmq_stream_s3_log_manifest,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                              {init_writer,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                                  {resource,<<"/">>,queue,<<"s1">>},
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                                  "/.../__s1_1763145000075864515"}]}}
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>       in function  gen_batch_server:handle_continue/2 (src/gen_batch_server.erl, line 423)
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>       in call from gen_batch_server:init_it/6 (src/gen_batch_server.erl, line 163)
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     ancestors: [osiris_server_sup,osiris_sup,<0.136.0>]
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     message_queue_len: 1
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     messages: [{'$gen_cast',
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                       {register_offset_listener,<0.399.0>,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                           {rabbitmq_stream_s3_log_manifest,
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                               format_osiris_event,[]},
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>                           -1}}]
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     links: [<0.140.0>]
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     dictionary: []
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     trap_exit: true
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     status: running
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     heap_size: 1598
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     stack_size: 36
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>     reductions: 5586
2025-11-14 18:41:38.436302+00:00 [error] <0.765.0>   neighbours:

Second issue:
If you instead configure a bucket name that does not even exist, it 'seems' to work fine.

To Reproduce
Configure s3.bucket to a bucket that does not exist or one that you don't have the correct permissions for.

Expected behavior

There need to be some kind of error stating that we cannot access the bucket, in both cases.

Screenshots
N/A

Additional context
Add any other context about the problem here.