#1157 CentOS Automotive SIG IAM role
Closed: Fixed 10 months ago by lrossett. Opened 11 months ago by lrossett.

Hello,

I would like to request the following AWS resources for the CentOS Automotive SIG:

  • An IAM role that has permissions to read, delete, publish and tag AMIs
  • The role should allow API access for such operations as well.

This AWS role will be used by the CentOS Automotive SIG to publish some of its images to AWS for public usage.


Metadata Update from @arrfab:
- Issue assigned to arrfab

11 months ago

Metadata Update from @arrfab:
- Issue tagged with: authentication, centos-build-pipeline, medium-gain, medium-trouble

11 months ago

@lrossett : can you send me (private email works fine) the public ip range from which you'll interact with the aws api ? We need to restrict from where the credentials will be used (best practices)
Also, when discussing with @pingou I realized that I have his gpg pub key but can you update your fas account to point to a gpg public key id that can be found on a public keyserver ?

TIA

users/access key/secret key generated and gpg encrypted transferred to @pingou
There is now a (non public) centos-sigs-ami-images S3 bucket which you can use to upload first your raw cloud image.
From there you can import as snapshot in one region as AMI and then copy to different regions

PS : waiting for the IP addresses range to adapt new policy attached to that user, so don't try it now : it wouldn't work

Metadata Update from @arrfab:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

11 months ago

@arrfab Should I target a specific s3 region?

That bucket was created in us-east-2 (only one) so you can start your import to create the AMI in same region and then copy it to others

I am getting an "AccessDenied" (403) error, is the user policy still being processed?

yes, as said above, I'm still waiting for a mail from your about the IP range to allow for that (currently it would be denied, per existing policy) ;-)

PS : waiting for the IP addresses range to adapt new policy attached to that user, so don't try it now : it wouldn't work

Metadata Update from @arrfab:
- Issue tagged with: blocked

11 months ago

Policy updated with the IP (only one ?) that you sent us

Can we close this ticket now ? (as policy was updated and no negative feedback received)

Apologies, yes it can be closed.

Metadata Update from @lrossett:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

10 months ago

Login to comment on this ticket.

Metadata