This may be due to your S3 bucket being newly created.
If a new S3 bucket has been created, it will need to be fully configured and billing files need to be transferred over to the new bucket for data to be ingested into the platform.