- Newest
- Most votes
- Most comments
The issue you're experiencing with creating an object in your S3 on Outposts bucket using an access point is likely related to connectivity or endpoint configuration. Here are a few points to consider:
-
Endpoint Configuration: Ensure that you have properly set up an endpoint for your S3 on Outposts. S3 on Outposts requires a specific endpoint to route requests to access points and enable private VPC connectivity to Outpost buckets.
-
VPC Connectivity: S3 on Outposts only supports VPC-only access points. Make sure your VPC is correctly configured to communicate with the Outpost.
-
Service Link Connection: Verify that the service link connection between your Outpost and the home AWS Region is active. If this connection is down, you may encounter issues creating or accessing objects.
-
IAM Permissions: While you've provided bucket and access point policies, ensure that the IAM user or role you're using to execute the AWS CLI command has the necessary permissions to perform the PutObject operation.
-
ARN Format: Double-check that you're using the correct ARN format for S3 on Outposts access points in your command. The format should be: arn:aws:s3-outposts:region:account-id:outpost/outpost-id/accesspoint/accesspoint-name
-
x-amz-outpost-id Header: When making requests to S3 on Outposts, you may need to include the x-amz-outpost-id header for proper request routing.
If you've verified these points and are still encountering issues, you may want to check the status of your Outpost and ensure there are no ongoing connectivity problems. Additionally, you could try creating the object directly in the bucket (without using the access point) to isolate whether the issue is specific to the access point configuration.
Sources
Working with Amazon S3 on Outposts endpoints - Amazon S3 on Outposts
Working with S3 on Outposts buckets - Amazon S3 on Outposts
Relevant content
asked 2 years ago
