AMI not avalable #1
Comments
|
Hi Joon and Mike,
Could you check the status of our missing CWAS AMI please?
Thanks
S
…On Thu, Jun 20, 2019 at 11:06 AM J Andrew R Farrell < ***@***.***> wrote:
When I search AWS for the ami "ami-0e1757919181cfb66" I don't get any
results. Can you make sure it is set to public and the correct id is in the
readme. Thanks
[image: image]
<https://user-images.githubusercontent.com/6642462/59871024-d664a700-9353-11e9-8f92-9dba6fb226ca.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=ABV4BAIFWPB5ZNPZZCE5ICLP3PBMHA5CNFSM4HZZNDH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2YVSOQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABV4BAJ2QIRGOUDNFXCK43TP3PBMHANCNFSM4HZZNDHQ>
.
|
|
I can confirm that the image is not public.
$ aws ec2 describe-images --image-ids ami-0e1757919181cfb66
{
"Images": [
{
"VirtualizationType": "hvm",
"Description": "",
"Hypervisor": "xen",
"EnaSupport": true,
"SriovNetSupport": "simple",
"ImageId": "ami-0e1757919181cfb66",
"State": "available",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"SnapshotId": "snap-0ff052e1f5fe6d65e",
"DeleteOnTermination": true,
"VolumeType": "gp2",
"VolumeSize": 180,
"Encrypted": false
}
}
],
"Architecture": "x86_64",
"ImageLocation": "xxxxxxxx/An 2018 to share",
"RootDeviceType": "ebs",
"OwnerId": "xxxxxxxxx",
"RootDeviceName": "/dev/xvda",
"CreationDate": "2018-10-08T21:22:08.000Z",
"Public": false,
"ImageType": "machine",
"Name": "An 2018 to share"
}
]
}
Joon, I assume the image is ready to be published, but wanted to confirm with you before changing the setting myself.
All the best,
Mike
…________________________________
From: Stephan Sanders <stephansanders@gmail.com>
Sent: Thursday, June 20, 2019 11:54:09 AM
To: sanderslab/cwas; Gilson, Michael C; Joon An
Cc: sanderslab/cwas; Subscribed
Subject: Re: [sanderslab/cwas] AMI not avalable (#1)
Hi Joon and Mike,
Could you check the status of our missing CWAS AMI please?
Thanks
S
On Thu, Jun 20, 2019 at 11:06 AM J Andrew R Farrell <notifications@github.com<mailto:notifications@github.com>> wrote:
When I search AWS for the ami "ami-0e1757919181cfb66" I don't get any results. Can you make sure it is set to public and the correct id is in the readme. Thanks
[image]<https://urldefense.proofpoint.com/v2/url?u=https-3A__user-2Dimages.githubusercontent.com_6642462_59871024-2Dd664a700-2D9353-2D11e9-2D8f92-2D9dba6fb226ca.png&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=RYij6pmNWQCJwMfqEcLAllc-lwCupVcVUlFwOwpOaDc&e=>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sanderslab_cwas_issues_1-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DABV4BAIFWPB5ZNPZZCE5ICLP3PBMHA5CNFSM4HZZNDH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2YVSOQ&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=cIxZtseMDEQ6dWG22J7XIe6RUoS-jbhXpWRj1bprh2E&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABV4BAJ2QIRGOUDNFXCK43TP3PBMHANCNFSM4HZZNDHQ&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=7fwc5UbVUafpgEVhrGMiB-9TMqwIg_jMxAJZEw0BdCQ&e=>.
|
|
Greetings, all
The CWAS AMI is now public. Verified from separate account and via the command line.
Please let me know if you encounter further access issues.
$ aws ec2 describe-images --image-ids ami-0e1757919181cfb66
{
"Images": [
{
"VirtualizationType": "hvm",
"Description": "",
"Hypervisor": "xen",
"EnaSupport": true,
"SriovNetSupport": "simple",
"ImageId": "ami-0e1757919181cfb66",
"State": "available",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"SnapshotId": "snap-0ff052e1f5fe6d65e",
"DeleteOnTermination": true,
"VolumeType": "gp2",
"VolumeSize": 180,
"Encrypted": false
}
}
],
"Architecture": "x86_64",
"ImageLocation": "xxxxxxxxx/An 2018 to share",
"RootDeviceType": "ebs",
"OwnerId": "xxxxxxxxx",
"RootDeviceName": "/dev/xvda",
"CreationDate": "2018-10-08T21:22:08.000Z",
"Public": true,
"ImageType": "machine",
"Name": "An 2018 to share"
}
]
}
…-Mike
________________________________
From: Gilson, Michael C
Sent: Thursday, June 20, 2019 12:44:07 PM
To: Stephan Sanders; sanderslab/cwas; Joon An
Cc: sanderslab/cwas; Subscribed
Subject: Re: [sanderslab/cwas] AMI not avalable (#1)
I can confirm that the image is not public.
$ aws ec2 describe-images --image-ids ami-0e1757919181cfb66
{
"Images": [
{
"VirtualizationType": "hvm",
"Description": "",
"Hypervisor": "xen",
"EnaSupport": true,
"SriovNetSupport": "simple",
"ImageId": "ami-0e1757919181cfb66",
"State": "available",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"SnapshotId": "snap-0ff052e1f5fe6d65e",
"DeleteOnTermination": true,
"VolumeType": "gp2",
"VolumeSize": 180,
"Encrypted": false
}
}
],
"Architecture": "x86_64",
"ImageLocation": "xxxxxxxx/An 2018 to share",
"RootDeviceType": "ebs",
"OwnerId": "xxxxxxxxx",
"RootDeviceName": "/dev/xvda",
"CreationDate": "2018-10-08T21:22:08.000Z",
"Public": false,
"ImageType": "machine",
"Name": "An 2018 to share"
}
]
}
Joon, I assume the image is ready to be published, but wanted to confirm with you before changing the setting myself.
All the best,
Mike
________________________________
From: Stephan Sanders <stephansanders@gmail.com>
Sent: Thursday, June 20, 2019 11:54:09 AM
To: sanderslab/cwas; Gilson, Michael C; Joon An
Cc: sanderslab/cwas; Subscribed
Subject: Re: [sanderslab/cwas] AMI not avalable (#1)
Hi Joon and Mike,
Could you check the status of our missing CWAS AMI please?
Thanks
S
On Thu, Jun 20, 2019 at 11:06 AM J Andrew R Farrell <notifications@github.com<mailto:notifications@github.com>> wrote:
When I search AWS for the ami "ami-0e1757919181cfb66" I don't get any results. Can you make sure it is set to public and the correct id is in the readme. Thanks
[image]<https://urldefense.proofpoint.com/v2/url?u=https-3A__user-2Dimages.githubusercontent.com_6642462_59871024-2Dd664a700-2D9353-2D11e9-2D8f92-2D9dba6fb226ca.png&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=RYij6pmNWQCJwMfqEcLAllc-lwCupVcVUlFwOwpOaDc&e=>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sanderslab_cwas_issues_1-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DABV4BAIFWPB5ZNPZZCE5ICLP3PBMHA5CNFSM4HZZNDH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2YVSOQ&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=cIxZtseMDEQ6dWG22J7XIe6RUoS-jbhXpWRj1bprh2E&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABV4BAJ2QIRGOUDNFXCK43TP3PBMHANCNFSM4HZZNDHQ&d=DwMFaQ&c=iORugZls2LlYyCAZRB3XLg&r=J3bHVIU7V3YgTWStB4Qt14jW7qpSgeCPjnq0sQc7njI&m=gI25HQgKehhukLNhK7EtOlj_-kMw5ADkv9LuuaHD2Ao&s=7fwc5UbVUafpgEVhrGMiB-9TMqwIg_jMxAJZEw0BdCQ&e=>.
|
|
I would like to point out that this image is in the US East N.Virginia region (us-east-1) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I search AWS for the ami "ami-0e1757919181cfb66" I don't get any results. Can you make sure it is set to public and the correct id is in the readme. Thanks
The text was updated successfully, but these errors were encountered: